[OpenIndiana-discuss] mapping target number to disk?

[Dan Swartzendruber]

Thanks, Jim!  The WWN would be good enough, since all my drives (in the data
pool anyway) have the WWN printed on the top :)

-----Original Message-----
From: Jim Klimov [mailto:jim at cos.ru] 
Sent: Monday, June 11, 2012 3:08 PM
To: Discussion list for OpenIndiana
Cc: Dan Swartzendruber
Subject: Re: [OpenIndiana-discuss] mapping target number to disk?

2012-06-11 17:10, Dan Swartzendruber wrote:
> I've been seeing a ton of messages like:
>
>
>
> Jun 11 08:59:08 nas     Log info 0x31120303 received for target 9.
>
> Jun 11 08:59:08 nas     scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc
>
> Jun 11 08:59:08 nas scsi: [ID 365881 kern.info]
> /pci at 0,0/pci8086,27d0 at 1c/pci1000,3040 at 0 (mpt_sas10):
>

Actually, re-reading that original post, I have some more ideas :)
Methods 1 and 2 can help you find the OS device name that it is
complaining about. Method 3 can help find the serial number of
the disk, which should help to physically locate it.

1) Run the "format" command to list the drives. You might see
    the /pci... device string there, i.e.:
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
        0. c0t0d0 <ATA-SEAGATE ST32500N-3AZQ-232.88GB>
           /pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 0,0
        1. c0t1d0 <ATA-SEAGATE ST32500N-3AZQ-232.88GB>
           /pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
     ....

2) Run a listing of /dev/dsk and grep for the device path, i.e.:
    # ls -la /dev/dsk | grep pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
lrwxrwxrwx   1 root     root          63 Jul 14  2009 c0t1d0 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:wd
lrwxrwxrwx   1 root     root          62 Jul 14  2009 c0t1d0p0 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:q
...
lrwxrwxrwx   1 root     root          62 Jul 14  2009 c0t1d0s9 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:j



3) Search the /var/adm/messages* logs for the device path,
    this may yield the hardware details (like smartctl might).
    If your log rotation works, this may need to be done soon
    after boot, or after a pool import. Example:

# cat /var/adm/messages* | ggrep -A12 -B1 
pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
May 16 03:11:48 thumper scsi: [ID 583861 kern.info] sd10 at 
marvell88sx0: target 1 lun 0
May 16 03:11:48 thumper genunix: [ID 936769 kern.info] sd10 is 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
May 16 03:11:48 thumper genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0 (sd10) online
May 16 03:11:48 thumper sata: [ID 663010 kern.info] 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1 :
May 16 03:11:48 thumper sata: [ID 761595 kern.info]     SATA disk device 
at port 2
May 16 03:11:48 thumper sata: [ID 846691 kern.info]     model SEAGATE 
ST32500NSSUN250G 0743B590GG
May 16 03:11:48 thumper sata: [ID 693010 kern.info]     firmware     3AZQ
May 16 03:11:48 thumper sata: [ID 163988 kern.info]     serial number 
5QE590GG
May 16 03:11:48 thumper sata: [ID 594940 kern.info]     supported features:
May 16 03:11:48 thumper sata: [ID 981177 kern.info]      48-bit LBA, 
DMA, Native Command Queueing, SMART, SMART self-test
May 16 03:11:48 thumper sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
May 16 03:11:48 thumper sata: [ID 349649 kern.info]     Supported queue 
depth 32
May 16 03:11:48 thumper sata: [ID 349649 kern.info]     capacity = 
488390625 sectors
...

HTH,
//Jim Klimov