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 -

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.

 

 


  • How to Update Linux /usr/share/misc/pci.ids
  • pcimodules and lspci not working alternative solution
  • How to disable Google Fonts in Wordpress
  • Unable to load dynamic library /usr/lib64/php/modules/php_openssl
  • mysqld in Linux hacked
  • W: GPG error: http://archive.debian.org squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AED4B06F473041FA NO_PUBKEY 64481591B98321F9
  • cannot mount kvm ntfs image
  • h264 DVR security camera footage cannot be played
  • dhcpd.conf how to secure so only known and allowed clients will be given dhcpd IP address leases
  • Thunderbird E-mail List Blank White but e-mails still clickable and viewable
  • css responsive images
  • responsive table without changing much code solution
  • yum how to install old obsolete packages
  • PHP Howto Store Value of Included File Output Into Variable
  • PHP Migration from 5.3 to 5.4+ and dealing with deprecated functions
  • ffmpeg vidstab to stabilize video
  • userdel user userdel: cannot lock /etc/passwd; try again later.
  • mdadm how to mount inactive array
  • How to find and mount mdadm arrays automatically
  • M2Crypto.SSL.Checker.WrongHost: Peer certificate subjectAltName does not match host, expected fedora-archive.ip-connect.vn.ua, got DNS:mirror.ip-connect.vn.ua