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

  • How to allow SSH root user access in Linux/Debian/Mint/RHEL/Ubuntu/CentOS
  • Ansible Tutorial - Playbook How To Install From Scratch and Deploy LAMP + Wordpress on Remote Server
  • Ceph Install Errors on Proxmox / How To Fix Solution
  • Proxmox Update Error https://enterprise.proxmox.com/debian/pve bullseye InRelease 401 Unauthorized [IP: 144.217.225.162 443]
  • QEMU/KVM How to Hot-add A Virtual Disk .raw/.qcow2 via QEMU Monitor Commands
  • Proxmox How To Enable Ceph Distributed Storage Cluster with OSD and Pools
  • pulseaudio issue on QEMU/KVM guest VM when microphone is replugged/unplugged pulseaudio: pa_threaded_mainloop_lock failed pulseaudio: Reason: Invalid argument
  • Ubuntu Linux Mint - Volume Control Stopped Working
  • Proxmox Services Won't Start Failed to start The Proxmox VE cluster filesystem. Proxmox VE firewall. PVE Status Daemon. Proxmox VE scheduler. PVE Cluster HA Resource Manager Daemon. PVE Local HA Resource Manager Daemon.
  • Proxmox Guide FAQ / Errors / Howto
  • Virtualbox Vbox Issue Cannot Enable Nested Virtualization Button is Grayed/Greyed Out and Unclickable HowTo Solution
  • Virtualbox VBOX Howto Port Forward To Guests
  • Linux Ubuntu Debian Centos Mint - How To Check if Intel VT-x or AMD-V Hardware Virtualization is Enabled?
  • Linux Howto Zip Multiple Files and Directories
  • Windows Cannot Format USB drive Device Media is Write Protected Error Solution
  • Linux Mint 20 cannot install snapd missing solution
  • Virtualbox VBOX How To Install Guest-Utils/GuestUtils so drag and drop and clipboard works Ubuntu Mint Debian Linux
  • How to install Kubernetes with microk8s and deploy apps on Debian/Mint/Ubuntu Linux
  • vi how to delete everything to the end of the line or the rest of the line from the cursor
  • Cisco Howto Configure Console Port/Terminal/Comm Server with Async Cable Setup