update-initramfs not working properly anymore (ZFS PVE host)

[Dulcow]

Hi there,

I made a mistake and install "grub-pc" package on an host with ZFS and it managed to remove all the UUIDs from /dev/disk/by-uuid/

root@pve-nuc12-1:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.5.13-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
WARN: /dev/disk/by-uuid/12F7-171D does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping

What can I do to fix this?

Thanks,

D.

 

[jsterr]

Hi there,

I made a mistake and install "grub-pc" package on an host with ZFS and it managed to remove all the UUIDs from /dev/disk/by-uuid/

root@pve-nuc12-1:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.5.13-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
WARN: /dev/disk/by-uuid/12F7-171D does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping

What can I do to fix this?

Thanks,

D.

Try proxmox-boot-tool clean https://forum.proxmox.com/threads/how-to-regenerate-etc-kernel-proxmox-boot-uuids.99333/

 

[Dulcow]

Thanks, it removed the warning but I cannot see any UUID in the folder:

root@pve-nuc12-1:/dev/disk/by-uuid# ls
16460683345362895815

And this command does not seem to do anything anymore. How do I force reinstalling grub on Proxmox?

root@pve-nuc12-1:/dev/disk/by-uuid# proxmox-boot-tool refresh
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..

 

[jsterr]

What does proxmox-boot-tool status say? For hostbootloader management see: https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_grub

 

[Dulcow]

Well, some stuff isn't there...

root@pve-nuc12-1:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi

 

[Dulcow]

And "grub-update" does not look good...

root@pve-nuc12-1:~# update-grub
Generating grub configuration file ...
W: This system is booted via proxmox-boot-tool:
W: Executing 'update-grub' directly does not update the correct configs!
W: Running: 'proxmox-boot-tool refresh'

Found linux image: /boot/vmlinuz-6.5.13-1-pve
Found initrd image: /boot/initrd.img-6.5.13-1-pve
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.5.11-8-pve
Found initrd image: /boot/initrd.img-6.5.11-8-pve
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.5.11-7-pve
Found initrd image: /boot/initrd.img-6.5.11-7-pve
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/nvme0n1p3.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
done

 

[Dulcow]

I reinstalled the machine today and I still see some funny stuff when I removed a previously installed kernel:

grub-probe: error: unknown filesystem

 

[LnxBil]

I reinstalled the machine today and I still see some funny stuff when I removed a previously installed kernel:

grub-probe: error: unknown filesystem

Why is this funny? Not every error is an error that should be tackled. The prober probes stuff and if something is not identifyable, you get this "error".

 

[Dulcow]

I have never seen this one before hence my reaction. I will forget about it then. Thanks ;-)

 

[LnxBil]

I have never seen this one before hence my reaction. I will forget about it then. Thanks ;-)

You will see it even more the more disk devices you attach. So don't worry.