March 9, 201412 yr One of my recorded shows aren't playing properly. So I rebooted my media clients and gave UnRaid a once over, and noticed a bunch of errors in the log. Interestingly this happened during a Parity check (correcting). Do I need to be concerned? Mar 9 04:33:49 Rigel kernel: sd 0:0:3:0: [sde] Unhandled sense code (Drive related) Mar 9 04:33:49 Rigel kernel: sd 0:0:3:0: [sde] (Drive related) Mar 9 04:33:49 Rigel kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Mar 9 04:33:49 Rigel kernel: sd 0:0:3:0: [sde] (Drive related) Mar 9 04:33:49 Rigel kernel: Sense Key : 0x3 [current] Mar 9 04:33:49 Rigel kernel: Info fld=0x578259a0 Mar 9 04:33:49 Rigel kernel: sd 0:0:3:0: [sde] (Drive related) Mar 9 04:33:49 Rigel kernel: ASC=0x11 ASCQ=0x0 Mar 9 04:33:49 Rigel kernel: sd 0:0:3:0: [sde] CDB: (Drive related) Mar 9 04:33:49 Rigel kernel: cdb[0]=0x28: 28 00 57 82 58 2f 00 02 78 00 Mar 9 04:33:49 Rigel kernel: end_request: critical target error, dev sde, sector 1468160047 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468159984 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468159992 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160000 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160008 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160016 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160024 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160032 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160040 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160048 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160056 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160064 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160072 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160080 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160088 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160096 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160104 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160112 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160120 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160128 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160136 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160144 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160152 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160160 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160168 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160176 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160184 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160192 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160200 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160208 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160216 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160224 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160232 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160240 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160248 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160256 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160264 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160272 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160280 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160288 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160296 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160304 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160312 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160320 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160328 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160336 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160344 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160352 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160360 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160368 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160376 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160384 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160392 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160400 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160408 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160416 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160424 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160432 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160440 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160448 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160456 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160464 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160472 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160480 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160488 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160496 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160504 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160512 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160520 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160528 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160536 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160544 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160552 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160560 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160568 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160576 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160584 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160592 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160600 (Errors) Mar 9 04:33:49 Rigel kernel: md: disk3 read error, sector=1468160608 (Errors) Mar 9 04:47:02 Rigel sSMTP[8871]: Creating SSL connection to host
March 10, 201412 yr Author Adding to it... WebUI finally came back; using the Disk Health plugin from Dynamix, I get this for disk3: ATA Error Count: 9 (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 9 occurred at disk power-on lifetime: 3296 hours (137 days + 8 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 -- -- -- -- -- -- -- 84 51 5f 00 00 00 40 Error: ICRC, ABRT 95 sectors at LBA = 0x00000000 = 0 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 3f 00 00 40 00 00:00:00.045 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.044 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.043 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.042 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.041 READ DMA Error 8 occurred at disk power-on lifetime: 3296 hours (137 days + 8 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 -- -- -- -- -- -- -- 84 51 5f 00 00 00 40 Error: ICRC, ABRT 95 sectors at LBA = 0x00000000 = 0 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 3f 00 00 40 00 00:00:00.044 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.043 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.042 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.041 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.040 READ DMA Error 7 occurred at disk power-on lifetime: 3296 hours (137 days + 8 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 -- -- -- -- -- -- -- 84 51 5f 00 00 00 40 Error: ICRC, ABRT 95 sectors at LBA = 0x00000000 = 0 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 3f 00 00 40 00 00:00:00.043 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.042 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.041 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.040 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.039 READ DMA Error 6 occurred at disk power-on lifetime: 3296 hours (137 days + 8 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 -- -- -- -- -- -- -- 84 51 5f 00 00 00 40 Error: ICRC, ABRT 95 sectors at LBA = 0x00000000 = 0 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 3f 00 00 40 00 00:00:00.042 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.041 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.040 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.039 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.038 READ DMA Error 5 occurred at disk power-on lifetime: 3296 hours (137 days + 8 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 -- -- -- -- -- -- -- 84 51 5f 00 00 00 40 Error: ICRC, ABRT 95 sectors at LBA = 0x00000000 = 0 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 3f 00 00 40 00 00:00:00.041 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.040 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.039 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.038 READ DMA c8 00 20 3f 00 00 40 00 00:00:00.037 READ DMA
March 10, 201412 yr Paste the entire SMART report. http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report
March 10, 201412 yr ... and the entire syslog. With disk errors, you always want to see the very first report of trouble.
March 10, 201412 yr Author Paste the entire SMART report. http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report Thanks - it's attached. I remember when pre-clearing drives a while back, Joe L. said to 'keep an eye on it' - I'm pretty sure that it was the report of THIS drive. I will dig to see if it was. ... and the entire syslog. With disk errors, you always want to see the very first report of trouble. Attached. I just selected this section because it seemed to be the first point of error. The only related thing I see is UnMenu's scheduled Email was set to go out right before the error. At the time this happened, there was a couple of things going on... a Parity check, and a local backup of a PC. However, this is not an uncommon scenario at my house so that's not likely. all my disks are mounted in an externally attached case via a SAS expander. Both the UnRaid host and the jbod case are on a BBU. I have another, empty WD black drive that I can move the data to. What I need to know is if this data can now be trusted, or if the errors are something significant. Thanks for both of your time. hmm - check out this OLD smart report that I posted in this thread about the Pre-clear. Interestingly enough it already had 9 errors? Smart_sde.txt SYSLOG_CURRENT_1TB_FAILED.zip
March 11, 201412 yr I'm sorry, I'm somewhat mystified. I do think his advice is very good though. SMART report is great, no important issues at all, the SMART errors are all very old, nothing recent. The syslog does not show any errors from the disk itself, just a brief spell of issues for a short range from the controller. As far as I can see, it had trouble reading from a short range of that drive but did not report any parity check errors! And the drive appears to be working fine afterward, no issues reported. It never spins down, so you must have something keeping it busy.
March 11, 201412 yr Author Thanks. Safe to assume that this should be a correcting parity check, right? You are right about the drive never getting to spundown. There is a vm that uses this drive 24/7. Good detective work seeing that. Thanks both for your help.
March 12, 201412 yr Author I'm sorry, I'm somewhat mystified. I do think his advice is very good though. SMART report is great, no important issues at all, the SMART errors are all very old, nothing recent. The syslog does not show any errors from the disk itself, just a brief spell of issues for a short range from the controller. As far as I can see, it had trouble reading from a short range of that drive but did not report any parity check errors! And the drive appears to be working fine afterward, no issues reported. It never spins down, so you must have something keeping it busy. Run another parity check. Okay parity check ran fine. Im glad that smart report looks clean. That would indicate that the physical drive is good, right? The same backup process was running and reading from this share ad before. This time, that process errored out. So I'm guessing that this is an IO timeout, when two IO bound processes are running? This is the first time that I saw anything in the errors column in UnRaid (only other issue was a blue balled drive).
March 29, 201412 yr Author Hello! less than a three weeks later, i've got another rash of errors, also on the same drive. again during a parity check. here's the excerpt from sys log. I'll post smart report again to see if there's anything there. I've also moved my parity check window to a different time, to see if that makes a difference. Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Unhandled sense code Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: Result: hostbyte=0x00 driverbyte=0x08 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: Sense Key : 0x3 [current] Mar 24 02:37:04 Rigel kernel: Info fld=0x578259a0 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: ASC=0x11 ASCQ=0x0 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] CDB: Mar 24 02:37:04 Rigel kernel: cdb[0]=0x28: 28 00 57 82 58 7f 00 03 f0 00 Mar 24 02:37:04 Rigel kernel: end_request: critical target error, dev sde, sector 1468160127 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160064 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160072 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160080 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160088 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160096 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160104 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160112 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160120 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160128 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160136 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160144 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160152 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160160 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160168 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160176 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160184 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160192 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160200 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160208 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160216 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160224 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160232 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160240 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160248 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160256 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160264 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160272 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160280 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160288 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160296 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160304 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160312 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160320 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160328 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160336 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160344 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160352 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160360 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160368 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160376 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160384 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160392 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160400 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160408 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160416 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160424 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160432 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160440 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160448 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160456 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160464 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160472 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160480 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160488 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160496 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160504 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160512 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160520 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160528 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160536 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160544 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160552 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160560 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160568 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160576 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160584 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160592 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160600 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160608 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160616 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160624 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160632 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160640 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160648 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160656 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160664 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160672 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160680 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160688 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160696 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160704 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160712 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160720 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160728 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160736 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160744 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160752 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160760 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160768 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160776 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160784 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160792 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160800 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160808 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160816 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160824 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160832 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160840 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160848 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160856 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160864 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160872 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160880 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160888 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160896 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160904 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160912 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160920 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160928 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160936 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160944 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160952 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160960 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160968 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160976 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160984 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160992 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161000 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161008 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161016 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161024 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161032 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161040 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161048 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161056 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468161064
March 29, 201412 yr Author here's the smartctl output... i'm not seeing that much - Raw_Read_Error_Rate went from 38 to 40. (the Raw value). nothing else changed. smart_sde_205.txt
March 29, 201412 yr Power On Hours, Load Cycle Count and MultiZone Errors indicate the end of life is near (the latter are actual 'mechanical' failures, I believe. I'd start saving for a new drive, and thinking about a replacement strategy.
March 30, 201412 yr Power On Hours, Load Cycle Count and MultiZone Errors indicate the end of life is near (the latter are actual 'mechanical' failures, I believe. I'd start saving for a new drive, and thinking about a replacement strategy. Those numbers don't look bad to me, just normal wear and tear, and not that much of it. I always look at the VALUE column to see how the manufacturer rates the value, and in both cases (Load Cycle Count and MultiZone Errors) they are still 100. It hasn't even dropped to 99 yet. That means this drive should not be bothered by the counts observed so far. And 26000 hours is not that much. You should still have several operational years left, hopefully even more.
March 30, 201412 yr Hello! less than a three weeks later, i've got another rash of errors, also on the same drive. again during a parity check. here's the excerpt from sys log. I'll post smart report again to see if there's anything there. I've also moved my parity check window to a different time, to see if that makes a difference. Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Unhandled sense code Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: Result: hostbyte=0x00 driverbyte=0x08 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: Sense Key : 0x3 [current] Mar 24 02:37:04 Rigel kernel: Info fld=0x578259a0 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] Mar 24 02:37:04 Rigel kernel: ASC=0x11 ASCQ=0x0 Mar 24 02:37:04 Rigel kernel: sd 0:0:3:0: [sde] CDB: Mar 24 02:37:04 Rigel kernel: cdb[0]=0x28: 28 00 57 82 58 7f 00 03 f0 00 Mar 24 02:37:04 Rigel kernel: end_request: critical target error, dev sde, sector 1468160127 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160064 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160072 Mar 24 02:37:04 Rigel kernel: md: disk3 read error, sector=1468160080 ... This syslog excerpt is just the aftermath of the more important disk errors. The very first disk error is usually the most important one to see.
March 30, 201412 yr Power On Hours, Load Cycle Count and MultiZone Errors indicate the end of life is near (the latter are actual 'mechanical' failures, I believe. I'd start saving for a new drive, and thinking about a replacement strategy. Those numbers don't look bad to me, just normal wear and tear, and not that much of it. I always look at the VALUE column to see how the manufacturer rates the value, and in both cases (Load Cycle Count and MultiZone Errors) they are still 100. It hasn't even dropped to 99 yet. That means this drive should not be bothered by the counts observed so far. And 26000 hours is not that much. You should still have several operational years left, hopefully even more. Live and learn. Thanks for the tip, RobJ! And I"m glad its not as serious for axeman.
March 31, 201412 yr Author I'd start saving for a new drive, and thinking about a replacement strategy. Thanks Dale - i'm going to be moving the data off this drive to a brand new 3TB RED. The beauty of it is that this drive is used as an NFS datastore for an ESXi VM; So just moving the one file and repointing in the VM should set be right back up again. And of course with UnRaid giving me protection, i'm not too worried about a failure/loss of data. (not to mention that the VM itself is backed up to CrashPlan). I need to schedule some downtime and get it done. Those numbers don't look bad to me, just normal wear and tear, and not that much of it. I always look at the VALUE column to see how the manufacturer rates the value, and in both cases (Load Cycle Count and MultiZone Errors) they are still 100. It hasn't even dropped to 99 yet. That means this drive should not be bothered by the counts observed so far. And 26000 hours is not that much. You should still have several operational years left, hopefully even more. What should I do with this drive? I am going to move critical data off of it, but should I be concerned that the drive is on it's way out? Should I run that longer smart report? the one that (i think) takes over 2hrs?
March 31, 201412 yr I'm learning too, had to do some research on your results as I didn't recognize them. Turns out those messages are from the LSI chipsets, and are notoriously difficult and cryptic, with no guides (or even error code tables) anywhere as to how to interpret the error codes. That is completely inexcusable in this day and age. There's no excuse for not using plain language to describe any issue. The best info I could find indicates there's an issue, possibly from a bug in the LSI firmware (still unfixed to date), or an issue on the drive surface, so yes, run that SMART long test, and expect it to take quite a few hours.
March 31, 201412 yr Author I'm learning too, had to do some research on your results as I didn't recognize them. Turns out those messages are from the LSI chipsets, and are notoriously difficult and cryptic, with no guides (or even error code tables) anywhere as to how to interpret the error codes. That is completely inexcusable in this day and age. There's no excuse for not using plain language to describe any issue. The best info I could find indicates there's an issue, possibly from a bug in the LSI firmware (still unfixed to date), or an issue on the drive surface, so yes, run that SMART long test, and expect it to take quite a few hours. Thanks RobJ! I will move the data off and run the test. Controller issue worries me even more. I'd much rather it be a bad drive! The previous owner of this controller had a bad flash of it and told me that one port was completely fried. I reflashed it and everything seemed to be OK. Thanks for your prompt reply - i appreciate you going out and learning something to help - instead of just writing it off as something you don't know.
Archived
This topic is now archived and is closed to further replies.