Hi. I have a 6 drive RAID-Z2 array, which has been working fine for several months. A few days ago, I logged in and saw that the array was degraded, and that one particular drive had had errors. The drive was only 4 months old, so I figured it must be broken, so I shut down the FreeNAS computer, removed that drive, put it in another computer and ran SeaTools on it to diagnose it. After quite a few hours, SeaTools said everything was cool, so I decided to plug the drive back in to FreeNAS and fire it up. I booted to the USB stick, like always, but it hung up on 'mountd', and wouldn't continue to boot. I left it overnight, and it stayed stuck on that item. At this point I started to panic, and downloaded a copy of the latest stable FreeNAS, wrote it to another USB drive, and tried to boot off of that. It booted, but when I tried to Auto-Import the RAID-Z2, it sits on Please Wait for about 20 minutes then says "An error has occured". After this, I can (sort of) access the array from the command line..."zpool status" lists it, which it didn't before, but it lists it with two unavailable drives. Below are the results of some commands I've noticed people ask for in similar situations to mine, all taken after the Auto-Import errored out:
With two drives unavailable, I'm terrified that I will do something else wrong and lose my data. Where can I go from here?
Code:
[root@freenas] ~# zpool status -v
pool: MAIN
state: DEGRADED
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: http://www.sun.com/msg/ZFS-8000-HC
scan: scrub repaired 144M in 6h32m with 0 errors on Fri Feb 15 20:02:12 2013
config:
NAME STATE READ WRITE CKS UM
MAIN DEGRADED 0 0 1
raidz2-0 DEGRADED 0 0 6
gptid/3e54ea70-1e5d-11e2-b155-00261889a36e ONLINE 0 0 0
952549345672949843 UNAVAIL 0 0 0 was /dev/gptid/3f04f9e9-1e5d-11e2-b155-00261889a36e
13589355565508211589 UNAVAIL 0 0 0 was /dev/gptid/85232dd5-77b3-11e2-9414-00261889a36e
gptid/feb27aa0-3f54-11e2-8fb8-00261889a36e ONLINE 0 0 0
gptid/40ca2b7b-1e5d-11e2-b155-00261889a36e ONLINE 0 0 0
gptid/0c4307e2-21f7-11e2-95fd-00261889a36e ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
<metadata>:<0x1d>Code:
[root@freenas] ~# gpart show
=> 63 3935169 da1 MBR (1.9G)
63 1930257 1 freebsd [active] (942M)
1930320 63 - free - (31k)
1930383 1930257 2 freebsd (942M)
3860640 3024 3 freebsd (1.5M)
3863664 41328 4 freebsd (20M)
3904992 30240 - free - (14M)
=> 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)
Segmentation faultCode:
[root@freenas] ~# glabel status
Name Status Components
ufs/FreeNASs3 N/A da1s3
ufs/FreeNASs4 N/A da1s4
gptid/3e54ea70-1e5d-11e2-b155-00261889a36e N/A ada0p2
gptid/feb27aa0-3f54-11e2-8fb8-00261889a36e N/A ada3p2
gptid/40ca2b7b-1e5d-11e2-b155-00261889a36e N/A ada4p2
gptid/0c4307e2-21f7-11e2-95fd-00261889a36e N/A ada5p2
ufs/FreeNASs1a N/A da1s1aCode:
[root@freenas] ~# camcontrol devlist <ST3000DM001-9YN166 CC4H> at scbus1 target 0 lun 0 (ada0,pass0) <ST2000DM001-9YN164 CC4B> at scbus2 target 0 lun 0 (pass1,ada1) <ST2000DM001-9YN164 CC4B> at scbus3 target 0 lun 0 (ada2,pass2) <ST3000DM001-1CH166 CC24> at scbus4 target 0 lun 0 (ada3,pass3) <WDC WD15EADS-00P8B0 01.00A01> at scbus5 target 0 lun 0 (ada4,pass4) <WDC WD30EZRX-00MMMB0 80.00A80> at scbus6 target 0 lun 0 (ada5,pass5) <ASMT 2105 0> at scbus7 target 0 lun 0 (pass6,da0) <Mass Storage Device \001\000\000?> at scbus8 target 0 lun 0 (pass7,da1)
With two drives unavailable, I'm terrified that I will do something else wrong and lose my data. Where can I go from here?
