Identify Failed Drive

[Drew Heath]

I ran into my first failed drive over the weekend, and am trying to figure out which drive it is. I am finding my failure after the fact in that I did not label or differentiate the serial numbers of the drives before hand.

A zpool status yields the following:

[root@ACD-ZFS-01] ~# zpool status
pool: ZFS-Vol-01
state: DEGRADED
status: One or more devices has been removed by the administrator.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Online the device using 'zpool online' or replace the device with
'zpool replace'.
scan: scrub repaired 0 in 2h54m with 0 errors on Sun Mar 5 02:54:28 2017
config:

NAME STATE READ WRITE CKSUM
ZFS-Vol-01 DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
gptid/2f130efb-ebfa-11e5-841f-9c5c8e8e6cfe ONLINE 0 0 0
gptid/2fd8caf9-ebfa-11e5-841f-9c5c8e8e6cfe ONLINE 0 0 0
gptid/30a7ebc1-ebfa-11e5-841f-9c5c8e8e6cfe ONLINE 0 0 0
gptid/31749bb4-ebfa-11e5-841f-9c5c8e8e6cfe ONLINE 0 0 0
gptid/3244742a-ebfa-11e5-841f-9c5c8e8e6cfe ONLINE 0 0 0
7805367242455134196 REMOVED 0 0 0 was /dev/gptid/33148c23-ebfa-11e5-841f-9c5c8e8e6cfe

errors: No known data errors

pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h1m with 0 errors on Fri Mar 10 03:46:17 2017
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
ada0p2 ONLINE 0 0 0

errors: No known data errors


I then took a look at glabel status, but assume that I am not seeing where the device is located because FreeNAS has disabled the drive due to the failure:


glabel status

Name Status Components
gptid/bef672f2-ebe6-11e5-a21b-9c5c8e8e6cfe N/A ada0p1
gptid/2f0621ec-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada1p1
gptid/2f130efb-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada1p2
gptid/2fcd7363-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada2p1
gptid/2fd8caf9-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada2p2
gptid/309b930e-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada3p1
gptid/30a7ebc1-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada3p2
gptid/316884e6-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada4p1
gptid/31749bb4-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada4p2
gptid/323934c2-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada5p1
gptid/3244742a-ebfa-11e5-841f-9c5c8e8e6cfe N/A ada5p2


Worst case, I can view the serial numbers for all the online drives, then by process of elimination find the odd drive out. I was curious however, if I was missing something, or if there was a better way of figuring out which drive failed. I am still running Corral and am waiting for Docker support to switch to the next version.

Thanks in advance for any guidance.

 

[danb35]

I am still running Corral

That's a bit of a problem, as you won't be able to replace the failed disk through the GUI.

Worst case, I can view the serial numbers for all the online drives, then by process of elimination find the odd drive out.

I think that's the best option at this point.

 

[Drew Heath]

That's a bit of a problem, as you won't be able to replace the failed disk through the GUI.

I am not quite ready to work on changing off of Corral yet. I also created a few Windows shares, so the migration will be pretty manual (which I am fine with, just will wait until Docker is ready). Is there an easy method from the CLI to replace the disk once I have it identified and replaced?

 

[nightshade00013]

https://forums.freenas.org/index.php?resources/identify-your-drives-by-serial-number.64/ should work fine for the command line to figure the serial numbers.

 

[Chris Moore]

https://forums.freenas.org/index.php?resources/identify-your-drives-by-serial-number.64/ should work fine for the command line to figure the serial numbers.

I thought Corral had that funky new CLI interface that they were still working on?

@Drew Heath , Corral was basically never a finished product and some features were never fully implemented.

 

[nightshade00013]

The basic shell should still be available. It's just under a menu in Corral if I remember right. I actually did not care for it all that much when I messed around with it on a test box so I didn't jump ship and was later glad I didn't.

 

[SweetAndLow]

You can replace a drive in corral using the freenas cli I wrote the steps in the wiki when it first came out. Not sure what happened to it though.

 

[Ericloewe]

You can replace a drive in corral using the freenas cli I wrote the steps in the wiki when it first came out. Not sure what happened to it though.

Most useful content from the wiki was moved over to the Corral subforum under documentation.

 

[Drew Heath]

Thanks everyone! I will hunt down the bad drive this evening and report back once I have a new drive in hand.

 

[Drew Heath]

I was able to get a new drive slivered via the command prompt. I plan to stay with Corral until docker features release, then will copy all of my data and rebuild the system from scratch. Thank you for all of the help!