DMESG drive errors
Greetings,
I have an OEL5 system that I am trying to "fix". Im not sure my issue can be "fixed", but I would like the advice of the community. I have exhausted all my resources trying to work this problem. Any adcie would be appreciated.
I have a the following errors in my dmesg log that I would like to "take care of".
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
sd: Current: sense key: Illegal Request
Add. Sense: Logical unit not supported
sdb: test WP failed, assume Write Enabled
sdb: asking for cache data failed
sdb: assuming drive cache: write through
I have two Qlogic hba's installed on this system to communicate to the SAN and when the qla2xxx driver loads the scsi subsystem thinks there are 2 drives (sdb and sdc), but fails to communicate with them
as evidenced from:
scsi4 : qla2xxx
qla2xxx 0000:13:00.0:
QLogic Fibre Channel HBA Driver: 8.03.01.04.05.05-k
QLogic QLE2460 - PCI-Express Single Channel 4Gb Fibre Channel HBA
ISP2432: PCIe (2.5Gb/s x4) @ 0000:13:00.0 hdma+, host#=4, fw=4.04.09 (486)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com
alua: device handler registered
emc: device handler registered
rdac: device handler registered
device-mapper: multipath: version 1.0.5 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
device-mapper: multipath emc: version 0.0.3 loaded
device-mapper: dm-raid45: initialized v0.2594l
qla2xxx 0000:13:00.0: LIP reset occured (f7f7).
qla2xxx 0000:13:00.0: LOOP UP detected (4 Gbps).
Vendor: DGC Model: LUNZ Rev: 0428
Type: Direct-Access ANSI SCSI revision: 04
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
sd: Current: sense key: Illegal Request
Add. Sense: Logical unit not supported
sdb: test WP failed, assume Write Enabled
sdb: asking for cache data failed
sdb: assuming drive cache: write through
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
sd: Current: sense key: Illegal Request
Add. Sense: Logical unit not supported
sdb: test WP failed, assume Write Enabled
sdb: asking for cache data failed
sdb: assuming drive cache: write through
sdb:end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
end_request: I/O error, dev sdb, sector 0
Furthermore, my SAN disks also produce an error before the system and ID and mount them. I have the following messages fro each of my SAN disks.
SCSI device sde: 209715200 512-byte hdwr sectors (107374 MB)
sde: test WP failed, assume Write Enabled
sde: asking for cache data failed
sde: assuming drive cache: write through
SCSI device sde: 209715200 512-byte hdwr sectors (107374 MB)
sde: test WP failed, assume Write Enabled
sde: asking for cache data failed
sde: assuming drive cache: write through
sde:<6>sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
Dev sde: unable to read RDB block 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
sd 3:0:0:1: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, manual intervention required
end_request: I/O error, dev sde, sector 0
unable to read partition table
sd 3:0:0:1: Attached scsi disk sde
Vendor: DGC Model: RAID 5 Rev: 0428
Type: Direct-Access ANSI SCSI revision: 04
scsi 3:0:0:2: alua: not supported
scsi 3:0:0:2: alua: not attached
the output of multipath -ll is:
oraflesh (36006016004802200aa216fb40f24e011) dm-0 DGC,RAID 5
size=200G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 3:0:0:3 sdg 8:96 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
`- 3:0:1:3 sdk 8:160 active ready running
oradata2 (36006016004802200da0fe1470f24e011) dm-2 DGC,RAID 5
size=25G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 3:0:0:2 sdf 8:80 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
`- 3:0:1:2 sdj 8:144 active ready running
oradata1 (36006016004802200e82e39180f24e011) dm-1 DGC,RAID 5
size=100G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 3:0:1:1 sdi 8:128 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
`- 3:0:0:1 sde 8:64 active ready running
oraarc (36006016004802200a477736f0f24e011) dm-3 DGC,RAID 5
size=125G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 3:0:1:0 sdh 8:112 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
`- 3:0:0:0 sdd 8:48 active ready running
I created a ramdisk image with the following switches:
--preload=sd_mod
--preload=scsi_mod
--preload=sr_mod
--with=scsi_transport_fc
--with=qla2xxx
--with=dm_mod
--with=dm_multipath
I noticed the hwhandler='1 emc' parameter from multipath -ll, but I did not put that in my ramdisk image. If I add dm_emc to the ramdisk, should I use preload or with? Would it help with all the I/O errors? Would it help me with my sdb and sdc problem?
The system boots from a load hard drive (sda)