So presuming your system won’t boot have you tried switching to the second SSD in your boot mirror? You would most likely need to change this in your bios.
Seems unlikely that both your boot SSDs would fail at exactly the same time.
This is a recurring OpenZFS issue I’ve seen a few times, though not 100% certain on the exact cause. Seems to be more common on Non-ECC systems during very large transfers.
If you’re able to boot with enough disks disconnected to cause the pool to fail to import, reconnect them after boot and check if you can import the pool readonly via zpool import tank -o readonly=on
I’d hope you have backups in place, however if not, you should copy off any important data while the pool is imported readonly. Keep in mind GUI won’t be able to see/interact with this so you will need to pull data via something like SFTP.
If that’s successful, your data is most likely fine. You can then zpool export tank, enable the zfs_recover tunable (sudo echo 1 > /sys/module/zfs/parameters/zfs_recover) and try importing via the GUI.
Assuming that import succeeds, leave it for a day or two and then see if it imports as normal after a reboot.
Edit: This post details the same but is better laid out than mine, worth referencing that too
I’m referring to your data pool, have you attempted booting with the data pool disks disconnected?
TrueNAS will attempt to import all pools as part of the init/startup process, so the ZFS panic looks like it could well have been thrown as part of initial pool import
Edit: Not to say it couldn’t be your boot-pool, but best to confirm. If it boots no problem with the disks disconnected, then you know for sure where the problem is.
Okay, amazing, if the data disks are intact that saves a lot of hassle as you don’t have any critical data at risk, just a matter of pulling out the configuration now
Let’s give this a go then seeing as you don’t have config:
On the boot page, press “e” on your primary boot option:
Add zfs.zfs_recover=1 to the end of the line then press ctrl+x to boot. With the data disks disconnected, that should hopefully get you into the system and able to download a config backup. I’d recommend a reinstall after the fact, technically you could leave it for a bit as I mentioned earlier, but considering how easy it is to reinstall once you have a configuration backup better safe than sorry!
Hi Henry,
thank you. So if I do this command with the added parameter then it should boot with network and I can logon and backup the config?
It will be tomorrow morning now before I can nick one of the kids monitors
That’s the goal, yes. As with all things I can’t give you a 100% guarantee, but it should be your best shot at getting into a bootable state to grab a copy of the config.
In future, I’d recommend either taking a config backup after any major configuration changes are made, or deploying a script that can backup config automatically to your storage pool (see: configuration-backup).
