How to configure the server to boot from an already created volume

Asset ID:	1-71-1624053.1
Update Date:	2017-07-12
Keywords:

Solution Type Technical Instruction Sure

Solution 1624053.1 : How to configure the server to boot from an already created volume

Applies to:

SPARC T4-1B - Version All Versions to All Versions [Release All Releases]
Netra SPARC T4-1B - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)

Goal

Configure a server to boot from a previously created internal boot volume under a LSI controller

Solution

After creating a boot volume, identify its path, target and device name:

{0} ok probe-scsi-all

...

/pci@400/pci@1/pci@0/pci@c/LSI,sas@0

FCode Version 1.00.60, MPT Version 2.00, Firmware Version 11.05.02.00

Target 376 Volume 0  <<<---
  Unit 0   Disk   LSI      Logical Volume   3000    583983104 Blocks, 298 GB
  VolumeDeviceName 3e518ec87daeab64  VolumeWWID 0e518ec87daeab64

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

...

Path = /pci@400/pci@1/pci@0/pci@c/LSI,sas@0

Target = 376

VolumeDeviceName = 3e518ec87daeab64

Create an alias with the name of your preference pointing to the path plus a reference "/disk@" followed by the volume target.

In this example:

-> Path /pci@400/pci@1/pci@0/pci@c/LSI,sas@0 + /disk@ + Target 376

{0} ok show-disks
a) /pci@400/pci@2/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0,1/fp@0,0/disk
b) /pci@400/pci@2/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0/fp@0,0/disk
c) /pci@400/pci@1/pci@0/pci@c/LSI,sas@0/disk                     <<<--- 
d) /pci@400/pci@1/pci@0/pci@0/pci@0/usb@0,2/hub@3/storage@2/disk
e) /iscsi-hba/disk
q) NO SELECTION
Enter Selection, q to quit: c
/pci@400/pci@1/pci@0/pci@c/LSI,sas@0/disk has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
         for creating devalias mydev for /pci@400/pci@1/pci@0/pci@c/LSI,sas@0/disk

{0} ok devalias bootvol /pci@400/pci@@1/pci@0/pci@c/LSI,sas@0/disk@376
{0} ok setenv boot-device bootvol
{0} ok reset-all
    OR
[0] ok boot bootvol

Now you can proceed to boot from that volume:

{0} ok boot bootvol
NOTICE: Entering OpenBoot.
... POST ...
SPARC T4-1B, No Keyboard
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.35.3, 255.5000 GB memory available, Serial #10298152.
Ethernet address 0:10:e0:43:5f:za, Host ID: 86243fza.

Boot device: /pci@400/pci@1/pci@0/pci@c/LSI,sas@0/disk@376  File and args:
ufs-file-system
Loading: /platform/sun4v/boot_archive
...

After boot you can verify at Solaris level, the relationship between 'format' and 'prtconf' outputs with the volume device name already seen on 'probe-scsi-all'

# prtconf -vp |grep bootpath

bootpath: '/pci@400/pci@1/pci@0/pci@c/LSI,sas@0/disk@w3e518ec87daeab64,0:a'

# format

AVAILABLE DISK SELECTIONS:
       0. c1t3E518EC87DAEAB64d0 <LSI-LogicalVolume-3000 cyl 65533 alt 2 hd 64 sec 139> sblade02
          /pci@400/pci@1/pci@0/pci@c/LSI,sas@0/iport@v0/disk@w3e518ec87daeab64,0
       ...

References

<NOTE:1387817.1> - Hardware RAID on the T3 & T4 Servers
<NOTE:1010006.1> - How to create an OBP boot device alias

Attachments

This solution has no attachment