"WARNING: The volume volume1 (ZFS) status is UNKNOWN"; 3 of 4 hard disks not seen

[wdockery]

Hello, I am a relative newbie--first post, limited experience, intermediate Unix user. My family uses 6 laptops and a couple of desktops--mostly Macs. I built a computer in 2014 and installed FreeNAS to serve as storage for backups of all of these devices created with Retrospect Desktop for Mac. It is in an office in my house--climate controlled, sitting on thin carpet. Besides the Retrospect share, I also created a volume on FreeNAS, accessible via afp://, to which laptops could save files. Once I got FreeNAS up and running and watched the FreeNAS video once, I left the box alone. Whenever I opened my laptop, the shared volume, "freenas" would pop up in my "network shares" sidebar. I never needed to access Retrospect backups. I assumed all was well. The last time I noticed "freenas" in my Mac's sidebar was about 3 weeks ago; then I sort of tuned out and didn't notice.

Two days ago, I needed to save something to "freenas" and noticed that it wasn't in my Mac OS sidebar; I couldn't even connect to the share. I logged onto the FreeNAS web admin page (first time in months) and saw the blinking yellow light.

As directed in these forums, I ran a few commands from the command line. smartctl -t long is pending (has 2 more hours to run).

I would appreciate advice on next steps. If the advice pertains to additional shell commands, I would need specific directions. If it pertains to removing drives, swapping cables, etc, I will need specific directions also. This is all new territory for me.

The (lost?) data is important but not critical--it's a backup; I can make a new one, but it will take time.

I placed my system specifications in my signature section. If the system components/design is bad, then please let me know.

Thanks for your help--


[root@freenas] /var/log# smartctl -a /dev/ada0

smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p12 amd64] (local build)

Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===

Model Family: Seagate Barracuda 7200.14 (AF)

Device Model: ST3000DM001-1CH166

Serial Number: W1F5BZFC

LU WWN Device Id: 5 000c50 077d9998c

Firmware Version: CC29

User Capacity: 3,000,592,982,016 bytes [3.00 TB]

Sector Sizes: 512 bytes logical, 4096 bytes physical

Rotation Rate: 7200 rpm

Device is: In smartctl database [for details use: -P show]

ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b

SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Tue Nov 29 09:21:18 2016 CST


==> WARNING: A firmware update for this drive may be available,

see the following Seagate web pages:

http://knowledge.seagate.com/articles/en_US/FAQ/207931en

http://knowledge.seagate.com/articles/en_US/FAQ/223651en


SMART support is: Available - device has SMART capability.

SMART support is: Enabled


=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

See vendor-specific Attribute list for marginal Attributes.


General SMART Values:

Offline data collection status: (0x82) Offline data collection activity

was completed without error.

Auto Offline Data Collection: Enabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: ( 584) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 1) minutes.

Extended self-test routine

recommended polling time: ( 317) minutes.

Conveyance self-test routine

recommended polling time: ( 2) minutes.

SCT capabilities: (0x3085) SCT Status supported.


SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 73595008

3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0

4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 23

5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0

7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 32658146

9 Power_On_Hours 0x0032 080 080 000 Old_age Always - 18373

10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0

12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 23

183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0

184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0

187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0

188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0

189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0

190 Airflow_Temperature_Cel 0x0022 056 043 045 Old_age Always In_the_past 44 (0 203 49 22 0)

191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0

192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 18

193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 47

194 Temperature_Celsius 0x0022 044 057 000 Old_age Always - 44 (0 21 0 0 0)

197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 18329h+25m+16.220s

241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 10624514500

242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 70890188942


SMART Error Log Version: 1

No Errors Logged


SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Completed without error 00% 18366 -


SMART Selective self-test log data structure revision number 1

SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

1 0 0 Not_testing

2 0 0 Not_testing

3 0 0 Not_testing

4 0 0 Not_testing

5 0 0 Not_testing

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.


[root@freenas] /var/log# smartctl -t long /dev/ada0 [pending]


[root@freenas] /var/log# camcontrol devlist

Code:

<ST3000DM001-1CH166 CC29>		  at scbus2 target 0 lun 0 (pass0,ada0)
<SanDisk Cruzer Fit 1.27>		  at scbus5 target 0 lun 0 (pass1,da0)

[root@freenas] /var/log# zpool status -v
no pools available


[root@freenas] /var/log# glabel status
Name Status Components
gptid/7a449a4b-4e84-11e4-aaf8-b8975a5fd7e1 N/A ada0p2
ufs/FreeNASs3 N/A da0s3
ufs/FreeNASs4 N/A da0s4
ufs/FreeNASs1a N/A da0s1a


[root@freenas] /var/log# gpart show
=> 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)

=> 63 15633345 da0 MBR (7.5G)
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 11728416 - free - (5.6G)

=> 0 1930257 da0s1 BSD (942M)
0 16 - free - (8.0k)
16 1930241 1 !0 (942M)



[root@freenas] /var/log# gpart status
Name Status Components
ada0p1 OK ada0
ada0p2 OK ada0
da0s1 OK da0
da0s2 OK da0
da0s3 OK da0
da0s4 OK da0
da0s1a OK da0s1

 

[danb35]

