Aug 26 20:29:08 wfaltstsr085 scsi: Vendor: EMC Serial Number: 189B1000@
Aug 26 20:29:08 wfaltstsr085 scsi: Sense Key: Not_Ready
Aug 26 20:29:08 wfaltstsr085 scsi: ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0
I have tried everything I found on google but I can't label and use this disk. Anyone have any idea what could be wrong? I don't have access to the EMC SAN myself but the IT guy says everything looks ok on his side.
One possibility, which is on the array side, is that the admin presented you a TDEV, but did not bind it to a pool. So if you can, ask him if it’s bound. I assume he check the device itself to confirm it is indeed not in a “not_ready” state.
It looks like you are using Solaris MPxIO. Have you configured mpxio for Symmetrix? You need to set certain parameters in the /kernel/drv/scsi_vhci.conf file, such as:
The number of spaces in the string above must be 5, as shown above. You also need to set /kernel/drv/fp.conf to contain:
Mpxio-disable=”no”;
You then need to do a reboot -- -r
More help is available in the “EMC Host Connectivity Guide for Oracle Solaris”. Assuming this message doesn’t stay in the moderation queue too long, post your results, I’m up late this evening on a maintenance window and can help. One more thing. If you are still having problems, please run the inq command. You can download it from emc at:
ftp://ftp.emc.com/pub/elab/inquiry/v7.3.2.0/
Download the appropriate version based on your os (probably inq.sol64), then post the results back here. Good luck!
That's exactly how I set the multipathing up - didn't really think about the 5 spaces so I just doublechecked now but it's the same result error as before.
messages:
Aug 27 10:28:08 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:08 wfaltstsr085 Corrupt label; wrong magic number
Aug 27 10:28:32 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:32 wfaltstsr085 drive offline
Aug 27 10:28:34 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:34 wfaltstsr085 drive offline
Aug 27 10:28:36 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:36 wfaltstsr085 drive offline
Aug 27 10:28:36 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:36 wfaltstsr085 drive offline
Aug 27 10:28:36 wfaltstsr085 scsi: WARNING: /scsi_vhci/ssd@g60000970000298701218533030394231 (ssd0):
Aug 27 10:28:36 wfaltstsr085 Error for Command: read(10) Error Level: Fatal
Ask your SAN guy for the output from symdev show 9b1 -sid 218 , this will tell you everything you need to know about this device. It may be that the device is ACLX or unbound, in any case we'll be able to figure out from this command output
storagtetalk
1 Rookie
•
53 Posts
1420
1
Posted August 26th, 2015 19:00
One possibility, which is on the array side, is that the admin presented you a TDEV, but did not bind it to a pool. So if you can, ask him if it’s bound. I assume he check the device itself to confirm it is indeed not in a “not_ready” state.
It looks like you are using Solaris MPxIO. Have you configured mpxio for Symmetrix? You need to set certain parameters in the /kernel/drv/scsi_vhci.conf file, such as:
load-balance="round-robin";
auto-failback="enable";
device-type-scsi-options-list="EMC SYMMETRIX", "symmetric-option";
symmetric-option=0x1000000;
The number of spaces in the string above must be 5, as shown above. You also need to set /kernel/drv/fp.conf to contain:
Mpxio-disable=”no”;
You then need to do a reboot -- -r
More help is available in the “EMC Host Connectivity Guide for Oracle Solaris”. Assuming this message doesn’t stay in the moderation queue too long, post your results, I’m up late this evening on a maintenance window and can help. One more thing. If you are still having problems, please run the inq command. You can download it from emc at:
ftp://ftp.emc.com/pub/elab/inquiry/v7.3.2.0/
Download the appropriate version based on your os (probably inq.sol64), then post the results back here. Good luck!