System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

sense key: Not Ready ; Add. Sense: Logical unit not ready

 
skt_skt
Honored Contributor

sense key: Not Ready ; Add. Sense: Logical unit not ready


Red Hat Enterprise Linux Server release 5.1 (Tikanga)

LINUX system got hung with the following errors given below prior to that .Both Sense key and Additional Sense Code indicates an error at the device level; am i right?
The device in quetions is part of live Red Hat cluster/VG

#powermt display dev=sdbf
Pseudo name=emcpowern
Symmetrix ID=xxxxxxxxxxxxxx
Logical device ID=0770
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
3 qla2xxx sdac FA 13dA active alive 0 0
4 qla2xxx sdbf FA 4dA active alive 0 0


May 9 16:50:03 adeld194p kernel: qla2400 0000:08:03.0: scsi(3:0:4:0): Enabled tagged queuing, queue depth 32.
May 9 16:50:03 adeld194p kernel: SCSI device sdbf: 125829120 512-byte hdwr sectors (64425 MB)
May 9 16:50:03 adeld194p kernel: sdbf: test WP failed, assume Write Enabled
May 9 16:50:03 adeld194p kernel: sdbf: asking for cache data failed
May 9 16:50:03 adeld194p kernel: sdbf: assuming drive cache: write through
May 9 16:50:03 adeld194p kernel: SCSI device sdbf: 125829120 512-byte hdwr sectors (64425 MB)
May 9 16:50:03 adeld194p kernel: sdbf: test WP failed, assume Write Enabled
May 9 16:50:03 adeld194p kernel: sdbf: asking for cache data failed
May 9 16:50:03 adeld194p kernel: sdbf: assuming drive cache: write through
May 9 16:50:03 adeld194p kernel: sdbf:<6>sd 3:0:4:0: Device not ready: <6>: Current: sense key: Not Ready
May 9 16:50:03 adeld194p kernel: Add. Sense: Logical unit not ready, manual intervention required
May 9 16:50:03 adeld194p kernel:
May 9 16:50:03 adeld194p kernel: end_request: I/O error, dev sdbf, sector 0

May 9 16:50:04 adeld194p kernel: end_request: I/O error, dev sdbf, sector 0
May 9 16:50:04 adeld194p kernel: sd 3:0:4:0: Device not ready: <6>: Current: sense key: Not Ready
May 9 16:50:04 adeld194p kernel: Add. Sense: Logical unit not ready, manual intervention required
May 9 16:50:04 adeld194p kernel:
May 9 16:50:04 adeld194p kernel: end_request: I/O error, dev sdbf, sector 0
May 9 16:50:04 adeld194p kernel: sd 3:0:4:0: Device not ready: <6>: Current: sense key: Not Ready
May 9 16:50:04 adeld194p kernel: Add. Sense: Logical unit not ready, manual intervention required
May 9 16:50:04 adeld194p kernel:
May 9 16:50:04 adeld194p kernel: end_request: I/O error, dev sdbf, sector 0
May 9 17:15:13 adeld194p syslogd 1.4.1: restart.
2 REPLIES
Matti_Kurkela
Honored Contributor

Re: sense key: Not Ready ; Add. Sense: Logical unit not ready

Yes. The storage system is using the SCSI sense codes to tell you that the storage system has a problem of some kind.

Is that an EMC Symmetrix storage system? If you don't have SAN admin access, find someone who has.

With admin access, something like "symevent list -error" might help you understand what is going on.

MK
MK
skt_skt
Honored Contributor

Re: sense key: Not Ready ; Add. Sense: Logical unit not ready

i noticed that the messages are appearing when scanning for newly added LUNs. Looks the scanning tool/utlity is causing contributing to the problem and causing system hang/reboot