Things are looking bad--as far as your system knows, it only has one hard drive connected. Your RAIDZ2 volume will tolerate the loss of two drives, but not three. Nothing's looking obviously wrong with the one drive you have left, other than being a bit warmer than we prefer to see and only having had one SMART test run in its lifetime, but the other three are gone. And the Seagate 3 TB drives have a pretty awful track record.

Other than complete failure of the drives, you could be looking at a SATA port and/or cabling issue, or possibly even power. Try different SATA cables if you have them, try connecting the "dead" drives to different ports on your motherboard, try a different power supply if possible. Can you tell if the other drives are even spinning?

 

[Z300M]

The ST3000DM001 got Seagate a very bad reputation, with the result that some people (but not I) now avoid Seagate like the plague.

But wait for someone more knowledgeable than I to suggest what to do next.

 

[wdockery]

Things are looking bad--as far as your system knows, it only has one hard drive connected. Your RAIDZ2 volume will tolerate the loss of two drives, but not three. Nothing's looking obviously wrong with the one drive you have left, other than being a bit warmer than we prefer to see and only having had one SMART test run in its lifetime, but the other three are gone. And the Seagate 3 TB drives have a pretty awful track record.

Other than complete failure of the drives, you could be looking at a SATA port and/or cabling issue, or possibly even power. Try different SATA cables if you have them, try connecting the "dead" drives to different ports on your motherboard, try a different power supply if possible. Can you tell if the other drives are even spinning?

I'll listen to see whether the disks are spinning. I read somewhere that there may be an indicator light on these drives, but I don't recall seeing it. Honestly, I have not been back inside of the chassis since 2014.

I'll order some new SATA cables and try swapping them with the current ones. Certain types I should look for, or avoid?

My motherboard has only 4 SATA ports, so I'm not sure I can try swapping ports.

A few questions about going into the chassis to troubleshoot:

1. At this point, I'm such a novice that I'm not even sure which of the 4 disks in the chassis is ada0. And I don't know which of the other disks would be ada1, 2, 3, or whatever numbering system would be used. Would they be numbered according to the ports on the motherboard?
2. If I start unplugging and removing drives, will I jeopardize any chance of reassembling volume1? Are there right and wrong ways to do this, given the RAIDZ2 configuration?
3. If I wanted to test the drives outside of the chassis, is there a way I could plug them into my Mac laptop? What type of cables (something for power, and something to plug the drive into a USB port) would I need?
4. And what would I be looking for?

And other questions going forward:

1. Will this recur?
2. Is this common (3 out of 4 drives dead at 2 years)?
3. Is it something I did with my build? Inadequate cooling? Spilled coffee? (none recalled, but I may smell coffee in the chassis.) Do I need to start over with a fundamentally different build?
4. What is a smarter set up that would have notified me of problems? (I never activated any email notifications.)

 

[SweetAndLow]

The things that jump out at me are:
1. very unsuitable hardware
2. no smart tests running

make sure your drives are plugged in and powered up. But the smart errors are pretty clear that the drives have failed.

 

[depasseg]

My motherboard has only 4 SATA ports, so I'm not sure I can try swapping ports.

You can move things around in an orderly fashion to see if the problem is with the Drive, cable, or port.

I'm not even sure which of the 4 disks in the chassis is ada0.

Compare the serial number from the smartctl command to the S/N printed on the disk.

Would they be numbered according to the ports on the motherboard?

No. The naming is pseudo random and doesn't correspond to physical ports on the board.

will I jeopardize any chance of reassembling volume1?

No. Each ZFS drive has a label that identifies the pool that it's a member of. The order or method that drives connect isn't important.

What is a smarter set up that would have notified me of problems? (I never activated any email notifications.)

SMART Short tests should be run daily. SMART Long tests should be run weekly, and email alerts should be configured and tested.

 

[Robert Trevellyan]

The question is, how did you end up with 3 disks failed overnight?

One possible scenario is ... you didn't, but rather, you don't have email alerts set up. Over time, two drives failed and everything continued working but with all redundancy gone. The GUI would have had a big red alert light, if you had logged in. Now, a third drive has failed, and ... :(

Pure speculation, but it fits the circumstances.

 

[Bidule0hm]

44 °C is too hot for the drives, probably why they failed in the first place.

 

[Robert Trevellyan]

Device Model: ST3000DM001-1CH166

 

[wdockery]

Things are looking bad--as far as your system knows, it only has one hard drive connected. Your RAIDZ2 volume will tolerate the loss of two drives, but not three. Nothing's looking obviously wrong with the one drive you have left, other than being a bit warmer than we prefer to see and only having had one SMART test run in its lifetime, but the other three are gone. And the Seagate 3 TB drives have a pretty awful track record.

Other than complete failure of the drives, you could be looking at a SATA port and/or cabling issue, or possibly even power. Try different SATA cables if you have them, try connecting the "dead" drives to different ports on your motherboard, try a different power supply if possible. Can you tell if the other drives are even spinning?

Do you like your current hardware set-up? I ask because a have received comments that my home-built computer is poorly designed. (I found it on an internet blog.) Would you be willing to share how well your system has performed and what would be the approximate cost of my acquiring and assembling the parts? Thanks.

 

[JackShine]

If I were u, id count my losses, backup as much data as u can and start again.

No use beating a dead horse.