Hello, Debian community! Decades-long Linux user. First-time caller. Thanks to anyone who reads this for trying to help me out!!!
I was upgrading a Debian 12 (bookworm) server, and it hung at the end:(I suspect the cause of the failure was my adding a line (bpffs /sys/fs/bpf bpf defaults 0 0) to /etc/fstab but not rebooting before running sudo apt upgrade.)
I was planning to comment out the new line in /etc/fstab and re-run update-initramfs with sudo update-initramfs -c -v -k 6.1.0-22-amd64, but I had to power cycle the unresponsive server, and when it came back, it dumped me into a grub> prompt, so I couldn't even comment out the line.
My root partition is present (on LVM):I guess I could just try booting with the ....old files. But I see the files on (hd0,gpt2), which is a separate partition that mounts to my filesystem as /boot.
I can see an earlier vmlinuz-6.1.0-18-amd64 I want to try to use (as well as all the 6.1.0-22-amd64 files too), but I can't figure out how to get grub to see them:I have a separate /boot partition and can't figure out how to reference it. /etc/fstab says:I have tried various forms of the following in grub, but all fail with error: file ... not found:Thank you for sharing any ideas you may have!
I was upgrading a Debian 12 (bookworm) server, and it hung at the end:
Then the server apparently crashed:update-initramfs: Generating /boot/initrd.img-6.1.0-22-amd64
Code:
...Processing triggers for fontconfig (2.14.1-4) ...Processing triggers for desktop-file-utils (0.26-1) ...Processing triggers for initramfs-tools (0.142) ...update-initramfs: Generating /boot/initrd.img-6.1.0-22-amd64Connection to 192.168.2.130 closed by remote host.Connection to 192.168.2.130 closed.Progress: [ 99%] [#####################################################################################################################################..]I was planning to comment out the new line in /etc/fstab and re-run update-initramfs with sudo update-initramfs -c -v -k 6.1.0-22-amd64, but I had to power cycle the unresponsive server, and when it came back, it dumped me into a grub> prompt, so I couldn't even comment out the line.
My root partition is present (on LVM):
Code:
grub> ls (lvm/server-name--vg-root)/lost+found/ boot/ etc/ media/ vmlinuz.old var/ bin usr/ ... /home ... initrd.img.old vmlinuz initrd.imgI can see an earlier vmlinuz-6.1.0-18-amd64 I want to try to use (as well as all the 6.1.0-22-amd64 files too), but I can't figure out how to get grub to see them:
Code:
grub> ls (hd0,gpt2)/lost+found/ efi/ ... config-6.1.0-18-amd64 vmlinuz-6.1.0-18-amd64 initrd.img-6.1.0-18-amd System.map-6.1.0-18-amd64 ... config-6.1.0-22-amd64 vmlinuz-6.1.0-22-amd64 initrd.img-6.1.0-22-amd System.map-6.1.0-22-amd64 Code:
# /boot was on /dev/nvme0n1p2 during installationUUID=8b47..... /boot ext2 defaults 0 2Code:
grub> linux /vmlinuz-6.1.0-18-amd64 root=/dev/nvme0n1p2error: file `/vmlinuz-6.1.0-18-amd64` not found.grub> linux /boot/vmlinuz-6.1.0-18-amd64 root=/dev/nvme0n1p2error: file `/boot/vmlinuz-6.1.0-18-amd64` not found.Statistics: Posted by JamesLavin — 2024-07-01 00:26 — Replies 3 — Views 83