February 1, 201511 yr My array went through its monthly parity check and one of the drives is showing 813 errors, I have looked through the syslog (attached and they appear to be read errors. What is the general concensus now should I swap the drive out or is it nothing too much to worry about? Actually looking at the log it appeary the check was run as "check" NOCORRECT presulmably that means that the data has not been corrected? If so should I rerun the parity check with the correct option? syslog_Jan_31_15.zip
February 2, 201511 yr Author So should I run the parity check with the correct option or will this damage my array?
February 2, 201511 yr Parity checks never write to the data drives, and NOCORRECT means it won't write to the parity drive either. In addition to the read errors on disk 4, were there parity errors? Post a smart report of disk 4. Also you are on v5rc12a. You should consider upgrading to the current stable version of unRAID 5.0.6
February 3, 201511 yr Author There are no parity errors showing in the syslog and the menu says that the last parity check was on the 1st Feb 2015 finding 0 errors.. However the error column was showing 813 errors, but now I have rebooted the system that is now reading 0. I ran a short smart test on the drive and found this which says it passed but then says completed: read failure smartctl -a -d ata /dev/sde smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F2 EG series Device Model: SAMSUNG HD154UI Serial Number: S1Y6J9BS807554 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Mon Feb 2 23:53:14 2015 GMT 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: ( 114) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (20645) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 36) minutes. SCT capabilities: (0x003f) 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 0x000f 099 099 051 Pre-fail Always - 160 3 Spin_Up_Time 0x0007 071 071 011 Pre-fail Always - 9610 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 3539 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 14667 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 42594 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 325 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 160 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 234 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 093 067 000 Old_age Always - 7 (Min/Max 7/7) 194 Temperature_Celsius 0x0022 087 068 000 Old_age Always - 13 (Min/Max 7/13) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 2365 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 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 Short offline Completed: read failure 20% 42594 1536964556 # 2 Short offline Completed: read failure 20% 42594 1536964640 # 3 Short offline Completed without error 00% 31269 - # 4 Short offline Completed without error 00% 31269 - 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.
February 3, 201511 yr Seeing as how the drive has almost 5 years of power on time and is starting to show signs of having problems, I'd replace it. Have you looked at the smart reports for the rest of your drives? If they are all healthy, I'd replace this drive now.
February 3, 201511 yr Author Ran a Smart test on all the remaining drives and no faults. Just read error of disk 4 as shown above. Replace and rebuild?
February 3, 201511 yr Author Before I replace this drive, presumably my parity is correct as I did a "check NOCORRECT"? So just unassign the drive, shyt down the array, replace, assign the drive and rebuild?
February 3, 201511 yr I don't think you have to do anything in the array assignments until after you put in the new drive. Unraid will figure out the old drive is missing, and when you select the new drive it will say something like "wrong disk", and offer the option to rebuild and expand onto the new disk after you check the box.
February 22, 201511 yr Author I replaced the drive for a new 3Tb one and all is well. However the drived that was showing problems I put back into a spare slot in the array and have run PreClear on it for three cycles without error. Is it safe to add back to the array?
February 22, 201511 yr I replaced the drive for a new 3Tb one and all is well. However the drived that was showing problems I put back into a spare slot in the array and have run PreClear on it for three cycles without error. Is it safe to add back to the array? Run a smart long test on it and see if it completes now.
February 22, 201511 yr Author OK I ran a short and a long Smart test and both returned OK. Does this mean it is OK to put back into the array? Or is it still a bit iffy? If so what is likely to have caused the error? Ridley
February 23, 201511 yr Author === 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (20645) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 36) minutes. SCT capabilities: (0x003f) 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 0x000f 100 093 051 Pre-fail Always - 5 3 Spin_Up_Time 0x0007 050 050 011 Pre-fail Always - 15570 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 3546 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 14275 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 42673 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 329 13 Read_Soft_Error_Rate 0x000e 100 093 000 Old_age Always - 5 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 235 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 089 067 000 Old_age Always - 11 (Min/Max 6/11) 194 Temperature_Celsius 0x0022 087 068 000 Old_age Always - 13 (Min/Max 6/13) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1431 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 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% 42667 - # 2 Short offline Completed without error 00% 42661 - # 3 Short offline Completed: read failure 20% 42594 1536964556 # 4 Short offline Completed: read failure 20% 42594 1536964640 # 5 Short offline Completed without error 00% 31269 - # 6 Short offline Completed without error 00% 31269 - 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.
February 23, 201511 yr The only thing that would cause me concern is the "Completed: read failure" at the bottom. Other than that the drive looks fine. I am guessing that the issue before was a loose or bad cable? Someone smarter than me would need to confirm that, I am just guessing. If it was a cabling issue then it is probably fine to use it but keep an eye on it. On a side note, how are you keeping your drives at 13 degree C Maximum? Does your server live in a refrigerator? EDIT: I lied - see post below...
February 23, 201511 yr Oh I lied above! Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 235 That indicates that 235 sectors are uncorrectable. I would retire the drive...
February 23, 201511 yr Now those last two replies put me in a quandary... Exactly as it should. The drive is currently fine to use, but that could change very quickly to not fine. All drives will fail, the important bit is predicting when.
February 23, 201511 yr That drive is at or quickly approaching 5 years old (42673 power on hours). I wouldn't trust it with my data, but then again it isn't my data and isn't my array, so it's all your call. I just finished replacing all my 2TB ~5 year old drives with newer 4TB drives.
Archived
This topic is now archived and is closed to further replies.