Not able to add LUN

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!

device is not write_disable or not ready ?

I asked IT support to check the LUN on their side but he says everything looks fine there so I'm guessing no..

Hi,

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

Aug 27 10:28:36 wfaltstsr085 scsi:      Requested Block: 0                         Error Block: 0

Aug 27 10:28:36 wfaltstsr085 scsi:      Vendor: EMC                                Serial Number: 189B1000@

Aug 27 10:28:36 wfaltstsr085 scsi:      Sense Key: Not_Ready

Aug 27 10:28:36 wfaltstsr085 scsi:      ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0

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

Aug 27 10:28:36 wfaltstsr085 scsi:      Requested Block: 0                         Error Block: 0

Aug 27 10:28:36 wfaltstsr085 scsi:      Vendor: EMC                                Serial Number: 189B1000@

Aug 27 10:28:36 wfaltstsr085 scsi:      Sense Key: Not_Ready

Aug 27 10:28:36 wfaltstsr085 scsi:      ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0

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

Aug 27 10:28:36 wfaltstsr085 scsi:      Requested Block: 0                         Error Block: 0

Aug 27 10:28:36 wfaltstsr085 scsi:      Vendor: EMC                                Serial Number: 189B1000@

Aug 27 10:28:36 wfaltstsr085 scsi:      Sense Key: Not_Ready

Aug 27 10:28:36 wfaltstsr085 scsi:      ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0

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

Aug 27 10:28:36 wfaltstsr085 scsi:      Requested Block: 0                         Error Block: 0

Aug 27 10:28:36 wfaltstsr085 scsi:      Vendor: EMC                                Serial Number: 189B1000@

Aug 27 10:28:36 wfaltstsr085 scsi:      Sense Key: Not_Ready

Aug 27 10:28:36 wfaltstsr085 scsi:      ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0

The Inq I have installed gives the following:

Inquiry utility, Version V7.6.2.0 (Edit Level: 1808) built with SYMAPI Version V7.6.2.0 (Edit Level 1808)

Copyright (c) [1997-2013] EMC Corporation. All Rights Reserved.

For help type inq -h.
........
------------------------------------------------------------------------------------------------------------

DEVICE                                            :VEND    :PROD            :REV   :SER NUM    :CAP(kb)

------------------------------------------------------------------------------------------------------------

/dev/rdsk/c0t0d0s2                                :LSILOGIC:Logical Volume  :3000  :LSI Inte   :    71556295

/dev/rdsk/c0t2d0s2                                :HITACHI :H101473SCSUN72G :SA23  :0743DB0X   :    71687369

/dev/rdsk/c4t60000970000298701218533030394231d0s2 :EMC     :SYMMETRIX       :5876  :18009b1000 :   537600000

I should perhaps mention that without setting multipathing up, I get errors saying:

ug 26 23:12:04 wfaltstsr085 scsi: WARNING: /pci@7c0/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w50000975f013098c,0 (ssd4):

Aug 26 23:12:04 wfaltstsr085    Corrupt label; wrong magic number

Aug 26 23:12:04 wfaltstsr085 scsi: WARNING: /pci@7c0/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w50000975f0130984,0 (ssd3):

Aug 26 23:12:04 wfaltstsr085    Corrupt label; wrong magic number

Aug 26 23:12:04 wfaltstsr085 scsi: WARNING: /pci@7c0/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w50000975f013098c,0 (ssd4):

Aug 26 23:12:04 wfaltstsr085    Corrupt label; wrong magic number

Aug 26 23:12:04 wfaltstsr085 scsi: WARNING: /pci@7c0/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w50000975f013098c,0 (ssd4):

Aug 26 23:12:04 wfaltstsr085    Corrupt label; wrong magic number

Aug 26 23:12:04 wfaltstsr085 scsi: WARNING: /pci@7c0/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w50000975f0130984,0 (ssd3):

Trying to label the disk in format does not work:
format> label

[0] SMI Label

[1] EFI Label

Specify Label type[0]: 0

Ready to label disk, continue? y
Warning: error writing VTOC.

Warning: no backup labels

Label failed.
Analyze gives errors:
analyze> test

Ready to analyze (won't harm data). This takes a long time,

but is interruptable with CTRL-C. Continue? y
       pass 0 - pattern = 0xc6dec6de

Not ready error during write

ASC: 0x4   ASCQ: 0x3

Warning: unable to restore original data.

Warning: Drive not ready, aborting surface analysis.
Messages:

Aug 11 22:43:42 wfaltstsr085    Error for Command: write                   Error Level: Fatal

Aug 11 22:43:42 wfaltstsr085 scsi:      Requested Block: 0                         Error Block: 0

Aug 11 22:43:42 wfaltstsr085 scsi:      Vendor: EMC                                Serial Number: 189B1000@

Aug 11 22:43:42 wfaltstsr085 scsi:      Sense Key: Not_Ready

Aug 11 22:43:42 wfaltstsr085 scsi:      ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0

I can't overwrite the current VTOC:
# dd if=/dev/null of=/dev/rdsk/c2t50000975F0130980d0s2

dd: /dev still /rdsk/c2t50000975F0130980d0s2: open: I/O error

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

The problem was that the LUN had not been been bound to any storage pool.

Thankyou all for your input.

Thanks for this. I asked for IT support for this and he emailed me back that the device was not bound to any storage pool.

He has now fixed it and everything looks normal again

That has burned me all too often...

You'll be happy to hear the concept of having to bind LUNS has gone away with VMAX3.