| Asset ID: |
1-75-1499897.1 |
| Update Date: | 2017-04-25 |
| Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1499897.1
:
Troubleshooting guide to find the faulty disk in a Raid Volume for systems who contains LSI 1064/1064E/1068/1068E SAS Controller
| Related Items |
- Solaris Operating System
- Sun SPARC Enterprise T2000 Server
|
| Related Categories |
- PLA-Support>Sun Systems>SPARC>CMT>SN-SPARC: Tx000
- _KM>Content>Procedures and Guidelines
|
In this Document
Applies to:
Sun SPARC Enterprise T2000 Server - Version All Versions and later
Solaris SPARC Operating System - Version 10 3/05 to 10 3/05 [Release 10.0]
Information in this document applies to any platform.
Purpose
Provide a clear (troubleshooting) guide.
For finding/locating the faulty disk in a Raid Volume for systems which contains a LSI 1064/1064E/1068/1068E SAS Controller.
Just for the clarification: The system used: Sun Fire T2000 (where most of the problems are reported on), for other systems just look at the System Handbook.
Troubleshooting Steps
*Hereby just an overview of the T2000 with 4x disks installed (NO RAID Volumes):*
Tx000
-----
sc> showenvironment
=============== Environmental Status ===============
--------------------------------------------
System Disks:
--------------------------------------------
Disk Status Service OK2RM
--------------------------------------------
HDD0 OK OFF OFF
HDD1 OK OFF OFF
HDD2 OK OFF OFF
HDD3 OK OFF OFF
--------------------------------------------
SOLARIS
-------
RAID COMMANDS
-------------
# raidctl
Controller: 1
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.2.0
Disk: 0.3.0
# raidctl -l 1
Controller Type Version
----------------------------------------------------------------
c1 LSI_1064E 1.06.00.00
# raidctl -l c1t0d0
Device not found.
# raidctl -l c1t1d0
Device not found.
# raidctl -l c1t2d0
Device not found.
# raidctl -l c1t3d0
Device not found.
# raidctl -l -g 0.0.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.0.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e01179ca30
# raidctl -l -g 0.1.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.1.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e011622dc0
# raidctl -l -g 0.2.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.2.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e011746360
# raidctl -l -g 0.3.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.3.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e011551c00
# raidctl -S 1
1 "LSI_1064E"
# raidctl -S c1t0d0
Device not found.
# raidctl -S c1t1d0
Device not found.
# raidctl -S c1t2d0
Device not found.
# raidctl -S c1t3d0
Device not found.
# raidctl -S -g 0.0.0 1
0.0.0 GOOD
# raidctl -S -g 0.1.0 1
0.1.0 GOOD
# raidctl -S -g 0.2.0 1
0.2.0 GOOD
# raidctl -S -g 0.3.0 1
0.3.0 GOOD
SOLARIS COMMANDS
----------------
# ls -al /dev/cfg/c1
lrwxrwxrwx 1 root root 61 Jan 18 2011 /dev/cfg/c1 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi
# ls -al /dev/dsk/c1*s0
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t0d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0:a
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t1d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0:a
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t2d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0:a
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t3d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0:a
# cfgadm -alv
Ap_Id Receptacle Occupant Condition Information When Type Busy Phys_Id
c1 connected configured unknown unavailable scsi-sata n
/devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi
c1::dsk/c1t0d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t0d0
c1::dsk/c1t1d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t1d0
c1::dsk/c1t2d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t2d0
c1::dsk/c1t3d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t3d0
# format
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0
# iostat -iEn
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e01179ca30
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e011622dc0
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c1t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e011746360
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c1t3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e011551c00
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
# prtdiag -v
System Configuration: Sun Microsystems sun4v Sun Fire T200
============================ Environmental Status ============================
LEDs:
----------------------------------------------------------------
Location LED State
----------------------------------------------------------------
CH/HDD0 SERVICE off
CH/HDD0 OK2RM off
CH/HDD1 SERVICE off
CH/HDD1 OK2RM off
CH/HDD2 SERVICE off
CH/HDD2 OK2RM off
CH/HDD3 SERVICE off
CH/HDD3 OK2RM off
# grep "/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2" /etc/path_to_inst
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2" 0 "mpt"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0" 0 "sd"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0" 1 "sd"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0" 3 "sd"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0" 4 "sd"
# prtconf -vp
Node 0xf02f1fe8
firmware-version : '1.06.00.00'
mpt-version : '1.05'
model : 'LSI,1064'
version : '1.00.40'
name : 'LSILogic,sas'
revision-id : 00000002
# prtpicl -v
LSILogic,sas (scsi-2, 9b00000557)
:Label PCIX0
:revision-id 0x2
:version 1.00.40
:model LSI,1064
:mpt-version 1.05
:firmware-version 1.6.0.0
:nvdata-version-default 0
:nvdata-version-persistent 0
:num-phys 0x4
:initiator-port 500062b00000d310
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
:name LSILogic,sas
sd (block, 9b00000592)
:target-port 500000e01179ca32
:port-wwn 50 00 00 e0 11 79 ca 32
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e01179ca30
:target 0
:lun 0
:inquiry-serial-no 000545S00TDH
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
:instance 0
sd (block, 9b000005b7)
:target-port 500000e011622dc2
:port-wwn 50 00 00 e0 11 62 2d c2
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e011622dc0
:target 0x1
:lun 0
:inquiry-serial-no 000538S00BTS
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
:instance 1
sd (block, 9b000005db)
:target-port 500000e011746362
:port-wwn 50 00 00 e0 11 74 63 62
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e011746360
:target 0x2
:lun 0
:inquiry-serial-no 000544S00LYM
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
:instance 3
sd (block, 9b000005ff)
:target-port 500000e011551c02
:port-wwn 50 00 00 e0 11 55 1c 02
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e011551c00
:target 0x3
:lun 0
:inquiry-serial-no 000533S009AM
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0
:instance 4
disk_discovery (picl, 9b000007bc)
disk (disk, 9b000007bf)
:State configured
:Location HDD0
:Path /pci@780/pci@0/pci@9/scsi@0/sd@0,0
disk (disk, 9b000007c5)
:State configured
:Location HDD1
:Path /pci@780/pci@0/pci@9/scsi@0/sd@1,0
disk (disk, 9b000007cb)
:State configured
:Location HDD2
:Path /pci@780/pci@0/pci@9/scsi@0/sd@2,0
disk (disk, 9b000007d1)
:State configured
:Location HDD3
:Path /pci@780/pci@0/pci@9/scsi@0/sd@3,0
OBP
---
ok setenv auto-boot? false
auto-boot? = false
ok setenv fcode-debug? true
fcode-debug? = true
ok reset-all
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
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e01179ca32 PhyNum 0
Target 1
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011622dc2 PhyNum 1
Target 2
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011746362 PhyNum 2
Target 3
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011551c02 PhyNum 3
ok select scsi (or select /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2)
ok .properties
firmware-version 1.06.00.00
mpt-version 1.05
model LSI,1064
version 1.00.40
name LSILogic,sas
ok show-sas-wwid
SAS World Wide ID is 500062b0 0000d310
ok show-children
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
MPT Version 1.05, Firmware Version 1.06.00.00
Target 0
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e01179ca32 PhyNum 0
Target 1
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011622dc2 PhyNum 1
Target 2
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011746362 PhyNum 2
Target 3
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011551c02 PhyNum 3
ok show-volumes
No volumes to show
ok unselect-dev
ok setenv fcode-debug? false
ok setenv auto-boot? true
ok reset-all
So as you can see when there are NO RAID Volumes, the SAS addressing (Persistent
mapping:Enabled, Physical mapping type:Direct Attach) is as follow:
PhyNum C.ID.L HDD/DISK
0 0.0.0 0 FUJITSU MAV2073RCSUN72G 0301 500000e01179ca32
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 id1,sd@n500000e01179ca30 c1t0d0 (sd0)
1 0.1.0 1 FUJITSU MAV2073RCSUN72G 0301 500000e011622dc2
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0 id1,sd@n500000e011622dc0 c1t1d0 (sd1)
2 0.2.0 2 FUJITSU MAV2073RCSUN72G 0301 500000e011746362
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0 id1,sd@n500000e011746360 c1t2d0 (sd3)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 500000e011551c02
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0 id1,sd@n500000e011551c00 c1t3d0 (sd4)
*Lets create a RAID Volume (RAID1, IM) of:*
PhyNum C.ID.L HDD/DISK
1 0.1.0 1 FUJITSU MAV2073RCSUN72G 0301 500000e011622dc2
/pci@780/pci@0/pci@9/scsi@0/sd@1,0 id1,sd@n500000e011622dc0 c1t1d0 (sd1)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 500000e011551c02
/pci@780/pci@0/pci@9/scsi@0/sd@3,0 id1,sd@n500000e011551c00 c1t3d0 (sd3)
# raidctl -c -r 1 c1t1d0 c1t3d0
Creating RAID volume will destroy all data on spare space of member disks, proceed
(yes/no)? yes
Volume c1t1d0 is created successfully!
And hereby the logging:
messages
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk 0 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk 1 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||optimal|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||optimal|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk (target 3) is |out of sync||online|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||degraded|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||resyncing||degraded|
And lets collect some information
SOLARIS
-------
RAID COMMANDS
-------------
# raidctl
Controller: 1
Volume:c1t1d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.2.0
Disk: 0.3.0
# raidctl -l 1
Controller Type Version
----------------------------------------------------------------
c1 LSI_1064E 1.06.00.00
# raidctl -l c1t0d0
Device not found.
# raidctl -l c1t1d0
Volume Size Stripe Status Cache RAID
Sub Size Level
Disk
----------------------------------------------------------------
c1t1d0 68.3G N/A SYNC OFF RAID1
0.1.0 68.3G GOOD
0.3.0 68.3G GOOD
# raidctl -l c1t2d0
Device not found.
# raidctl -l c1t3d0
Device not found.
# raidctl -l -g 0.0.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.0.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e01179ca30
# raidctl -l -g 0.1.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.1.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
# raidctl -l -g 0.2.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.2.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
GUID:500000e011746360
# raidctl -l -g 0.3.0 1
Disk Vendor Product Firmware Capacity Status HSP
----------------------------------------------------------------------------
0.3.0 FUJITSU MAV2073RCSUN72G 0301 68.3G GOOD N/A
# raidctl -S 1
1 "LSI_1064E"
# raidctl -S c1t0d0
Device not found.
# raidctl -S c1t1d0
c1t1d0 2 0.1.0 0.3.0 1 SYNC
# raidctl -S c1t2d0
Device not found.
# raidctl -S c1t3d0
Device not found.
# raidctl -S -g 0.0.0 1
0.0.0 GOOD
# raidctl -S -g 0.1.0 1
0.1.0 GOOD
# raidctl -S -g 0.2.0 1
0.2.0 GOOD
# raidctl -S -g 0.3.0 1
0.3.0 GOOD
SOLARIS COMMANDS ( after raid creation )
----------------
# ls -al /dev/cfg/c1
lrwxrwxrwx 1 root root 61 Jan 18 2011 /dev/cfg/c1 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi
# ls -al /dev/dsk/c1*s0
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t0d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0:a
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t1d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0:a
lrwxrwxrwx 1 root root 65 Jan 18 2011 /dev/dsk/c1t2d0s0 ->
../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0:a
# cfgadm -alv
Ap_Id Receptacle Occupant Condition Information When Type Busy Phys_Id
c1 connected configured unknown unavailable scsi-sata n
/devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi
c1::dsk/c1t0d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t0d0
c1::dsk/c1t1d0 connected configured unknown LSILOGIC Logical Volume unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t1d0
c1::dsk/c1t2d0 connected configured unknown FUJITSU MAV2073RCSUN72G unavailable disk
n /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi::dsk/c1t2d0
# format
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
1. c1t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> -
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
# iostat -iEn
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e01179ca30
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: LSILOGIC Product: Logical Volume Revision: 3000 Device Id:
id1,sd@n600508e00000000002597313fccb530e
Size: 73.34GB <73340551168 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 3 Predictive Failure Analysis: 0
c1t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAV2073RCSUN72G Revision: 0301 Device Id:
id1,sd@n500000e011746360
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
# prtdiag -v
System Configuration: Sun Microsystems sun4v Sun Fire T200
============================ Environmental Status ============================
LEDs:
----------------------------------------------------------------
Location LED State
----------------------------------------------------------------
CH/HDD0 SERVICE off
CH/HDD0 OK2RM off
CH/HDD1 SERVICE off
CH/HDD1 OK2RM off
CH/HDD2 SERVICE off
CH/HDD2 OK2RM off
CH/HDD3 SERVICE off
CH/HDD3 OK2RM off
# grep "/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2" /etc/path_to_inst
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2" 0 "mpt"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0" 0 "sd"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0" 1 "sd"
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0" 3 "sd"
# prtconf -vp
Node 0xf02f1fe8
firmware-version : '1.06.00.00'
mpt-version : '1.05'
model : 'LSI,1064'
version : '1.00.40'
name : 'LSILogic,sas'
revision-id : 00000002
# prtpicl -v
LSILogic,sas (scsi-2, 9b00000557)
:Label PCIX0
:revision-id 0x2
:version 1.00.40
:model LSI,1064
:mpt-version 1.05
:firmware-version 1.6.0.0
:nvdata-version-default 0
:nvdata-version-persistent 0
:num-phys 0x4
:initiator-port 500062b00000d310
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
:name LSILogic,sas
sd (block, 9b00000592)
:target-port 500000e01179ca32
:port-wwn 50 00 00 e0 11 79 ca 32
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e01179ca30
:target 0
:lun 0
:inquiry-serial-no 000545S00TDH
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
:instance 0
sd (block, a5000005b7)
:target-port 3e53cbfc13735902
:port-wwn 3e 53 cb fc 13 73 59 02
:inquiry-device-type 0
:inquiry-vendor-id LSILOGIC
:inquiry-product-id Logical Volume
:inquiry-revision-id 3000
:devid id1,sd@n600508e00000000002597313fccb530e
:target 0x1
:lun 0
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
:instance 1
sd (block, 9b000005db)
:target-port 500000e011746362
:port-wwn 50 00 00 e0 11 74 63 62
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAV2073RCSUN72G
:inquiry-revision-id 0301
:devid id1,sd@n500000e011746360
:target 0x2
:lun 0
:inquiry-serial-no 000544S00LYM
:devfs-path /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
:instance 3
disk_discovery (picl, 9b000007bc)
disk (disk, 9b000007bf)
:State configured
:Location HDD0
:Path /pci@780/pci@0/pci@9/scsi@0/sd@0,0
disk (disk, 9b000007c5)
:State configured
:Location HDD1
:Path /pci@780/pci@0/pci@9/scsi@0/sd@1,0
disk (disk, 9b000007cb)
:State configured
:Location HDD2
:Path /pci@780/pci@0/pci@9/scsi@0/sd@2,0
disk (disk, 9b000007d1)
:State unconfigured
:Location HDD3
:Path /pci@780/pci@0/pci@9/scsi@0/sd@3,0
OBP ( after raid creation )
---
ok setenv auto-boot? false
auto-boot? = false
ok setenv fcode-debug? true
fcode-debug? = true
ok reset-all
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
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e01179ca32 PhyNum 0
Target 1 Volume 0
Unit 0 Disk LSILOGICLogical Volume 3000 143243264 Blocks, 73 GB
Target 2
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011746362 PhyNum 2
ok select scsi (or select /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2)
ok .properties
firmware-version 1.06.00.00
mpt-version 1.05
model LSI,1064
version 1.00.40
name LSILogic,sas
ok show-sas-wwid
SAS World Wide ID is 500062b0 0000d310
ok show-children
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
MPT Version 1.05, Firmware Version 1.06.00.00
Target 0
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e01179ca32 PhyNum 0
Target 1 Volume 0
Unit 0 Disk LSILOGICLogical Volume 3000 143243264 Blocks, 73 GB
Target 2
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011746362 PhyNum 2
ok show-volumes
Volume 0 Target 1 Type IM (Integrated Mirroring)
Degraded Enabled Resync In Progress
2 Members 143243264 Blocks, 73 GB
Disk 1
Primary Online
Target 4 FUJITSU MAV2073RCSUN72G 0301
Disk 0
Secondary Online Out Of Sync
Target 3 FUJITSU MAV2073RCSUN72G 0301
ok unselect-dev
ok setenv fcode-debug? false
ok setenv auto-boot? true
ok reset-all
So as you now when there are NO RAID Volumes, the SAS addressing (Persistent
mapping:Enabled, Physical mapping type:Direct Attach) was as follow:
PhyNum C.ID.L HDD/DISK
0 0.0.0 0 FUJITSU MAV2073RCSUN72G 0301 500000e01179ca32
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 id1,sd@n500000e01179ca30 c1t0d0 (sd0)
1 0.1.0 1 FUJITSU MAV2073RCSUN72G 0301 500000e011622dc2
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0 id1,sd@n500000e011622dc0 c1t1d0 (sd1)
2 0.2.0 2 FUJITSU MAV2073RCSUN72G 0301 500000e011746362
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0 id1,sd@n500000e011746360 c1t2d0 (sd3)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 500000e011551c02
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0 id1,sd@n500000e011551c00 c1t3d0 (sd4)
And once the RAID Volume has been created the SAS addressing is as follow:
PhyNum C.ID.L HDD/DISK
0 0.0.0 0 FUJITSU MAV2073RCSUN72G 0301 500000e01179ca32
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 id1,sd@n500000e01179ca30 c1t0d0 (sd0)
0.1.0 LSILOGICLogical Volume 3000 3e53cbfc13735902
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
id1,sd@n600508e00000000002597313fccb530e (sd1)
? 0.4.0 ? FUJITSU MAV2073RCSUN72G 0301
? 0.3.0 ? FUJITSU MAV2073RCSUN72G 0301
2 0.2.0 2 FUJITSU MAV2073RCSUN72G 0301 500000e011746362
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0 id1,sd@n500000e011746360 c1t2d0 (sd3)
And if you keep the following events in mind:
messages
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk 0 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk 1 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 created.
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||optimal|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||optimal|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Physical disk (target 3) is
|out of sync||online|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is |enabled||degraded|
scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0): Volume 1 is
|enabled||resyncing||degraded|
The SAS addressing is as follow:
PhyNum C.ID.L HDD/DISK
0 0.0.0 0 FUJITSU MAV2073RCSUN72G 0301 500000e01179ca32
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 id1,sd@n500000e01179ca30 c1t0d0 (sd0)
0.1.0 LSILOGICLogical Volume 3000 3e53cbfc13735902
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
id1,sd@n600508e00000000002597313fccb530e (sd1)
1 0.4.0 1 FUJITSU MAV2073RCSUN72G 0301 (Physical disk 1)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 (Physical disk 0)
2 0.2.0 2 FUJITSU MAV2073RCSUN72G 0301 500000e011746362
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0 id1,sd@n500000e011746360 c1t2d0 (sd3)
Because when a Raid Volume has been created, the target of the first assigned disk
will be assigned to the Raid Volume and the target id's of the disks behind the Raid
Controller will change:
-> 0.1.0 Raid Volume
0.1.0 -> 0.4.0 HDD1 (PhyNum 1) (Physical disk 1)
0.3.0 -> 0.3.0 HDD0 (PhyNum 3) (Physical disk 0)
Lets create the same RAID Volume (RAID1, IM) of:
PhyNum C.ID.L HDD/DISK
1 0.1.0 1 FUJITSU MAV2073RCSUN72G 0301 500000e011622dc2
/pci@780/pci@0/pci@9/scsi@0/sd@1,0 id1,sd@n500000e011622dc0 c1t1d0 (sd1)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 500000e011551c02
/pci@780/pci@0/pci@9/scsi@0/sd@3,0 id1,sd@n500000e011551c00 c1t3d0 (sd3)
But this time from OBP:
ok 0 delete-volume
The volume and its data will be deleted
Are you sure (yes/no)? [no] yes
Volume 0 has been deleted
ok 1 3 create-im-volume
Target 1 size is 143243264 Blocks, 73 GB
Target 3 size is 143243264 Blocks, 73 GB
The volume can be any size from 1 MB to 69943 MB
What size do you want? [69943]
Volume size will be 143243264 Blocks, 73 GB
PhysDisk 0 has been created for target 1
PhysDisk 1 has been created for target 3
Volume has been created
ok show-children
MPT Version 1.05, Firmware Version 1.06.00.00
Target 0
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e01179ca32 PhyNum 0
Target 1 Volume 0
Unit 0 Disk LSILOGICLogical Volume 3000 143243264 Blocks, 73 GB
Target 2
Unit 0 Disk FUJITSU MAV2073RCSUN72G 0301 143374738 Blocks, 73 GB
SASAddress 500000e011746362 PhyNum 2
ok show-volumes
Volume 0 Target 1 Type IM (Integrated Mirroring)
Degraded Enabled Resync In Progress
2 Members 143243264 Blocks, 73 GB
Disk 0
Primary Online
Target 4 FUJITSU MAV2073RCSUN72G 0301
Disk 1
Secondary Online Out Of Sync
Target 3 FUJITSU MAV2073RCSUN72G 0301
the SAS addressing is as follow:
PhyNum C.ID.L HDD/DISK
0 0.0.0 0 FUJITSU MAV2073RCSUN72G 0301 500000e01179ca32
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 id1,sd@n500000e01179ca30 c1t0d0 (sd0)
0.1.0 LSILOGICLogical Volume 3000 3e53cbfc13735902
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
id1,sd@n600508e00000000002597313fccb530e (sd1)
1 0.4.0 1 FUJITSU MAV2073RCSUN72G 0301 (Physical disk 0)
3 0.3.0 3 FUJITSU MAV2073RCSUN72G 0301 (Physical disk 1)
2 0.2.0 2 FUJITSU MAV2073RCSUN72G 0301 500000e011746362
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0 id1,sd@n500000e011746360 c1t2d0 (sd3)
because when a Raid Volume has been created, the target of the first assigned disk
will be assigned to the Raid Volume and the target id's of the disks behind the Raid
Controller will change:
-> 0.1.0 Raid Volume
0.1.0 -> 0.4.0 HDD1 (PhyNum 1) (Physical disk 0)
0.3.0 -> 0.3.0 HDD0 (PhyNum 3) (Physical disk 1)
and hereby an overview (the Physical disk number is might different, but is not
important, the phy-num is important):
raidctl
-> 0.1.0 Raid Volume
0.1.0 -> 0.4.0 HDD1 (PhyNum 1) (Physical disk 1)
0.3.0 -> 0.3.0 HDD0 (PhyNum 3) (Physical disk 0)
create-im-volume
-> 0.1.0 Raid Volume
0.1.0 -> 0.4.0 HDD1 (PhyNum 1) (Physical disk 0)
0.3.0 -> 0.3.0 HDD0 (PhyNum 3) (Physical disk 1)
Because the relationship of the target/phy-num is NOT known. So as mentioned before,
there are 2x ways to determine this:
- human logic
not 100% guaranteed, needs some guesses
- using obp
100% guranteed, but requires downtime (usefull when the system is not booting)
Attachments
This solution has no attachment
