Format cannot see newly created LUNs
(Doc ID 1535112.1)
Last updated on APRIL 01, 2024
Applies to:
Solaris Operating System - Version 10 10/08 U6 and laterInformation in this document applies to any platform.
Symptoms
New LUNS 12 and 13 added but can't see them in format:
1. The new LUNs can be seen in cfgadm:
c4 fc-fabric connected configured unknown
:
c4::23540002ac00093a,12 disk connected configured unknown <====
c4::23540002ac00093a,13 disk connected configured unknown <====
c7 fc-fabric connected configured unknown
:
c7::23340002ac00093a,12 disk connected configured unknown <====
c7::23340002ac00093a,13 disk connected configured unknown <====
2 . fcinfo remote-port also sees the new LUNs:
root># fcinfo remote-port -sl -p 210000e08b8f28c2
Remote Port WWN: 22540002ac00093a
Active FC4 Types: SCSI
SCSI Target: yes
Node WWN: 2ff70002ac00093a
Link Error Statistics:
Link Failure Count: 0
Loss of Sync Count: 2
Loss of Signal Count: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 7
Invalid CRC Count: 0
LUN: 12
Vendor: 3PARdata
Product: VV
OS Device Name: /devices/scsi_vhci/ssd@g50002ac0008b093a:c,raw
LUN: 13
Vendor: 3PARdata
Product: VV
OS Device Name: /devices/scsi_vhci/ssd@g50002ac0008c093a:c,raw
3. devfsadm -Cv returns no error
4. A reconfiguration reboot did not fix the problem.
The new LUNs are still not seen in format:
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/scsi_vhci/ssd@g500000e017ad5f50
1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/scsi_vhci/ssd@g500000e017ad0cb0
2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/scsi_vhci/ssd@g500000e017ac7420
3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/scsi_vhci/ssd@g500000e017ad5f70
4. c2t50002AC0008D093Ad0 <3PARdata-VV-0000 cyl 65533 alt 2 hd 8 sec 400>
/scsi_vhci/ssd@g50002ac0008d093a
5. c2t50002AC0008E093Ad0 <3PARdata-VV-0000 cyl 65533 alt 2 hd 8 sec 400>
/scsi_vhci/ssd@g50002ac0008e093a
6. c2t50002AC00088093Ad0 <3PARdata-VV-0000 cyl 65533 alt 2 hd 8 sec 400>
/scsi_vhci/ssd@g50002ac00088093a
7. ocr1 <3PARdata-VV-0000 cyl 860 alt 2 hd 8 sec 304>
/scsi_vhci/ssd@g50002ac00083093a
8. ocr2 <3PARdata-VV-0000 cyl 860 alt 2 hd 8 sec 304>
/scsi_vhci/ssd@g50002ac00084093a
9. oradata1 <3PARdata-VV-0000 cyl 65533 alt 2 hd 16 sec 600>
/scsi_vhci/ssd@g50002ac00085093a
10. oradata2 <3PARdata-VV-0000 cyl 65533 alt 2 hd 8 sec 400>
/scsi_vhci/ssd@g50002ac00086093a
11. oradata3 <3PARdata-VV-0000 cyl 65533 alt 2 hd 8 sec 400>
/scsi_vhci/ssd@g50002ac00087093a
12. voting1 <3PARdata-VV-0000 cyl 860 alt 2 hd 8 sec 304>
/scsi_vhci/ssd@g50002ac00080093a
13. voting2 <3PARdata-VV-0000 cyl 860 alt 2 hd 8 sec 304>
/scsi_vhci/ssd@g50002ac00081093a
14. voting3 <3PARdata-VV-0000 cyl 860 alt 2 hd 8 sec 304>
/scsi_vhci/ssd@g50002ac00082093a
Notice the unusual device names ocr1, ocr2 ...
Changes
The user has manually added device symbolic links in /dev/rdsk
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |