Just installed this not too long ago and some read errors reported.  Got a diagnostics after it happened and put the system to sleep in case I needed to grab any other details that would be lost on a restart.

 

Is the drive actually failing or could this be caused by another issue?  Never had issues with my cabled.

 

Any help would be greatly appreciated!

tower-diagnostics-20200307-1219.zip

Edited March 18, 20206 yr by newbie_dude

LSI controllers in some cases generate a few errors when waking up from sleep and/or spinning up some devices, they look harmless.

Thank you!! Is there some test I can run to get greater confidence it's not the drive?  Never had this error before and I've had the controller for years.

 

Always appreciate your prompt help JB.

You can run a SMART test, but the errors happened in multiple devices, which again suggests not a specific device problem:

 

Mar  7 12:18:24 Tower kernel: sd 7:0:0:0: [sdb] tag#520 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar  7 12:18:24 Tower kernel: sd 7:0:0:0: [sdb] tag#520 CDB: opcode=0x88 88 00 00 00 00 02 ba a0 f4 00 00 00 00 08 00 00
Mar  7 12:18:24 Tower kernel: print_req_error: I/O error, dev sdb, sector 11721044992
Mar  7 12:18:25 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred
Mar  7 12:18:25 Tower kernel: mdcmd (1379): spindown 7
Mar  7 12:18:25 Tower dhcpcd[1569]: eth0: leased 192.168.0.16 for 604800 seconds
Mar  7 12:18:25 Tower avahi-daemon[7808]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.16.
Mar  7 12:18:25 Tower avahi-daemon[7808]: New relevant interface eth0.IPv4 for mDNS.
Mar  7 12:18:25 Tower dhcpcd[1569]: eth0: adding route to 192.168.0.0/24
Mar  7 12:18:25 Tower dhcpcd[1569]: eth0: adding default route via 192.168.0.1
Mar  7 12:18:25 Tower avahi-daemon[7808]: Registering new address record for 192.168.0.16 on eth0.IPv4.
Mar  7 12:18:27 Tower ntpd[1630]: Listen normally on 19 eth0 192.168.0.16:123
Mar  7 12:18:27 Tower ntpd[1630]: new interface(s) found: waking up resolver
Mar  7 12:18:31 Tower kernel: sd 7:0:2:0: [sdd] tag#514 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar  7 12:18:31 Tower kernel: sd 7:0:2:0: [sdd] tag#514 CDB: opcode=0x88 88 00 00 00 00 02 ba a0 f4 00 00 00 00 08 00 00
Mar  7 12:18:31 Tower kernel: print_req_error: I/O error, dev sdd, sector 11721044992
Mar  7 12:18:31 Tower kernel: sd 7:0:5:0: Power-on or device reset occurred
Mar  7 12:18:32 Tower kernel: mdcmd (1380): spindown 8
Mar  7 12:18:32 Tower kernel: mdcmd (1381): spindown 9
Mar  7 12:18:39 Tower kernel: sd 7:0:5:0: [sdg] tag#517 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar  7 12:18:39 Tower kernel: sd 7:0:5:0: [sdg] tag#517 CDB: opcode=0x88 88 00 00 00 00 01 d1 bf be 00 00 00 00 08 00 00
Mar  7 12:18:39 Tower kernel: print_req_error: I/O error, dev sdg, sector 7813971456
Mar  7 12:18:39 Tower kernel: sd 7:0:3:0: Power-on or device reset occurred
Mar  7 12:18:48 Tower kernel: sd 7:0:3:0: [sde] tag#520 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar  7 12:18:48 Tower kernel: sd 7:0:3:0: [sde] tag#520 CDB: opcode=0x88 88 00 00 00 00 02 ba a0 f4 00 00 00 00 08 00 00
Mar  7 12:18:48 Tower kernel: print_req_error: I/O error, dev sde, sector 11721044992

 

Oh I didn't even notice that.  Thanks for the clarification!