Failed to start Import ZFS pool <pool-name>

salpot

Member
Nov 17, 2021
19
13
23
45
Greetings,

I keep getting "Failed to start Import ZFS pool hddmirror." when Proxmox is booting. The pool is just fine when the login shows up after a minute or so of waiting. I found the following in syslog:

Code:
Nov 17 18:58:10 kong systemd[1]: Starting Import ZFS pool hddmirror...
...
...
Nov 17 18:58:10 kong zpool[950]: cannot import 'hddmirror': no such pool available
Nov 17 18:58:10 kong systemd[1]: zfs-import@hddmirror.service: Main process exited, code=exited, status=1/FAILURE
Nov 17 18:58:10 kong systemd[1]: zfs-import@hddmirror.service: Failed with result 'exit-code'.
Nov 17 18:58:10 kong systemd[1]: Failed to start Import ZFS pool hddmirror.

hddmirror is the only pool with 2 drives in mirror Raid.

I tried both suggestions here https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Grub_boot_ZFS_problem but still having the same problem.
Tried both at the same time and separately. I even changed the time in ZFS_INITRD_PRE_MOUNTROOT_SLEEP to 10, 20 and 30.

Any ideas what else to try?

I am currently on VE 7.1

Thank you
 
Last edited:
hi,


hddmirror is the only pool with 2 drives in mirror Raid.
does the pool show up in zpool list?

I tried both suggestions here https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Grub_boot_ZFS_problem but still having the same problem.
just checking, have you changed the kernel version in this command to match yours: b) edit /etc/default/zfs, set ZFS_INITRD_PRE_MOUNTROOT_SLEEP='4', and then issue a "update-initramfs -k 4.2.6-1-pve -u" ?
you can check your kernel version with pveversion command.
 
hi,



does the pool show up in zpool list?


just checking, have you changed the kernel version in this command to match yours: b) edit /etc/default/zfs, set ZFS_INITRD_PRE_MOUNTROOT_SLEEP='4', and then issue a "update-initramfs -k 4.2.6-1-pve -u" ?
you can check your kernel version with pveversion command.
Hello,

Yes, the pool shows up in zpool list and it is working normally. I also did use the kernel version that is currently running. No need to use the -k option in the first place, it'll just use the current running version.