[SOLVED] PVE 8.4.5, ZFS rpool, Something's really wrong with boot process

bofh666

Renowned Member
Apr 5, 2017
10
3
68
43
Hi there! :)

I've got Hetzner dedicated server with two identical NVMe drives with PVE default zfs (RAID1) installation which was working flawlessly for years. Last time I've upgraded PVE 11 days ago to 8.4.5, everything went well and the server came online after reboot as expected.

Yesterday the server became unavailable suddenly. Reboot which helped in such (rare) cases didn't at this time, but in Recovery mode (kind of Live CD) the server booted just fine, so I've decided to request IP KVM for troubleshooting.

After Recovery mode the server didn't boot because run-init wasn't able to import rpool as it was previously in use from another system (Recovery mode), which is expected.
I've imported it manually as suggested: zpool import rpool -f and got filesystem 'rpool/ROOT/pve-1' cannot be mounted at /root//mnt' due to canonicalization error: No such file or directory message.
I've mounted the filesystems as suggested and exited: zfs mount -a; exit. And got some Free initramfs and switch to another root fs messagess (guess count is equal to the number of filesystems in the rpool) followed by No init found. Try passing init= bootarg error.
Then I've tried to exit one more time and got kernel panic. Next reboot has been followed by kernel panic.

I've booted into Rescue mode one more time to ensure no hardware errors in dmesg output, fine smartctl output for both of drives and to do zpool scrub rpool just in case — no errors found.

After that all boot attempts stuck at cannot be mounted at /root//mnt' due to canonicalization error. Looks like something is missing between slashes... Tried to boot previous Grub2 entry with same result.

Didn't find anything relevant on the forum and over Internet. Desperately need adviсe on further troubleshooting!

UPD: Found this thread. I do use Docker in one of my VMs, which virtual disk resides on ZFS storage...
 

Attachments

  • screenshot_1754561321757.jpg
    screenshot_1754561321757.jpg
    98.9 KB · Views: 8
  • screenshot_1754561590804.jpg
    screenshot_1754561590804.jpg
    90.4 KB · Views: 7
  • screenshot_1754562133504.jpg
    screenshot_1754562133504.jpg
    71 KB · Views: 7
  • screenshot_1754563475408.jpg
    screenshot_1754563475408.jpg
    98.9 KB · Views: 7
  • screenshot_1754577682340.jpg
    screenshot_1754577682340.jpg
    94.7 KB · Views: 8
Last edited:
Managed to resolve the issue. It appeared that I've messed up with root zvol mountpoint when was troubleshooting in Recovery mode. So
Code:
zpool import -f rpool
zfs set mountpoint=/ rpool/ROOT/pve-1
in initramfs cli and reboot fixed boot process.
 
Last edited:
Managed to resolve the issue. It appeared that I've messed up with root zvol mountpoint when was troubleshooting in Recovery mode. So
Code:
zpool import -f rpool
zfs set mountpoint=/ rpool/ROOT/pve-1
in initramfs cli and reboot fixed boot process.
You saved my life. I thought I blew away the pool somewhere messing around with chroot recovery instructions. Thank you!