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.

 

 


Tags:

linux, buffer, sdb, cdb, indicate, failing, sata, unplugged, kernel, motherboard, ahci, plugged, removing, responding, continued, reseating, ve, doesn, doa, reboot, __ratelimit, callbacks, suppressed, hostbyte, did_bad_target, driverbyte, driver_ok, end_request, dev, sector, errors,

Latest Articles

  • Linux ln symlink how to update existing symbolic link
  • Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution
  • LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive
  • How to use nmap locate other machines/computers/servers on your network using nmap
  • Linux Mint 18.2 Create Config File To Start Application Upon Login
  • Dell Wyse Thin Client BIOS Access Key
  • sudoers file in /etc warning about comments/includes!
  • Centos 7 Reallocate logical volume space to another
  • lvm how to reduce volume size
  • letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."
  • SSH error cannot Forward or Listen "bind: Cannot assign requested address"
  • X11 SSH Linux Forwarding Error
  • Using Microsoft's Group Policy Management Editor (GPME) To Change Default Permissions and Internet Explorer Security Settings
  • Thunderbird How To Disable An Email Account
  • iptables linux firewall recommended rules for public computing
  • LVM How To Create Pool (dynamically allocated and not fully allocated)
  • VMWare Pro Workstation Nic Disconnected and No IP Using NAT
  • Linux How To Create A RamDisk
  • mdadm force resync when resync=PENDING solution
  • Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG