August 27, 201312 yr Hi All, Just followed the troubleshooting section of the site, and spotted the highlighted problems that the guide says to look out for. Seems that the drive is well and truly failed/failing. It's quite new (4ish months old) so I will probably return it, but before I do so, can someone call time on it (as I'm not a doctor ) Conversely, If it does look fine, advice for my next steps would be greatly appreciated. Many Thanks, Austin root@Tower:~# smartctl -a -d ata /dev/sde smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DM001-9YN164 Serial Number: ****** (OBSCURED BY AUSTINGEORGE) Firmware Version: CC4H User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Tue Aug 27 23:00:33 2013 BST 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 General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 592) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) 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 116 099 006 Pre-fail Always - 101225448 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2803 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 8645921123 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 8370 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 2015 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 001 001 000 Old_age Always - 414 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 084 084 000 Old_age Always - 16 190 Airflow_Temperature_Cel 0x0022 061 055 045 Old_age Always - 39 (Min/Max 36/39) 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 - 100 193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 9160 194 Temperature_Celsius 0x0022 039 045 000 Old_age Always - 39 (0 17 0 0) 197 Current_Pending_Sector 0x0012 038 038 000 Old_age Always - 10304 198 Offline_Uncorrectable 0x0010 038 038 000 Old_age Offline - 10304 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 218347547399844 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 140971955382684 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 166230312339591 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 8368 hours (348 days + 16 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 71 00 00 00 00 40 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 00 00 00 00 00 ff 28d+05:24:08.322 NOP [Abort queued commands] c8 00 f8 17 66 00 e0 00 28d+05:23:37.392 READ DMA c8 00 10 07 66 00 e0 00 28d+05:23:37.392 READ DMA 25 00 48 bf 64 00 e0 00 28d+05:23:37.390 READ DMA EXT c8 00 20 9f 64 00 e0 00 28d+05:23:37.390 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 8370 20704 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.
August 27, 201312 yr Most of the parameters look fine, until you get near the bottom of the table! It does not look as if it has failed yet, but certainly appears to be failing. With bad sector counts that high, there must be some mechanical damage inside, and I would not trust it at all. It looks like you may still be able to recover some of the files off it though. Grab the most important, then the almost as important, then the increasingly lesser files until you either have everything you want off it, or it has quit completely.
August 27, 201312 yr Author Hi Rob, Thanks for your diagnosis! I'll definitely grab as much as I can. Is it just a matter of mounting the disk as a share, then copying files to another disk? Also, when i'm reading the airflow temp, should i read the figures as that it reached 55degC, with nominal 45degC? Trying to se if my enclosure is too restrictive, as it does get quite warm. Thanks again! Austin
August 27, 201312 yr I'll definitely grab as much as I can. Is it just a matter of mounting the disk as a share, then copying files to another disk? If it's not a part of the array, then you will have to manually mount it, or mount it with UnMENU. I'm not a Linux guru, so perhaps others can help better with that. I couldn't find the info on mounting I thought we had. Once mounted, use Midnight Commander (mc at the command line) to copy files. See Transferring Files Within the unRAID Server for a little help. Also, when i'm reading the airflow temp, should i read the figures as that it reached 55degC, with nominal 45degC? Trying to se if my enclosure is too restrictive, as it does get quite warm. If I recall correctly, that WORST of 55 is interpreted as 100-55 (so that as the temp gets worse, WORST value will decrease), which makes it equal to 45degC, the highest temp measured. Currently, it is 39, which is a little warm, but not excessive. If you can improve the cooling, do so.
August 28, 201312 yr Author It is part of the array. My setup consists of 6x2Gb drives (of which, 1 has failed), and a 320gb cache drive. The remainder of the array starts fine, but the failed drive doesn't start with the array and stays offline when looking at the tower array menu. Surely as I have a parity drive I can just reconstruct the array by replacing the failed drive with a new one? Also, amazon have accepted the return and a new one should pop through my door tomorrow. Regarding the cooling, as the enclosure is quite prone to vibrations and dust, I reduced the fan speeds considerably. I'll up them slightly and hopefully it'll drop the temps a tad.
August 28, 201312 yr If it's part of the array, that's great! When you start the array, UnRAID will either mount it, if it can, or create a virtual version of it, with all of its contents reconstructed from the other data drives and the parity drive. You will have safe access to everything on that drive, in case you need anything. But replace it as soon as you can. Many of us prefer to PreClear a new drive first, to ensure it's a good drive. That will take a little more time. Until the new drive has been rebuilt in its place, I would limit all other reading and writing to the array, just for safety. It's not that you can't make changes to the array now, but if one drive is down, then you no longer have parity protection against an additional drive going down. Some don't feel this caution is necessary, perhaps I'm more cautious than most.
August 29, 201312 yr Author Ah right, that's fine. I thought that's how it worked. Your comment about copying things off the failed drive threw me. Glad I went for a parity drive now. I'm a bit of a tight-ass when it comes to redundancy. As for stopping other drives from failing; the server is just hosting torrent uploads and an xbmc media share, so I've just shut the whole thing down. I'll put it on to pre-clear tonight when I get the drive Thanks for all your help Rob!
Archived
This topic is now archived and is closed to further replies.