All pools FAULTED after crash/hard reboot

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
From each drive? It's a single SMR drive so would that even possibly work?
For that pool, but the initial post shows that all three of pools (M2_fast01, MirrorPool, and SingleDrive12TB) are FAULTED.

@DanteUseless it may be time to start with the -fXT <txgnumber> testing.

SingleDrive12TB is showing 1372491 as the current txg, so start "walking backwards" from there. Both MirrorPool devices agree on 5940069. You'll need to manually zdb -l /dev/nvmeXp2 (where X is the number of your M2_fast01 member device) because it won't have been polled in the /dev/sdX run-through.

Try with -nfXT first as it should give you a summary of "pool will be rolled back to (timestamp)" - if it's a time before the hard reboot, it may be more successful. If you're okay with that time, remove the -n and just use -fXT <txgnumber>
 
Top