Unsolved
This post is more than 5 years old
2 Posts
0
5974
how to clean devices are seen by the format in solaris removed after?
I have a CX3-80 connected to a host with solaris 10, powerpath 5.3, already assigned 3 devices with id 3, 4 and 5. but there is a disk with id 0 and is not assigned, the disk appear on format like this:
4. c2t5006016839A02DE0d0
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016839a02de0,0
5. c2t5006016239A02DE0d0
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016239a02de0,0
6. c2t5006016839A02DE0d3
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016839a02de0,3
7. c2t5006016239A02DE0d3
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016239a02de0,3
8. c2t5006016239A02DE0d4
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016239a02de0,4
9. c2t5006016839A02DE0d4
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016839a02de0,4
10. c2t5006016839A02DE0d5
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016839a02de0,5
11. c2t5006016239A02DE0d5
/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016239a02de0,5
12. c5t5006016A39A02DE0d0
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016a39a02de0,0
13. c5t5006016A39A02DE0d3
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016a39a02de0,3
14. c5t5006016A39A02DE0d4
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016a39a02de0,4
15. c5t5006016A39A02DE0d5
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016a39a02de0,5
16. c5t5006016039A02DE0d0
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016039a02de0,0
17. c5t5006016039A02DE0d3
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016039a02de0,3
18. c5t5006016039A02DE0d4
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016039a02de0,4
19. c5t5006016039A02DE0d5
/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016039a02de0,5
20. emcpower0a
/pseudo/emcp@0
21. emcpower1a
/pseudo/emcp@1
22. emcpower2a
/pseudo/emcp@2
My question is how to clean the disk will not appear when running format, and the server was rebooted with the option "reboot -- -r"
Thank you in advance
mov1
2 Posts
0
August 30th, 2011 09:00
solution found in primus ID: emc152477
"Why do I see LUNZ in inq or in format on a Solaris host?"
FIX:
The Host LUN ID (HLU) is a direct correlation to the dX value in the Solaris device file, cXtXdX. If you are experiencing this issue then format will show only on the cxtxd0 devices.
Use the following procedure to determine whether you have HLU 0 assigned to the server:
(References to the fixes for Navisphere Manager will also apply to the Invista Element manager)
1. In the Navisphere Manager Enterprise Storage window, click the “Hosts” tab.
2. Right-click the host and choose “Properties.”
3. Click on the “Storage” tab.
The chart listed will show you the relationship between the Array LUN ID (ALU) and the Host LUN ID (HLU). To experience this issue there will not be a Host LUN ID 0.
Use one of the following procedures to remove the LUNZ devices from the Solaris host.
1. Add another LUN to the storage group. Navisphere Manager will by default assign the lowest Host ID to a new LUN. In this case it would be Host ID 0.
a. In Navisphere Manager, right-click the Host’s Storage group and choose “Select LUNs.”
b. Move the LUN from the “Available LUNs” field to the “Selected LUNs” field.
c. Click “Apply” and then “OK.”
d. Run devfsadm –C on the Solaris server.
2. Remove an existing LUN from the Storage Group and add it back in.
a. In Navisphere Manager, right-click the Host’s Storage group and choose “Select LUNs”
b. Move a LUN from the “Selected LUNs” field to the “Available LUNs” field.
c. Click “Apply.”
d. Move the LUN from the “Available LUNs” field to the “Selected LUNs” field.
e. Click “Apply.”
f. Scroll the “Selected LUNs” field to the right and verify the “Host ID” column now has a 0.
g. Click “OK.”
h. Run devfsadm –C on the Solaris server.
Caution! This procedure requires down time as you will be taking access to the LUN away from the server.
3. Using the “Failover Setup Wizard” or “Group Edit” disable the “ArraycommPath” variable in Navisphere Manager.
Caution! This procedure requires a reboot -- -r to work successfully.
If using the Emulex lpfc or the QLogic QLA drivers you can use the following procedure:
4. Comment out the lun=0 value for each Clariion target in the /kernel/drv/sd.conf file.
#name="sd" parent="lpfc" target=16 lun=0;
#name="sd" parent="lpfc" target=17 lun=0;
etc…
#name="sd" target=16 lun=0;
#name="sd" target=17 lun=0;
etc...
Caution! If you are binding HBA instances to targets 0-15, this procedure is not valid because Solaris can use these targets for internal purposes. This procedure will require a reboot to take effect.