jonlai9 Posted September 1, 2011 Share Posted September 1, 2011 Hey guys, I was helping my friend copy about 250GB of movies (that span almost all my drives) from my server to his external yesterday and noticed that disk3 started to report a ton of errors. There were several blocks of errors, of each were all multiple (at least 20-30) of the same two messages: Aug 31 21:34:18 LAI_SERVER kernel: handle_stripe read error: 3884082480/2, count: 1 (Errors) Aug 31 21:34:18 LAI_SERVER kernel: md: disk3 read error (Errors) At midnight, parity sync went on, and this morning at around 7am the same thing happened, albeit to a lesser degree (the blocks of error messages were smaller). Unraid reports 337 errors on disk3 and none for all my other drives - they were all 0 before yesterday. To me, the SMART report does not appear to suggest the drive is failing, but can someone verify that? Are the errors simply due to the fact that I was transferring too many files at the same time, overloading the bandwidth of the drives? To my knowledge, however, there should not have been anyone accessing the server at 7am this morning, so any activity related to the errors would have been caused by the parity sync itself. The parity sync this morning reported 0 errors. syslog attached. Thanks. SMART Report: === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD20EADS-00S2B0 Serial Number: WD-WCAVY3417702 Firmware Version: 01.00A01 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Sep 1 18:06:22 2011 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: PASSED 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: (41160) 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: ( 5) minutes. SCT capabilities: (0x3037) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 151 149 021 Pre-fail Always - 9441 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1544 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 6273 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 398 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 147 147 000 Old_age Always - 159708 194 Temperature_Celsius 0x0022 129 111 000 Old_age Always - 23 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 15 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 5 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 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 without error 00% 3530 - # 2 Extended offline Interrupted (host reset) 10% 3452 - # 3 Extended offline Aborted by host 90% 3415 - 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. syslog.txt Link to comment
Joe L. Posted September 2, 2011 Share Posted September 2, 2011 Hey guys, I was helping my friend copy about 250GB of movies (that span almost all my drives) from my server to his external yesterday and noticed that disk3 started to report a ton of errors. There were several blocks of errors, of each were all multiple (at least 20-30) of the same two messages: Aug 31 21:34:18 LAI_SERVER kernel: handle_stripe read error: 3884082480/2, count: 1 (Errors) Aug 31 21:34:18 LAI_SERVER kernel: md: disk3 read error (Errors) At midnight, parity sync went on, and this morning at around 7am the same thing happened, albeit to a lesser degree (the blocks of error messages were smaller). Unraid reports 337 errors on disk3 and none for all my other drives - they were all 0 before yesterday. To me, the SMART report does not appear to suggest the drive is failing, but can someone verify that? Are the errors simply due to the fact that I was transferring too many files at the same time, overloading the bandwidth of the drives? To my knowledge, however, there should not have been anyone accessing the server at 7am this morning, so any activity related to the errors would have been caused by the parity sync itself. The parity sync this morning reported 0 errors. syslog attached. Thanks. SMART Report: === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD20EADS-00S2B0 Serial Number: WD-WCAVY3417702 Firmware Version: 01.00A01 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Sep 1 18:06:22 2011 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: PASSED 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: (41160) 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: ( 5) minutes. SCT capabilities: (0x3037) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 151 149 021 Pre-fail Always - 9441 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1544 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 6273 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 398 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 147 147 000 Old_age Always - 159708 194 Temperature_Celsius 0x0022 129 111 000 Old_age Always - 23 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 15 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 5 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 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 without error 00% 3530 - # 2 Extended offline Interrupted (host reset) 10% 3452 - # 3 Extended offline Aborted by host 90% 3415 - 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. The read errors are because you have 15 unreadable sectors on the disk. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 15 They are pending re-allocation the next time they are written. Link to comment
jonlai9 Posted September 2, 2011 Author Share Posted September 2, 2011 Thanks Joe. So there shouldn't be any hardware related issues, correct? Link to comment
Joe L. Posted September 2, 2011 Share Posted September 2, 2011 Thanks Joe. So there shouldn't be any hardware related issues, correct? An un-readable sector on a hard-disk IS a hardware issue. Link to comment
jonlai9 Posted September 2, 2011 Author Share Posted September 2, 2011 Are 15 unreadable sectors going to pose any significant hardware issues down the road? Will this hard drive need to be replaced soon? Link to comment
jespeed Posted September 2, 2011 Share Posted September 2, 2011 Hello, Don't know about replacing soon or not but the fact that it has 15 sectors pending reallocation is notice to keep a very close eye on this drive. If that number continues to increase I would replace. Just my opinion. Take care, Jim S. Link to comment
Johnm Posted September 3, 2011 Share Posted September 3, 2011 I myself am drastic. i would see that as a sign to upgrade my array. I would replace it with another 2tb drive that had been precleared twice. once the rebuild was good and my data was good, I'd preclear or repair/zero that suspect drive twice and look at the reports. if the drive got a clean bill of health, i'd put it back into the array expanding it or save for a spare. if it is not stable... well I'd probably replace it. 15 is not a bad number that you need to panic about. but it is a sign of what could come. as i said I am drastic and that is not the solution for most people. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.