August 28, 201411 yr I currently have a drive that appears to be failing. There are a lot of signs pointing towards this including: 1.) Upon booting up the server, the motherboard reports AHCI Device Error on port3. This same SATA port works fine with another hard drive. 2.) Often there is trouble mounting/remounting the drive. 3.) The smart report shows an increasing Reallocated Sector Count. Currently it's only at 1, so I'm guessing this isn't a catastrophic problem (yet). smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA300 Serial Number: 33VHR7WAS LU WWN Device Id: 5 000039 ff4c7251b Firmware Version: MX6OABB0 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: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s) Local Time is: Thu Aug 28 10:37:42 2014 EDT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (23369) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 390) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 085 085 016 Pre-fail Always - 17367040 2 Throughput_Performance 0x0005 139 139 054 Pre-fail Offline - 71 3 Spin_Up_Time 0x0007 146 146 024 Pre-fail Always - 418 (Average 366) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 707 5 Reallocated_Sector_Ct 0x0033 001 001 005 Pre-fail Always FAILING_NOW 2004 7 Seek_Error_Rate 0x000b 089 089 067 Pre-fail Always - 14 8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 6877 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 27 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1178 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1178 194 Temperature_Celsius 0x0002 136 136 000 Old_age Always - 44 (Min/Max 18/57) 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 3207 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 8 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 24 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 181 (device log contains only the most recent five errors) 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 181 occurred at disk power-on lifetime: 6877 hours (286 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 06 42 00 20 00 Error: UNC 6 sectors at LBA = 0x00200042 = 2097218 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 06 42 00 20 e0 00 01:12:34.889 READ DMA ef 10 02 00 00 00 a0 00 01:12:34.889 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 01:12:34.889 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 01:12:34.886 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 01:12:34.886 SET FEATURES [set transfer mode] Error 180 occurred at disk power-on lifetime: 6877 hours (286 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 41 00 20 00 Error: UNC 1 sectors at LBA = 0x00200041 = 2097217 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 41 00 20 e0 00 01:12:31.146 READ DMA ef 10 02 00 00 00 a0 00 01:12:31.146 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 01:12:31.146 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 01:12:31.143 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 01:12:31.143 SET FEATURES [set transfer mode] Error 179 occurred at disk power-on lifetime: 6877 hours (286 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 40 00 20 00 Error: UNC 1 sectors at LBA = 0x00200040 = 2097216 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 40 00 20 e0 00 01:12:27.394 READ DMA ef 10 02 00 00 00 a0 00 01:12:27.394 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 01:12:27.394 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 01:12:27.391 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 01:12:27.391 SET FEATURES [set transfer mode] Error 178 occurred at disk power-on lifetime: 6877 hours (286 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 40 00 20 00 Error: UNC 8 sectors at LBA = 0x00200040 = 2097216 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 40 00 20 e0 00 01:12:23.857 READ DMA c8 00 08 40 00 1c e0 00 01:12:23.850 READ DMA c8 00 08 40 00 18 e0 00 01:12:23.846 READ DMA c8 00 08 40 00 14 e0 00 01:12:23.842 READ DMA c8 00 08 40 00 10 e0 00 01:12:23.841 READ DMA Error 177 occurred at disk power-on lifetime: 6735 hours (280 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 e0 b8 96 d2 06 Error: UNC 224 sectors at LBA = 0x06d296b8 = 114464440 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 98 96 d2 e0 00 1d+09:52:25.563 READ DMA EXT ef 10 02 00 00 00 a0 00 1d+09:52:25.563 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 1d+09:52:25.563 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 1d+09:52:25.561 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 1d+09:52:25.561 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. I happen to have a spare 4TB drive that has data on it that I can do without. This would be to replace a 3TB drive. The problem is that my parity drive is also 3TB. Is it possible to replace a 3TB drive with a 4TB drive just for the data rebuild so that I can then pull off the data. After the data is off, I'll reassign the drive as parity. Any help/advice anybody could give me would be appreciated.
August 28, 201411 yr You are right - that drive looks very sick. I would RMA it ASAP if it is still underwarranty. I happen to have a spare 4TB drive that has data on it that I can do without. This would be to replace a 3TB drive. The problem is that my parity drive is also 3TB. Is it possible to replace a 3TB drive with a 4TB drive just for the data rebuild so that I can then pull off the data. After the data is off, I'll reassign the drive as parity. Any help/advice anybody could give me would be appreciated. Unfortunately not. You can never use a drive larger than parity. You do have one potential option. That is to use the swap-disable process where you simultaneously replace the parity drive with a larger one and rebuild the failing drive onto the old parity disk. This would mean the 4TB drive ends up as the new parity drive so you have to decide if that is what you want.
August 28, 201411 yr Author Yeah I thought about that, except I'm not sure if the failed drive will last through the parity rebuild or if I would be able to even pull off the data. It tends to try to unmount itself during large write cycles.
August 28, 201411 yr Yeah I thought about that, except I'm not sure if the failed drive will last through the parity rebuild or if I would be able to even pull off the data. It tends to try to unmount itself during large write cycles. Not sure I understand this comment? With the parity disable process the failed data drive would no longer be in the system. Are you saying that another drive is showing issues?
August 28, 201411 yr Author I'm sorry I think I misunderstood before. I wasn't aware of the "swap-disable" procedure. I just started reading into it and it looks perfect for me. I'll try it out and see if it works.
Archived
This topic is now archived and is closed to further replies.