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

From: Pascal Grostabussiat <pascal.grostabussiat_at_gmail.com>
Date: Fri Sep 05 2008 - 10:48:19 EDT
Hi,

You can find below the description of the issue I encountered for a 
while ago now. The problem was never solved. However, I thought about 
writing a summary as a colleague found yesterday that this was likely 
due to a patch issue. The reason why he suspects that is that after 
jump-starting the same server, but not installing patches during the 
jump-start (under /a), but installing patches after a reboot, the 
problem was gone. However, if jump-starting the server as we did earlier 
and installing the patches as a standard post-installation procedure 
(under /a) the problem was back. Don't ask me why !?

I had one or two questions recently about people who encountered a 
similar issue and who were asking if I had found a solution. So I am 
posting that update/summary. Which patch(es) is/are or might cause the 
trouble, I don't know !

Regards,
/Pascal

Pascal Grostabussiat wrote:
> 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@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Fri Sep 5 10:50:55 2008

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:12 EST