JimPhreak Posted June 12, 2015 Share Posted June 12, 2015 I just got the following disk read errors yesterday. Are these a concern? Where do I go from here? Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752952 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752960 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752968 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752976 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752984 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714752992 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753000 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753008 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753016 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753024 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753032 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753040 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753048 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753056 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753064 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: md: disk3 read error, sector=4714753072 Link to comment
trurl Posted June 12, 2015 Share Posted June 12, 2015 Post complete syslog and smart reports for the drive. Link to comment
JimPhreak Posted June 12, 2015 Author Share Posted June 12, 2015 Post complete syslog and smart reports for the drive. Here's the syslog. By smart report you mean what exactly? I'm currently running an extended smart test on the drive now. Short test passed without errors. syslog.txt Link to comment
trurl Posted June 12, 2015 Share Posted June 12, 2015 Looks like your syslog rotated. See if you have any others in /var/log. From Main, click on the disk, then Health - Attributes and post that while you wait on the long test. Link to comment
JimPhreak Posted June 12, 2015 Author Share Posted June 12, 2015 Looks like your syslog rotated. See if you have any others in /var/log. From Main, click on the disk, then Health - Attributes and post that while you wait on the long test. That's the only one I see in the /var/log directory. Here are the attributes for the disk showing the read errors. Link to comment
trurl Posted June 12, 2015 Share Posted June 12, 2015 Looks like your syslog rotated. See if you have any others in /var/log. That's the only one I see in the /var/log directory. Looking at the syslog you posted again, I see that it is from Jun 2Jun 2 18:15:49 SPE-UNRAID-BCKP rsyslogd: [origin software="rsyslogd" swVersion="8.6.0" x-pid="1143" x-info="http://www.rsyslog.com"] start Go to Tools - System Log and post that one instead. Link to comment
JimPhreak Posted June 12, 2015 Author Share Posted June 12, 2015 Looks like your syslog rotated. See if you have any others in /var/log. That's the only one I see in the /var/log directory. Looking at the syslog you posted again, I see that it is from Jun 2Jun 2 18:15:49 SPE-UNRAID-BCKP rsyslogd: [origin software="rsyslogd" swVersion="8.6.0" x-pid="1143" x-info="http://www.rsyslog.com"] start Go to Tools - System Log and post that one instead. That's where I got the one I posted. It starts at June 2nd but you'll see it goes up until today. I just checked and my date was off. My server has today as being June 11th. Just fixed that by turning on NTP. Link to comment
JimPhreak Posted June 13, 2015 Author Share Posted June 13, 2015 Both short and extended tests completed without errors. Link to comment
c3 Posted June 13, 2015 Share Posted June 13, 2015 The syslog entries you are looking are; Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: mpt2sas0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] Sense Key : 0x2 [current] Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] ASC=0x4 ASCQ=0x0 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] CDB: Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: cdb[0]=0x88: 88 00 00 00 00 01 19 05 6b f8 00 00 00 80 00 00 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: blk_update_request: I/O error, dev sdf, sector 4714753016 Which means the drive did not come ready in time to service the request. The online SMART tests are not going to help you. Link to comment
JimPhreak Posted June 13, 2015 Author Share Posted June 13, 2015 The syslog entries you are looking are; Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: mpt2sas0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] Sense Key : 0x2 [current] Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] ASC=0x4 ASCQ=0x0 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: sd 0:0:4:0: [sdf] CDB: Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: cdb[0]=0x88: 88 00 00 00 00 01 19 05 6b f8 00 00 00 80 00 00 Jun 11 16:27:07 SPE-UNRAID-BCKP kernel: blk_update_request: I/O error, dev sdf, sector 4714753016 Which means the drive did not come ready in time to service the request. The online SMART tests are not going to help you. So...what now? Send the disk for RMA? Link to comment
c3 Posted June 13, 2015 Share Posted June 13, 2015 You could try power cycling the drive to see if it reports any out of range spin up times. But as a one off, I'd wait to see if the problem reoccurs in this drive or another. It's as likely to be a power supply as the disk drive with only one report. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.