My server insists on trying to install non-existant pools at boot. I came across this old post from 2013. The last 2 posts in that thread say that /boot/zfs/zpool.cache should be a symlink to /data/zfs/zpool.cache. But in my case it isn't. It looks like corrective action is needed, but I'm not 100% sure of the implications of doing that, to dive in without checking.
Relevant dmesg:
Is that still safe (we're now 2019 not 2013), and do I need to do more?
Relevant dmesg:
Beginning ZFS volume imports
Importing 13905614667333621281
cannot import '13905614667333621281': no such pool available
cannot import '13905614667333621281': no such pool available
Importing **********
Relevant command output:# ls -la /boot/zfs/zpool.cache
-rw-r--r-- 1 root wheel 1,792 2019-01-10 17:19:48 /boot/zfs/zpool.cache
# ls -la /data/zfs/zpool.cache
-rw-r--r-- 1 root www 11,456 2019-01-10 17:26:09 /data/zfs/zpool.cache
# zpool get cachefile
NAME PROPERTY VALUE SOURCE
********* cachefile /data/zfs/zpool.cache local
******** cachefile /data/zfs/zpool.cache local
freenas-boot cachefile - default
# sqlite3 /data/freenas-v1.db "select * from storage_volume"
<lists just the correct 2 pools that should exist>
What's needed to fix this? Delete the boot cache and recreate as a smylink to the /data one, as in that thread?Is that still safe (we're now 2019 not 2013), and do I need to do more?