- Thread Starter
- #26
It seems that this problem wasn't solved after all. After booting the FreeBSD VM a couple more times, it reverting to failing to import the zpool ("pool0") on boot.
To provide more context, it's a FreeBSD VM running under QEMU/KVM on a Fedora Linux hypervisor host. OpenZFS is also installed on the hypervisor and can see pool0 on the four physical disks that are being passed through to the FreeBSD VM. pool0 has been imported on the hypervisor before, but was properly exported before attempting to import it inside the VM.
To recap, pool0 can be manually imported just fine in the FreeBSD VM with either
I've tried adding echo statements to both /etc/rc.d/zfs and /etc/rc.d/zpool inside their name_start() functions and have set
This is perplexing.
To provide more context, it's a FreeBSD VM running under QEMU/KVM on a Fedora Linux hypervisor host. OpenZFS is also installed on the hypervisor and can see pool0 on the four physical disks that are being passed through to the FreeBSD VM. pool0 has been imported on the hypervisor before, but was properly exported before attempting to import it inside the VM.
To recap, pool0 can be manually imported just fine in the FreeBSD VM with either
zpool import pool0 or service zpool start, it just won't do it automatically at boot, even though zfs_load="YES" in /boot/loader.conf and zfs_enable="YES" in /etc/rc.conf.I've tried adding echo statements to both /etc/rc.d/zfs and /etc/rc.d/zpool inside their name_start() functions and have set
rc_debug="YES" in /etc/rc.conf, but I see no evidence that either rc script is being run at boot time. The only mention of "zfs" in the rc debug messages is Feb 14 14:19:55 filer2 root[2463]: /etc/rc.d/mountd: DEBUG: checkyesno: zfs_enable is set to YES., but it's the /etc/rc.d/mountd script outputting that.This is perplexing.