Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt upgrade makes ubuntu 22.04 unbootable #10

Closed
kindlychung opened this issue Feb 13, 2023 · 8 comments
Closed

apt upgrade makes ubuntu 22.04 unbootable #10

kindlychung opened this issue Feb 13, 2023 · 8 comments

Comments

@kindlychung
Copy link

I installed ubuntu 22.04 and everything worked until I tried sudo apt update && sudo apt upgrade, which results in some failure in grub efi configuration. After a restart I could not boot into ubuntu any more. The error looks like this:

Scanning nvme 0:4...
Unable to read file /
Failed to load /
BootOrder not defined
EFI boot manager: cannot load any image
Found EFI removable media binary efi/boot/...
180224 bytes read in 0 ms
Booting /efi\boot\bootaa64.efi
error: no such device: 87c6b...
error: unknown filesystem.
Entering rescue mode...
grub rescue>

MacOS is still working though.

@tobhe
Copy link
Member

tobhe commented Feb 13, 2023

was this after the first reboot? there used to be a race in the first-boot script that broke the random uuid renaming, but that should be fixed. This error message looks suspicious because the default uuid that gets changed with the first-boot script is ROOT_UUID=87c6b0ce-3bb6-4dc2-9298-3a799bbb5994 which seems to match your grub config.
I wonder if this happens again if you try a second time. The previous bug used to happen randomly.

@kindlychung
Copy link
Author

Yeah, it's the first reboot.

Unfortunately I have wiped it out so won't be able to try a second time. But I might give 22.10 a go. Thanks for your work!

@nreef12
Copy link

nreef12 commented Mar 26, 2023

I'm having about the same issue on the first reboot, it does seem like it has to do with the UUID image

@tobhe
Copy link
Member

tobhe commented Mar 26, 2023

Yes, there is a first-boot script that is supposed to change the uuid from the hardcoded initial one to a random one. It looks like it sometimes fails which causes a mismatch between what grub expects the actual UUID. This seems to happen randomly so I don't really know how to reproduce and fix it reliably. I thought I had fixed it at some point but apparently it just never happened on my hardware anymore.

@tobhe
Copy link
Member

tobhe commented Mar 26, 2023

This reddit post suggests that it actually might not be a Ubuntu specific problem but also happen on regular Asahi.

@nreef12
Copy link

nreef12 commented Mar 28, 2023

This reddit post suggests that it actually might not be a Ubuntu specific problem but also happen on regular Asahi.

I tried @marcan's suggestion on that post to run sudo update-grub, but it just tells me this:

grub probe: error: failed to get canonical path of `/dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799bbb5994'

@nreef12
Copy link

nreef12 commented Mar 28, 2023

Also, running journalctl -b0 > log.txt gets this

nreef12 referenced this issue Apr 4, 2023
mkfs.ext4 was run from lunar which enables it by default.

Add rw to initial kernel command line to fix read-only mount
interfering with first-boot.
@eslerm
Copy link
Member

eslerm commented Feb 14, 2024

Ubuntu Asahi has moved to 9 months of Ubuntu release support. Please ask to re-open issue if a supported version is affected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants