zpool disks showing offline

Michael C.

Cadet
Joined
Sep 27, 2014
Messages
3
I was in the process of replacing a drive. I took the bad drive offline, then replaced it with a new one of the same exact size and type. I then put it online, and the system locked up. I let it sit for 24 hours just in case, then had to reboot it. Upon rebooting, when I try to import the POOL it says make sure the disks are attached. I have pasted details below, any help would be appreciated.

FreeNAS-11.2-U7



# zpool import
pool: WD3TBR6
id: 18407972644127781829
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see: http://illumos.org/msg/ZFS-8000-3C
config:

WD3TBR6 UNAVAIL insufficient replicas
raidz2-0 UNAVAIL insufficient replicas
gptid/9902fe78-4b1b-11e4-88f8-0cc47a0e6b38.eli ONLINE
gptid/99be7de2-4b1b-11e4-88f8-0cc47a0e6b38.eli ONLINE
gptid/9a7a5574-4b1b-11e4-88f8-0cc47a0e6b38.eli ONLINE
17898062518865300450 UNAVAIL cannot open
8305505796969903960 UNAVAIL cannot open
4733809732980269042 OFFLINE




<WDC WD30EFRX-68EUZN0 80.00A80> at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD30EFRX-68EUZN0 80.00A80> at scbus1 target 0 lun 0 (pass1,ada1)
<WDC WD30EFRX-68EUZN0 80.00A80> at scbus2 target 0 lun 0 (pass2,ada2)
<WDC WD30EFRX-68EUZN0 80.00A80> at scbus3 target 0 lun 0 (pass3,ada3)
<WDC WD30EFRX-68EUZN0 80.00A80> at scbus4 target 0 lun 0 (pass4,ada4)
<WDC WD30EFRX-68EUZN0 82.00A82> at scbus5 target 0 lun 0 (pass5,ada5)
<Corsair Voyager 3.0 000A> at scbus7 target 0 lun 0 (pass6,da0)



=> 34 5860533101 ada0 GPT (2.7T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 5856338696 2 freebsd-zfs (2.7T)
5860533128 7 - free - (3.5K)

=> 34 5860533101 ada1 GPT (2.7T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 5856338696 2 freebsd-zfs (2.7T)
5860533128 7 - free - (3.5K)

=> 34 5860533101 ada2 GPT (2.7T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 5856338696 2 freebsd-zfs (2.7T)
5860533128 7 - free - (3.5K)

=> 34 5860533101 ada3 GPT (2.7T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 5856338696 2 freebsd-zfs (2.7T)
5860533128 7 - free - (3.5K)

=> 34 5860533101 ada4 GPT (2.7T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 5856338696 2 freebsd-zfs (2.7T)
5860533128 7 - free - (3.5K)

=> 34 31326141 da0 GPT (15G)
34 8190 - free - (4.0M)
8224 1024 1 freebsd-boot (512K)
9248 31316920 2 freebsd-zfs (15G)
31326168 7 - free - (3.5K)
 

mroptman

Dabbler
Joined
Dec 2, 2019
Messages
23
This frequently happened to me when replacing disks and the likely culprit always has been SATA power or data cables that were nudged just enough to become disconnected, but not appear so.

After firmly checking all drive cables, you could also have bad cables. Had a SAS to SATA breakout cables go dead randomly; replaced the cable and all 4 drives came back online.

You have raid-z2, so you only need one of the three offline/unavail drives to online the pool. If the pool comes back online, it would be a great time to ensure you have a backup of the pool since there could be multiple drive failures that could fault the whole pool.
 
Top