Messages file being flooded with failed sdb info

[bomahony]

I have a RHEL system and the messages file is being flooded with the following error since Jan2:

sdb : READ CAPACITY failed.
sdb : status=0, message=00, host=4, driver=00
sdb : sense not available.
sdb: Write Protect is off
sdb: Mode Sense: 00 00 00 00
sdb: asking for cache data failed
sdb: assuming drive cache: write through
sdb : READ CAPACITY failed.
sdb : status=0, message=00, host=4, driver=00
sdb : sense not available.
sdb: Write Protect is off
sdb: Mode Sense: 00 00 00 00
sdb: asking for cache data failed
sdb: assuming drive cache: write through
sdbev sdb: unable to read RDB block 0
unable to read partition table

It seems a USB device was plugged out on Jan 02: [Server is in a remote location so i dont know if that is actually true]

Jan 2 13:23:53 ccvobblrpr kernel: usb 2-1: USB disconnect, address 2
Jan 2 13:23:56 ccvobblrpr kernel: ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 13:23:56 ccvobblrpr kernel: ata1.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
Jan 2 13:23:56 ccvobblrpr kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 2 13:23:56 ccvobblrpr kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jan 2 13:23:56 ccvobblrpr kernel: ata1.01: status: { DRDY }
Jan 2 13:23:56 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:23:56 ccvobblrpr kernel: ata1.01: revalidation failed (errno=-2)
Jan 2 13:23:56 ccvobblrpr kernel: ata1: failed to recover some devices, retrying in 5 secs
Jan 2 13:24:01 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:24:01 ccvobblrpr kernel: ata1.01: revalidation failed (errno=-2)
Jan 2 13:24:01 ccvobblrpr kernel: ata1: failed to recover some devices, retrying in 5 secs
Jan 2 13:24:06 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:24:07 ccvobblrpr kernel: ata1.00: configured for PIO3
Jan 2 13:24:07 ccvobblrpr kernel: ata1.01: configured for PIO3
Jan 2 13:24:07 ccvobblrpr kernel: ata1: EH complete
Jan 2 13:24:39 ccvobblrpr kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 13:24:39 ccvobblrpr kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 2 13:24:39 ccvobblrpr kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 2 13:24:39 ccvobblrpr kernel: res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
Jan 2 13:24:39 ccvobblrpr kernel: ata1.00: status: { DRDY }
Jan 2 13:24:44 ccvobblrpr kernel: ata1: link is slow to respond, please be patient (ready=0)
Jan 2 13:24:45 ccvobblrpr nmbd[4128]: [2011/01/02 13:24:45, 0] nmbd/nmbd_namequery.c:query_name_response(109)
Jan 2 13:24:45 ccvobblrpr nmbd[4128]: query_name_response: Multiple (2) responses received for a query on subnet 10.10.20.33 for
name ITDESIGN2<1d>.
Jan 2 13:24:45 ccvobblrpr nmbd[4128]: This response was from IP 10.10.20.43, reporting an IP address of 10.10.20.43.
Jan 2 13:24:49 ccvobblrpr kernel: ata1: device not ready (errno=-16), forcing hardreset
Jan 2 13:24:49 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:25:03 ccvobblrpr kernel: ata1.01: revalidation failed (errno=-2)
Jan 2 13:25:03 ccvobblrpr kernel: ata1: failed to recover some devices, retrying in 5 secs
Jan 2 13:25:08 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:25:09 ccvobblrpr kernel: ata1.01: revalidation failed (errno=-2)
Jan 2 13:25:09 ccvobblrpr kernel: ata1: failed to recover some devices, retrying in 5 secs
Jan 2 13:25:14 ccvobblrpr kernel: ata1: soft resetting link
Jan 2 13:25:14 ccvobblrpr kernel: ata1.01: revalidation failed (errno=-2)
Jan 2 13:25:14 ccvobblrpr kernel: ata1.01: disabled
Jan 2 13:25:14 ccvobblrpr kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Jan 2 13:25:14 ccvobblrpr kernel: ata1.00: revalidation failed (errno=-5)
Jan 2 13:25:14 ccvobblrpr kernel: ata1: failed to recover some devices, retrying in 5 secs

So there is no sdb device attached. How do i get it to stop trying this?

[Mudgen]

I don't see where you've established that there's no sdb device attached. Is there a /dev/sdb? You may be able to just remove it. It should stay gone unless someone unplugs-replugs it, when udev will recreate the device.

[bomahony]

I was away for a bit so didnt get to return to this...

sda is a 5 volume hardware raid

sdc and sdd are two multipath iscsi connections to a network iscsi target.

There are no USB devices connected. The only thing that i could think it might be would be the Dell Virtual CDRom connected via the DRAC

[PoopNoodle]

Just to put in my 2 cents worth, I had the same thing happen. Turns out it was an mp3 player my daughter had left plugged in.

[bomahony]

Its in a server room in India. I *Hope* no one is plugging an MP3 player in!