-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
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. |
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! |
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. |
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
|
Also, running |
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.
Ubuntu Asahi has moved to 9 months of Ubuntu release support. Please ask to re-open issue if a supported version is affected. |
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:MacOS is still working though.
The text was updated successfully, but these errors were encountered: