December 19, 201213 yr I'm running unRAID v5.0-rc8a and have come home to find my syslog filled with errors. They occurred whilst the mover script was running - as a result my syslog was huge, and since the same errors were repeated over and over again I've just attached an excerpt and quoted the repeated lines below: kernel: handle_stripe read error: 1943077040/2, count: 1 kernel: md: disk2 read error and kernel: sd 0:0:2:0: [sde] Result: hostbyte=0x00 driverbyte=0x08 kernel: sd 0:0:2:0: [sde] Sense Key : 0xb [current] kernel: sd 0:0:2:0: [sde] ASC=0x47 ASCQ=0x3 kernel: sd 0:0:2:0: [sde] CDB: cdb[0]=0x28: 28 00 1a 84 3d 50 00 04 00 00 kernel: end_request: I/O error, dev sde, sector 444874064 I suspect from searching the forums that I either have a loose/dodgy cable or a bad disk. I understand I will need to carry out a SMART test to confirm which. Here are the results: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 105 3 Spin_Up_Time 0x0007 128 128 024 Pre-fail Always - 544 (Average 545) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 134 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 132 132 020 Pre-fail Offline - 32 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 296 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 95 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 135 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 135 194 Temperature_Celsius 0x0002 193 193 000 Old_age Always - 31 (Min/Max 17/36) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 122039 Am thinking most likely a dodgy cable or sas card - is there anything else I should be considering/trying? Cheers syslog.txt
December 20, 201213 yr Author I've re-seated the cable connectors and am going to try running the mover script again tonight. Am keeping my fingers crossed..!
December 20, 201213 yr Author Just to update, mover ran successfully overnight with no errors. Looks like it was just a loose cable
Archived
This topic is now archived and is closed to further replies.