Linux shows my drive as being dead is it really? Buffer I/O error on device sdb, logical block 0 sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00

Normally the below would indicate a failing or failed drive.  In this case the SATA port was unplugged and sometimes the Linux kernel/motherboard even with AHCI just don't play nice and can't handle it.

What happened is I plugged in a new drive after removing another one.  However the log shows that after the old drive was plugged in the Linux kernel kept complaining thinking the drive was there but not responding properly.  This continued even with reseating the new drive.
So if you've removed an old drive/dead drive and the port doesn't work on the new one, don't assume your new drive is DOA.  Instead reboot or try a new SATA port to be sure.

May 23 15:01:03 box2 kernel: __ratelimit: 1401 callbacks suppressed
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
May 23 15:01:03 box2 kernel: __ratelimit: 1402 callbacks suppressed
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:03 box2 kernel: __ratelimit: 1471 callbacks suppressed
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 0
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 1
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 2
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 3
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 0
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 3a 38 60 28 00 00 08 00
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 976773160
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 122096645
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 3a 38 60 28 00 00 08 00
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 976773160
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 122096645
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 0
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 1
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:03 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
May 23 15:01:03 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:03 box2 kernel: Buffer I/O error on device sdb, logical block 0
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
May 23 15:01:07 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
May 23 15:01:07 box2 kernel: end_request: I/O error, dev sdb, sector 0
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 3a 38 60 28 00 00 08 00
May 23 15:01:07 box2 kernel: end_request: I/O error, dev sdb, sector 976773160
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 23 15:01:07 box2 kernel: sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 3a 38 60 28 00 00 08 00
May 23 15:01:07 box2 kernel: end_request: I/O error, dev sdb, sector 976773160

As we can see the same drive comes up fine on another port.

However the drive was working fine and kept throwing errors like above so a reboot was required. This is the first time I've seen an issue like this.  It seems like the other port's issue affected the entire bus from working with any new device.

 

 

Latest Articles

  • AMD Set Fan Speed and Other Powerplay Memory/CPU Timings with a Linux script
  • Ethereum Mining Claymore Nanopool Error
  • genisoimage errors with long filenames and deep directory structures
  • Linux Kernel USB Export Errors
  • How to download gajim 0.16.9 XMPP/Jabber client so you can use OMEMO encryption
  • HP DL385 G7 Linux BIOS Update Flash
  • hwloc-nox set CPU affinity in Linux
  • Firefox An error occurred during a connection to some-ip-or-domain. SSL peer reports incorrect Message Authentication Code. Error code: SSL_ERROR_BAD_MAC_ALERT Solution
  • Proxmox understanding the directory structure and why an NFS datastore appears to be missing files/isos
  • pandoc convert markdown to html
  • Proxmox error uploading an iso solution
  • Cannot install moodle
  • MySQL change for Antelope format to Barracuda error solution
  • vmkping -I vmk1 10.0.2.69 PING 10.0.2.69 (10.0.2.69): 56 data bytes sendto() failed (Host is down)
  • gvfs mount in /run/user cannot be accessed or displayed wrong permissions
  • VMWare vSphere 6.7 Errors Solution 503 Service Unavailable (Failed to connect to endpoint:
  • How To Enable Nested KVM so guests can virtualize with hardware extensions
  • vi error solution E166: Can't open linked file for writing
  • Supermicro IPMI / KVM / BMC Remote Console Screen Resizing Issue - Window Cut Off Solution
  • Linux bash shell doesn't show username, hostname or current path fix solution