Creating the boot path on SPARC T3 - T8 Servers for internal disks

Asset ID:	1-79-1506246.1
Update Date:	2018-03-28
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1506246.1 : Creating the boot path on SPARC T3 - T8 Servers for internal disks

Applies to:

SPARC T3-1 - Version All Versions and later
SPARC T4-4 - Version All Versions and later
Netra SPARC T4-1 Server - Version All Versions and later
SPARC T3-2 - Version All Versions and later
SPARC T4-1 - Version All Versions and later
Information in this document applies to any platform.

Purpose

How to determine and create the proper boot path for the internal raid controller

Scope

This is intended for the system admin or anyone administering SPARC T3-x, SPARC T4-x, SPARC T5-x, SPARC T7-x, and SPARC T8-x Server internal disk assemblies.

There are examples on how to determine the correct device to place in the path, and what the path should look like.

Details

Boot Paths for internal disks, using HW Raid or not.

The following is based that the drives have been configured with a raid volume or not.

The steps below will show how to accomplish setting the correct boot path on the system.

Step1

Halt the system, get to the system console ( ok> prompt )

Perform the following: ok> probe-scsi-all (use this output for your information)

Note: The paths used in this example may not represent the path for your system

{0} ok probe-scsi-all
/pci@400/pci@2/pci@0/pci@e/scsi@0

FCode Version 1.00.60, MPT Version 2.00, Firmware Version 9.00.00.00

Target 9
   Unit 0   Disk   SEAGATE ST960005SSUN600G 0606    1172123568 Blocks, 600 GB
   SASDeviceName 5000c500437b4c8b SASAddress 5000c500437b4c89 PhyNum 0
                                                            |
                                                            \<-used for non hw raid boot path
Target a
   Unit 0   Removable Read Only device   TEAC    DV-W28SS-R      1.0C
   SATA device PhyNum 7
Target b
   Unit 0   Disk   SEAGATE ST960005SSUN600G 0606    1172123568 Blocks, 600 GB
   SASDeviceName 5000c500437e934b SASAddress 5000c500437e9349 PhyNum 1
Target 381 Volume 0
   Unit 0   Disk   LSI      Logical Volume   3000    1169920000 Blocks, 598 GB
   VolumeDeviceName 3191d94818ab05da VolumeWWID 0191d94818ab05da
               |
               \<-used for hw raid boot path

/pci@400/pci@1/pci@0/pci@b/pci@0/usb@0,2/hub@2/hub@3/storage@2
   Unit 0   Removable Read Only device    AMI     Virtual CDROM   1.00

{0} ok

Example of how the path looks under software control ( ie: format )

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
        0. c0t5000C500437B4C8Bd0 cyl 64986 alt 2 hd 27 sec 668> solaris
           /scsi_vhci/disk@g5000c500437b4c8b
        1. c0t5000C500437E934Bd0 cyl 64986 alt 2 hd 27 sec 668> solaris
           /scsi_vhci/disk@g5000c500437e934b
        2. c3t3191D94818AB05DAd0 cyl 65533 alt 2 hd 32 sec 557>
           /pci@400/pci@2/pci@0/pci@e/scsi@0/iport@v0/disk@w3191d94818ab05da,0

How to boot an internal HW Raid volume

To boot the hw raid internal volume use the following path:

{0} ok boot /pci@400/pci@2/pci@0/pci@e/scsi@0/disk@w3191d94818ab05da,0:a

Note that the path is derived from the controller path output from probe-scsi-all.
Some systems have two controllers. You must use the controller path the volume is under.
In this example it is...../pci@400/pci@2/pci@0/pci@e/scsi@0 And to that added disk@w...and the VolumeDeviceName, followed by ...... ,0:a

{0} ok boot /pci@400/pci@2/pci@0/pci@e/scsi@0/disk@w3191d94818ab05da,0:a

How to boot an internal disk that is not part a HW Raid volume

To boot the non hw raided internal disk in slot 0(indicated by PhyNum 0 from probe-scsi-all) use the following path:

{0} ok boot /pci@400/pci@2/pci@0/pci@e/scsi@0/disk@w5000c500437b4c89,0:a

Note that the path is derived from the controller path output from probe-scsi-all.
Some systems have two controllers. You must use the controller path the disk is under.
In this example it is...../pci@400/pci@2/pci@0/pci@e/scsi@0 And to that added disk@w...and the SASAddress, followed by ...... ,0:a

Reference: Hardware RAID on the T3 & T4 Servers

References

<NOTE:1010006.1> - How to create an OBP boot device alias

Attachments

This solution has no attachment