Somebody rushed a system update interrupting it before completion. The result was not bootable. So I reinstalled Rocky 8 and ran the 45drives scripts. End result is that ZFS is there but won’t mount the pool at boot. The complaint that zpool command is missing is incorrect.
At first, I thought there was a dinged configuration item. Inspecting the zfs-import-scan.service file, it looked unremarkable. Clicking the restart button for the service, it starts and ZFS pool mounts as expected.
At this point it still needs zfs mount -a issued.
Once mounts are complete, containers can be started.
At second though, is there a race? Or a wait-for-something returning early?
DVR storage is not there until the pool starts. (Channels from FancyBits).
Or at third thought, a premature release from a step preceding ZFS startup? I need a hint for what should be checked next.
Here’s the log entry for zfs-import-scan service, timestamps deleted
/usr/local/sbin/zpool is there, alive and well. Assume it is doing something exotic like zpool import -a which works. Without the pool there, my DVR doesn’t come up and other annoyances.
Failed to start Import ZFS pools by device scanning.
zfs-import-scan.service: Failed with result ‘exit-code’.
zfs-import-scan.service: Main process exited, code=exited, status=203/EXEC
zfs-import-scan.service: Failed at step EXEC spawning /usr/local/sbin/zpool: No such file or directory
zfs-import-scan.service: Failed to execute command: No such file or directory