June 8, 201412 yr So I had a disk "red ball" yesterday. I stopped the array, reassigned a warm spare to that slot, and it's rebuilding now. Everything went smoothly and seems to be working as it should. The read/write errors are below. It happened while the mover script was transferring cached data to the array. I've edited out the file operations. Jun 7 06:00:01 apollo logger: mover started Jun 7 06:00:26 apollo kernel: md: disk8 read error, sector=51800 (Errors) Jun 7 06:00:26 apollo kernel: md: disk8 read error, sector=51808 (Errors) Jun 7 06:00:26 apollo kernel: md: disk8 read error, sector=51816 (Errors) Jun 7 06:01:12 apollo kernel: md: disk8 write error, sector=51800 (Errors) Jun 7 06:01:12 apollo kernel: md: recovery thread woken up ... (unRAID engine) Jun 7 06:01:12 apollo kernel: md: disk8 write error, sector=51808 (Errors) Jun 7 06:01:12 apollo kernel: md: disk8 write error, sector=51816 (Errors) Jun 7 06:01:12 apollo kernel: md: recovery thread has nothing to resync (unRAID engine) Jun 7 06:08:21 apollo logger: mover finished Can someone help me figure out what caused these write errors? Should I keep the drive or is it no longer reliable? It has no reallocated or pending sectors, which I understand are the normal indicators of a failing drive. There are some high numbers in some other fields though. Wikipedia briefly mentions "UDMA CRC" and "Command Timeout" with non-zero values could relate to cabling. My drives are connected to a SuperMicro backplane (CSE-846BA) through Mini SAS (SFF-8087) cables to M1015 controllers. === START OF INFORMATION SECTION === Model Family: Seagate Barracuda XT Device Model: ST33000651AS Serial Number: Z290QZ8X LU WWN Device Id: 5 000c50 035f5eedc Firmware Version: CC45 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/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: 6.0 Gb/s) Local Time is: Sun Jun 8 15:34:46 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: 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: ( 600) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 454) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table 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 104 099 006 Pre-fail Always - 6368932 3 Spin_Up_Time 0x0003 090 073 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1305 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail Always - 113711999 9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 18894 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 89 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 097 000 Old_age Always - 17180131334 189 High_Fly_Writes 0x003a 058 058 000 Old_age Always - 42 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (0 6 28 20 0) 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 - 60 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1437 194 Temperature_Celsius 0x0022 028 045 000 Old_age Always - 28 (128 0 0 0 0) 195 Hardware_ECC_Recovered 0x001a 011 008 000 Old_age Always - 6368932 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 493 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 280929515868757 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2676197229 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3638008229 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% 18894 - # 2 Short offline Completed without error 00% 4639 - 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.
June 8, 201412 yr You should attached the entire syslog for analyses by those folks are more technically inclined than I am. How to get a syslog is described in this thread: http://lime-technology.com/forum/index.php?topic=9880.0 If it is too big to attach, zip it as syslogs compress to a very small size.
June 9, 201412 yr If your disk cables are neatly bundled, and close to each other making the server look beautiful,, you've positioned them for MAXIMUM noise coupling and crosstalk between them, almost guaranteed to cause CRC errors. Cut the tie-wraps, move the cables away from each other, make it look messy, and you'll probably find most of the CRC errors will go away. Joe L.
June 9, 201412 yr Author If your disk cables are neatly bundled, and close to each other making the server look beautiful,, you've positioned them for MAXIMUM noise coupling and crosstalk between them, almost guaranteed to cause CRC errors. Cut the tie-wraps, move the cables away from each other, make it look messy, and you'll probably find most of the CRC errors will go away. Joe L. I haven't intentionally bundled them, but I'll take a look inside and see if I can reroute them to provide more separation. Thanks!
Archived
This topic is now archived and is closed to further replies.