Oracle T5-2 server: how to make hardware raid

Make an hardware RAID on T5-2 server is very fun 🙂
The first important thing is to locate which disk must be used for the raid.
If you have more than two disks on the server you have the question: “which disk I’m selecting for the raid?”

It’s simple to answer this question. Just following the official ORACLE documentation:

0) Go to OK prompt
1) Get the physical devices list

ok show-devs



2) Select a controller

ok select /pci@300/pci@1/pci@0/pci@4/scsi@0

3)Go in front of the server and you will see the disks blinking!!! So it’s easy to identify which disks we are using.
4) Get the targets

{0} ok show-children

FCode Version 1.00.63, MPT Version 2.00, Firmware Version

Target 9
Unit 0 Disk HITACHI H109030SESUN300G A690 585937500 Blocks, 300 GB
SASDeviceName 5000cca0546f7da4 SASAddress 5000cca0546f7da5 PhyNum 0
Target a
Unit 0 Removable Read Only device TEAC DV-W28S-A 9.2A
SATA device PhyNum 3
Target b
Unit 0 Disk HITACHI H109030SESUN300G A690 585937500 Blocks, 300 GB
SASDeviceName 5000cca0546f5d48 SASAddress 5000cca0546f5d49 PhyNum 1

5) Make the raid ( in my case I maid raid-1 ) between the targets

{0} ok 9 b create-raid1-volume
Target 9 size is 583983104 Blocks, 298 GB
Target b size is 583983104 Blocks, 298 GB
The volume can be any size from 1 MB to 285148 MB
What size do you want? [285148]
Volume size will be 583983104 Blocks, 298 GB
Enter a volume name: [0 to 15 characters] boot
Volume has been created

6) Check the volume info

{0} ok show-volumes
Volume 0 Target 143 Type RAID1 (Mirroring)
Name boot WWID 00de54d908dba3cb
Optimal Enabled Background Init In Progress
2 Members 583983104 Blocks, 298 GB
Disk 0
Primary Optimal
Target 9 HITACHI H109030SESUN300G A690 PhyNum 0
Disk 1
Secondary Optimal
Target b HITACHI H109030SESUN300G A690 PhyNum 1

7) Unselect the controller ( disks are still blinking! )

unselect-dev /pci@300/pci@1/pci@0/pci@4/scsi@0

At this point you can boot the server and watch the device via format command.
For the maintenance you can manage the volumes directly from Solaris! This is due to sas2ircu utility.