November 20, 20169 yr When I log in to my UnRaid Dashboard array status usually has a amber mark in the SMART status column clicking on that takes you to the error page. You can see the errors. I don't know a lot about Linux but could use some help to know if this is some thing I need to worry about or not. Is my HDD going to fail? or can I format it to save it? Error 50734 occurred at disk power-on lifetime: 8389 hours (349 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 -- -- -- -- -- -- -- 04 41 20 18 55 06 e1 Error: ABRT 32 sectors at LBA = 0x01065518 = 17192216 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 20 18 55 06 e1 08 44d+19:18:38.741 READ DMA ca 00 80 70 45 b9 e0 08 44d+19:18:38.012 WRITE DMA ca 00 08 48 04 00 e0 08 44d+19:06:48.660 WRITE DMA ca 00 08 c8 61 04 e0 08 44d+19:06:48.652 WRITE DMA ca 00 08 48 52 04 e0 08 44d+19:06:48.652 WRITE DMA Error 50733 occurred at disk power-on lifetime: 8388 hours (349 days + 12 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 -- -- -- -- -- -- -- 04 41 40 18 4c 06 e1 Error: ABRT 64 sectors at LBA = 0x01064c18 = 17189912 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 40 18 4c 06 e1 08 44d+19:06:38.999 READ DMA ca 00 80 08 1d d6 e0 08 44d+19:06:38.257 WRITE DMA b0 d1 01 01 4f c2 00 08 44d+18:59:43.040 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 44d+18:59:43.037 SMART READ DATA ec 00 01 00 00 00 00 08 44d+18:59:43.029 IDENTIFY DEVICE
November 21, 20169 yr Community Expert Post up your diagnostics file. 'Tools' >>> Diagnostics' (And edit your post to get rid of all of the blank space at the end your first post.)
November 21, 20169 yr Author === 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: ( 73) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: (38940) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 391) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) SCT Status 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 0x002f 195 195 051 Pre-fail Always - 42401 3 Spin_Up_Time 0x0027 223 172 021 Pre-fail Always - 5808 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 168 5 Reallocated_Sector_Ct 0x0033 134 134 140 Pre-fail Always FAILING_NOW 1942 7 Seek_Error_Rate 0x002e 200 194 000 Old_age Always - 301 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 11779 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 75 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 46 193 Load_Cycle_Count 0x0032 156 156 000 Old_age Always - 132828 194 Temperature_Celsius 0x0022 122 101 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 503 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 23 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 001 001 000 Old_age Offline - 192832 SMART Error Log Version: 1 Warning: ATA error count 50734 inconsistent with error log pointer 5 ATA Error Count: 50734 (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 50734 occurred at disk power-on lifetime: 8389 hours (349 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 -- -- -- -- -- -- -- 04 41 20 18 55 06 e1 Error: ABRT 32 sectors at LBA = 0x01065518 = 17192216 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 20 18 55 06 e1 08 44d+19:18:38.741 READ DMA ca 00 80 70 45 b9 e0 08 44d+19:18:38.012 WRITE DMA ca 00 08 48 04 00 e0 08 44d+19:06:48.660 WRITE DMA ca 00 08 c8 61 04 e0 08 44d+19:06:48.652 WRITE DMA ca 00 08 48 52 04 e0 08 44d+19:06:48.652 WRITE DMA Error 50733 occurred at disk power-on lifetime: 8388 hours (349 days + 12 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 -- -- -- -- -- -- -- 04 41 40 18 4c 06 e1 Error: ABRT 64 sectors at LBA = 0x01064c18 = 17189912 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 40 18 4c 06 e1 08 44d+19:06:38.999 READ DMA ca 00 80 08 1d d6 e0 08 44d+19:06:38.257 WRITE DMA b0 d1 01 01 4f c2 00 08 44d+18:59:43.040 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 44d+18:59:43.037 SMART READ DATA ec 00 01 00 00 00 00 08 44d+18:59:43.029 IDENTIFY DEVICE Error 50732 occurred at disk power-on lifetime: 8388 hours (349 days + 12 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 -- -- -- -- -- -- -- 04 41 a0 18 d2 05 e1 Error: ABRT 160 sectors at LBA = 0x0105d218 = 17158680 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 a0 18 d2 05 e1 08 44d+18:26:42.078 READ DMA ca 00 80 08 1d d6 e0 08 44d+18:26:41.337 WRITE DMA Error 50731 occurred at disk power-on lifetime: 8385 hours (349 days + 9 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 -- -- -- -- -- -- -- 04 41 a0 28 9c 08 e1 Error: ABRT 160 sectors at LBA = 0x01089c28 = 17341480 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 a0 28 9c 08 e1 08 44d+15:46:52.318 READ DMA ca 00 80 08 1d d6 e0 08 44d+15:46:51.589 WRITE DMA b0 d1 01 01 4f c2 00 08 44d+15:29:34.862 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 44d+15:29:34.859 SMART READ DATA ec 00 01 00 00 00 00 08 44d+15:29:34.852 IDENTIFY DEVICE Error 50730 occurred at disk power-on lifetime: 8385 hours (349 days + 9 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 -- -- -- -- -- -- -- 04 41 40 88 88 08 e1 Error: ABRT 64 sectors at LBA = 0x01088888 = 17336456 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 40 88 88 08 e1 08 44d+15:26:52.936 READ DMA ca 00 80 70 45 b9 e0 08 44d+15:26:52.193 WRITE DMA ef 10 02 00 00 00 a0 08 44d+15:22:00.261 SET FEATURES [Enable SATA feature] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: unknown failure 90% 11776 - 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.
November 21, 20169 yr Community Expert I would replace that disk NOW. (Of course, you don't really need me to tell your that! You can read the SMART Report. )
November 21, 20169 yr "SMART overall-health self-assessment test result: FAILED!" ==> There's nothing to interpret here ... the disk FAILS the SMART test, and it's warning you that it's failing. Agree with Frank => replace it NOW ... as in TODAY. Your thread subject implies this is your parity drive; so if you've been giving any consideration to increasing the size of your parity disk (so you can use larger drives in your array) this would be a good time to get a larger disk. But regardless of the size, do it NOW !!
November 22, 20169 yr Author just wanted to make sure just picked up a 4Tb to replace it. Can some one point me to a good guide on replacing parity drives. I don't mind reading the manual
November 22, 20169 yr Community Expert http://lime-technology.com/wiki/index.php/UnRAID_6_2/Storage_Management You want to read both the "Upgrading parity disk(s)" and "Replacing failed disk(s)". The procedure is basically the same but the descriptions of how to do it is a bit different. Looking at both should answer your questions. IF not, post back with what is unclear and someone will help.
Archived
This topic is now archived and is closed to further replies.