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

Upgrade dockerhost-equinix-ubuntu2004-armv82-1 to Ubuntu 24.04 LTS #3692

Closed
Tracked by #3588
sxa opened this issue Aug 1, 2024 · 2 comments · Fixed by #3703
Closed
Tracked by #3588

Upgrade dockerhost-equinix-ubuntu2004-armv82-1 to Ubuntu 24.04 LTS #3692

sxa opened this issue Aug 1, 2024 · 2 comments · Fixed by #3703
Assignees

Comments

@sxa
Copy link
Member

sxa commented Aug 1, 2024

Now that we have Ubuntu 24.04 we should look at upgrading one of the Altras up to this level. This will also support the requirements of #3498.

Noting that we have previously had some problems with the boot process on these machines so it is essential that whoever does this is comfortable with connecting to the console of these machines.

Part of #3588

@sxa
Copy link
Member Author

sxa commented Aug 9, 2024

@Haroon-Khel Can you add some notes in here for historic reference about some of the problems + solutions you hit while doing this please?

@Haroon-Khel
Copy link
Contributor

Haroon-Khel commented Sep 23, 2024

Ill describe the kernel panic and go through solutions.

After upgrading the kernel and all of the packages, the machine required a reboot. During the reboot the system hit a kernel panic, which took me to the GRUB prompt.

At the GRUB prompt I set the vmlinuz and initrd paths

grub> linux /boot/vmlinuz-$new_kernel_version-generic root=/path/to/root-filesystem
grub> initrd /boot/initrd.img-$new_kernel_version-generic

This allowed the system to boot, but still hit the kernel panic on subsequent reboot. To fix this, boot back up using the above steps in the GRUB prompt. Then run update the initramfs

~# update-initramfs -u -k $new_kernel_version-generic

Then the system should be fine after a reboot.

If during

grub> linux /boot/vmlinuz-$new_kernel_version-generic root=/path/to/root-filesystem
grub> initrd /boot/initrd.img-$new_kernel_version-generic

you do not know the path to the root filesystem, or the path has changed (for example the contents on /dev/sda1 are now on /dev/sda2 according to the GRUB prompt), then try booting into a previous kernel. If successful run

update-initramfs -u -k $new_kernel_version-generic

with $new_kernel_version-generic being the updated kernel version, not the one you have booted into. The system should then reboot fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
2 participants