Issue with LUNs not showing despite sd.conf set !?

Hi guys,

this is turning me crazy and I might have got blind. I have a T2000 and
a non-sun but standard SCSI disk-array attached to it with some LUNs.
Everything was OK before, but since I reinstalled the OS, I only see the
internal disks and LUN 0 for the two targets I have. So, yes, I know, as
usual adding entries in the sd.conf file solves the problem. But I did,
and ... it does not help :-( I have now spent several hours trying
different things, but in no use. I have another T2000 connected to the
second half of the same disk-array and there is no problem there. I
spent time too trying to compare my both T2000 (drivers, modules,
conf-files etc...) but did not find much and still have the problem.

Before the OS re-installation the format output looked like this
(unfortunately the tech guy didn't copy the sd.conf file)

AVAILABLE DISK SELECTIONS:
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
1. c2t0d0 <VP-1252--FB951223-VOL#00-R001 cyl 58126 alt 2 hd 28
sec 480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,0
2. c2t0d1 <VP-1252--FB951223-VOL#01-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,1
3. c2t0d2 <VP-1252--FB951223-VOL#02-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,2
4. c2t0d3 <VP-1252--FB951223-VOL#03-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,3
5. c2t0d4 <VP-1252--FB951223-VOL#04-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,4
6. c2t0d5 <VP-1252--FB951223-VOL#05-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,5
7. c2t0d6 <VP-1252--FB951223-VOL#06-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,6
8. c2t0d7 <VP-1252--FB951223-VOL#07-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,7
9. c2t1d0 <VP-1252--FB951223-VOL#08-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,0
10. c2t1d1 <VP-1252--FB951223-VOL#09-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,1
11. c2t1d2 <VP-1252--FB951223-VOL#10-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,2
12. c2t1d3 <VP-1252--FB951223-VOL#11-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,3
13. c2t1d4 <VP-1252--FB951223-VOL#12-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,4
14. c2t1d5 <VP-1252--FB951223-VOL#13-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,5
15. c2t1d6 <VP-1252--FB951223-VOL#14-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,6
16. c2t1d7 <VP-1252--FB951223-VOL#15-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,7
Specify disk (enter its number): 0


Now it looks like this:

AVAILABLE DISK SELECTIONS:
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
1. c2t0d0 <VP-1252--FB951223-VOL#00-R001 cyl 58126 alt 2 hd 28
sec 480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@0,0
2. c2t1d0 <VP-1252--FB951223-VOL#08-R001 cyl 20342 alt 2 hd 4 sec
480>
/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1/sd@1,0
Specify disk (enter its number):


My sd.conf file looks as follows:

bash-3.00# more /kernel/drv/sd.conf
#
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "@(#)sd.conf 1.10 06/02/08 SMI"

name="sd" class="scsi" class_prop="atapi" target=0 lun=0;
name="sd" class="scsi" target=0 lun=1;
name="sd" class="scsi" target=0 lun=2;
name="sd" class="scsi" target=0 lun=3;
name="sd" class="scsi" target=0 lun=4;
name="sd" class="scsi" target=0 lun=5;
name="sd" class="scsi" target=0 lun=6;
name="sd" class="scsi" target=0 lun=7;
name="sd" class="scsi" target=0 lun=8;
name="sd" class="scsi" target=0 lun=9;
name="sd" class="scsi" target=0 lun=10;
name="sd" class="scsi" target=0 lun=11;
name="sd" class="scsi" target=0 lun=12;
name="sd" class="scsi" target=0 lun=13;
name="sd" class="scsi" target=0 lun=14;
name="sd" class="scsi" target=0 lun=15;

name="sd" class="scsi" class_prop="atapi" target=1 lun=0;
name="sd" class="scsi" target=1 lun=1;
name="sd" class="scsi" target=1 lun=2;
name="sd" class="scsi" target=1 lun=3;
name="sd" class="scsi" target=1 lun=4;
name="sd" class="scsi" target=1 lun=5;
name="sd" class="scsi" target=1 lun=6;
name="sd" class="scsi" target=1 lun=7;
name="sd" class="scsi" target=1 lun=8;
name="sd" class="scsi" target=1 lun=9;
name="sd" class="scsi" target=1 lun=10;
name="sd" class="scsi" target=1 lun=11;
name="sd" class="scsi" target=1 lun=12;
name="sd" class="scsi" target=1 lun=13;
name="sd" class="scsi" target=1 lun=14;
name="sd" class="scsi" target=1 lun=15;

etc...

I can see the disk running a probe-scsi-all:

{0} ok probe-scsi-all
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2

MPT Version 1.05, Firmware Version 1.06.00.00

Target 0 Volume 0
Unit 0 Disk LSILOGICLogical Volume 3000 143243264 Blocks, 73 GB

/pci@7c0/pci@0/pci@1/pci@0,2/scsi@1
Target 0
Unit 0 Disk VP-1252-FB951223-VOL#00 R001 781248000 Blocks,
381468 MB
Unit 1 Disk VP-1252-FB951223-VOL#01 R001 39060480 Blocks,
19072 MB
Unit 2 Disk VP-1252-FB951223-VOL#02 R001 39060480 Blocks,
19072 MB
Unit 3 Disk VP-1252-FB951223-VOL#03 R001 39060480 Blocks,
19072 MB
Unit 4 Disk VP-1252-FB951223-VOL#04 R001 39060480 Blocks,
19072 MB
Unit 5 Disk VP-1252-FB951223-VOL#05 R001 39060480 Blocks,
19072 MB
Unit 6 Disk VP-1252-FB951223-VOL#06 R001 39060480 Blocks,
19072 MB
Unit 7 Disk VP-1252-FB951223-VOL#07 R001 39060480 Blocks,
19072 MB
Target 1
Unit 0 Disk VP-1252-FB951223-VOL#08 R001 39060480 Blocks,
19072 MB
Unit 1 Disk VP-1252-FB951223-VOL#09 R001 39060480 Blocks,
19072 MB
Unit 2 Disk VP-1252-FB951223-VOL#10 R001 39060480 Blocks,
19072 MB
Unit 3 Disk VP-1252-FB951223-VOL#11 R001 39060480 Blocks,
19072 MB
Unit 4 Disk VP-1252-FB951223-VOL#12 R001 39060480 Blocks,
19072 MB
Unit 5 Disk VP-1252-FB951223-VOL#13 R001 39060480 Blocks,
19072 MB
Unit 6 Disk VP-1252-FB951223-VOL#14 R001 39060480 Blocks,
19072 MB
Unit 7 Disk VP-1252-FB951223-VOL#15 R001 39060480 Blocks,
19072 MB

{0} ok


I tried rebooting boot -r a few times, it didn't help, I tried
"update_drv -f sd", "devfsadm", it didn't help, I tried drvconfig,
devlinks and disks, without success. I tried to reconfigure the HBA
through cfgadm, it didn't change anything (the HBA is connected and
configured, but it only shows one disk on each target, just like
format). I checked /etc/path_to_inst but it aligned with what format
currently shows me. I googled, but could only find pointers saying that
the sd.conf file needs to be extended, which I already did.

Again, the disk-array is a non-Sun (Fibrenetix) disk-array but it is a
standard SCSI array (no FC), fully supported on Solaris (we have a few
of these working just fine on other Sun servers).

For other details, it is of course Solaris 10 (see below) and I have
VERITAS FS/VM installed (but this should not be of any issue even if the
LUNs were earlier controlled by VERITAS, just like the two LUN 0 that I
am currently seeing).

bash-3.00# uname -a
SunOS ... 5.10 Generic_127111-06 sun4v sparc SUNW,Sun-Fire-T200
bash-3.00# more /etc/release
Solaris 10 8/07 s10s_u4wos_12b SPARC
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
bash-3.00#


I must be missing a detail somewhere, or I might have become blind.

Many thanks in advance for any suggestion!!
Regards,
/Pascal
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • SUMMARY: Issue with LUNs not showing despite sd.conf set !?
    ... a non-sun but standard SCSI disk-array attached to it with some LUNs. ... AVAILABLE DISK SELECTIONS: ... Target 0 Volume 0 ... LUNs were earlier controlled by VERITAS, just like the two LUN 0 that I ...
    (SunManagers)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... i ran tap.exe on my target syste, and rebuilt a image, that seems ... not EWF required. ... the OS to write to disk: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconElToritoCDAsDisk.asp. ... created by TD to the sdi file. ...
    (microsoft.public.windowsxp.embedded)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... the DVD model on my target is different from the one on my build ... not EWF required. ... the OS to write to disk: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconElToritoCDAsDisk.asp. ... created by TD to the sdi file. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Sharing Files between Domain and Workgroup
    ... Start diagnosis for HOME (Targets BOKPC 192.168.1.105 home 192.168.1.104) ... Target BOKPC ... Shared resources at BOKPC ... test_for_MGB-database files Disk ...
    (microsoft.public.windowsxp.network_web)
  • Re: Newbie: cant boot
    ... This often doesn't work since when you partition and format the drive if will use the PC BIOS and set up particular disk geometry parameters in the MBR and/or boot sector. ... You are better off partitioning and formatting the disk on the *target* hardware. ... flash module, inserted in on target, turned it on and error message ...
    (microsoft.public.windowsxp.embedded)