Additional Notes
(VNX series or CLARiiON Only) disconnected ghost LUNs
When a Linux host is attached to both SPs in a VNX series or CLARiiON storage system, the driver will report a disconnected LUN 0 on SPB and a failure to read the capacity of the device. The Unisphere/Navisphere Host Agent requires that disconnected LUN 0 be reported properly. A device file name is allocated to the disconnected LUN 0 in the /dev filesystem, but the device cannot be mounted, partitioned, or otherwise accessed.
Here is an example of a disconnected LUN 0 being reported:
Jul 17 14:35:57 l82bi134 kernel: sdb : READ CAPACITY failed.
Jul 17 14:35:57 l82bi134 kernel: sdb : status = 1, message = 00, host = 0, driver = 28
Jul 17 14:35:57 l82bi134 kernel: Current sd00:00: sense key Illegal Request
Jul 17 14:35:57 l82bi134 kernel: Additional sense indicates Logical unit not re dy,cause not reportable
Jul 17 14:35:57 l82bi134 kernel: sdb : block size assumed to be 512 bytes, disk size 1GB.
Jul 17 14:35:57 l82bi134 kernel: sdb: I/O error: dev 08:10, sector 0
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 2
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 4
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 6
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 0
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 2
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 4
Jul 17 14:35:58 l82bi134 kernel: I/O error: dev 08:10, sector 6
Jul 17 14:35:58 l82bi134 kernel: unable to read partition table
208
EMC Host Connectivity with QLogic FC and iSCSI HBAs and FCoE CNAs for the Linux Environment
