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.

 

 


  • MySQL Adding New Field to Existing Database Table
  • MySQL Cannot Update/Write to any database table solution
  • Centos How To Update to Glibc 2.14 Plus
  • php remove last letters of string
  • MySQL Maximum INT Size Truncation Issue/Warning
  • MySQL How To Add New Field Column To Existing Table
  • mysql how to reset passwords with a few commands
  • htaccess apache how deny/allow to block or allow by IP address
  • PHP geoip.so fatal error Solution
  • Syntax error on line 221 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/conf.d/php.conf: Cannot load /etc/httpd/modules/libphp5.so into server: /etc/httpd/modules/libphp5.so: cannot open shared object file: No such file or direct
  • GCC 5 on Centos 6 - How To Install
  • bash find line and replace howto
  • How To Create Apache htpasswd file
  • possible SYN flooding on ctid 42131, port 80. Sending cookies. - Solution
  • Linux last command show login by IP instead of hostname
  • Install Windows From a Linux TFTP Server instead of using WDS Solution
  • How To Secure Samba NMBD/SMBD to bind to a specific IP address
  • tftp: client does not accept options - solution if you are using UEFI PXEBoot disable it!
  • Linux how to view video card make and exact model
  • Authentication refused: bad ownership or modes for directory /home/user SSH Public Key Authentication Failed Solution