How to use the HW Raid capability on the M3000 SPARC64 VII+ systems

Asset ID:	1-71-1332355.1
Update Date:	2017-10-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1332355.1 : How to use the HW Raid capability on the M3000 SPARC64 VII+ systems

Applies to:

Sun SPARC Enterprise M3000 Server - Version Not Applicable and later
Information in this document applies to any platform.

Goal

Hardware RAID is supported only on M3000 servers with SPARC64 VII+ processors. One way to identify the processors your server is to run the showhardconf(8) command. SPARC64 VII+ processors have a clock speed of 2.86 GHz.
Only RAID 1 is supported on M3000 servers with SPARC64 VII+ processors.

This document describes the basic operations to configure and manage hardware RAID volume using the M3000 server's on-board serial attached SCSI (SAS) controller.
It also describes the procedure for re-activating an existing RAID volume after the replacement of the MBU hosting the raid controller.

Further information can be found in the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Administration Guide - Chapter 5 - Managing Disks.

HW RAID volumes can be managed by using the Oracle Solaris OS raidctl utility.
Reminder : Solaris 10 Update 9 is the minimum Solaris version supported on M3000 servers with SPARC64 VII+ processors.

The status of the RAID volume as reported by raidctl might be:

OPTIMAL - The RAID volume is online and fully synchronized.
SYNC - The data between the primary and secondary member disks in an IM (Integrated Mirroring) volume are still synchronizing.
DEGRADED - A member disk is failed or otherwise offline.
FAILED - The RAID volume has failed and should be deleted and reinitialized. This failure can occur when both member disks in an IM volume are lost.

The Status column displays the status of each physical disk. Each member disk might be GOOD, indicating that it is online and functioning properly, or it might be FAILED, indicating that the disk has hardware or configuration issues that need to be addressed.

It's also possible to manage the volumes from OBP, using the FCode Utility Commands described below.
IMPORTANT NOTE: the OBP Level RAID commands are NOT SUPPORTED and are not intended for normal customer use. The command behavior and usage can change at any time with no notice. The only supported command is the Solaris 'raidctl' command.

FCode Command	Description
show-children	Lists all connected physical drives and logical volumes.
show-volumes	Lists all connected logical volumes in detail.
create-im-volume	Creates a RAID 1 volume (exactly two targets).
delete-volume	Deletes a RAID volume.
activate-volume	Re-activate a RAID volume.

Note that the status of the RAID volume as reported by show-volumes is similar to raidctl : Optimal / Degraded / Resync In Progress / Out of Sync / Enabled.

Solution

Creating Hardware RAID Volumes

Before creating any HW volume, it's worth checking if any HW volume already exists.

Creating a Hardware Mirrored Volume

Create the Hardware Volume from Solaris

1. Use the format command to check the disks available :

2. Use the raidctl command to check the current HW RAID configuration

# raidctl
Controller: 0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0
# raidctl -S
0 "LSI_1068E"
0.0.0 GOOD
0.1.0 GOOD
0.2.0 GOOD
0.3.0 GOOD

3. Create the Hardware Mirrored Volume via raidctl

Note : in the following example, c0t2d0 is used as the boot disk so the mirror is created on c0t0d0 and c0t1d0.

# raidctl -c c0t0d0 c0t1d0
Creating RAID volume will destroy all data on spare space of member disks, proceed (yes/no)? yes
Volume c0t0d0 is created successfully!

The following logs will appear in the console logs :

scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk 0 created.
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk 1 created.
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 created.
scsi: WARNING: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 is degraded
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk (target 1) is |out of sync||online|
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 is |enabled||degraded|

4. Check the status for the freshly created volume

# raidctl -S
0 "LSI_1068E"
c0t0d0 2 0.0.0 0.1.0 1 SYNC
0.0.0 GOOD
0.1.0 GOOD
0.2.0 GOOD
0.3.0 GOOD
# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  136.6G N/A     SYNC     OFF    RAID1
                0.0.0   136.6G          GOOD
                0.1.0   136.6G          GOOD

# format
Searching for disks...
c0t0d0: configured with capacity of 136.49GB

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
       2. c0t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@3,0

5. The Volume will be reported in the "Sync" status then the status will change to "OPTIMAL"

# raidctl -S
0 "LSI_1068E"
c0t0d0 2 0.0.0 0.1.0 1 OPTIMAL
0.0.0 GOOD
0.1.0 GOOD
0.2.0 GOOD
0.3.0 GOOD
# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  136.6G N/A     OPTIMAL OFF    RAID1
                0.0.0   136.6G          GOOD
                0.1.0   136.6G          GOOD

The console logs will then report :

scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk (target 1) is |online|
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 is |enabled||resyncing||optimal|
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 is |enabled||optimal|

Note that the sync operation may take some time to complete.
Ex with 146GB HDDs :

Jun 21 06:35:51      Volume 0 is |enabled||degraded|
Jun 21 06:35:51      Volume 0 is |enabled||resyncing||degraded|
Jun 21 07:35:54      Volume 0 is |enabled||resyncing||optimal|
Jun 21 07:35:54      Volume 0 is |enabled||optimal|

6. The volume can then be used to create a filesystem for instance.

Make sure to use "Auto configure" from the format/type menu.

# format
Searching for disks...

c0t0d0: configured with capacity of 136.49GB

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
       2. c0t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@3,0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]
Disk not labeled. Label it now? yes

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
        1. Quantum ProDrive 80S
        2. Quantum ProDrive 105S
...
        19. LSILOGIC-LogicalVolume-3000
        20. SUN146G
        21. other
Specify disk type (enter its number)[19]: 0
c0t0d0: configured with capacity of 136.49GB
<LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
selecting c0t0d0
[disk formatted]
format> disk

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
       2. c0t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@3,0
Specify disk (enter its number)[0]:

# newfs /dev/rdsk/c0t0d0s6
newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y
Warning: 816 sector(s) in last cylinder unallocated
/dev/rdsk/c0t0d0s6:     286248144 sectors in 46590 cylinders of 48 tracks, 128 sectors
        139769.6MB in 2912 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
..........................................................
super-block backups for last 10 cylinder groups at:
285281056, 285379488, 285477920, 285576352, 285674784, 285773216, 285871648,
285970080, 286068512, 286166944
# mkdir /RAID
# mount /dev/dsk/c0t0d0s6 /RAID
# df -k /RAID
Filesystem            kbytes    used   avail capacity Mounted on
/dev/dsk/c0t0d0s6    140957482 139793 139408115     1%    /RAID

Create the Hardware Volume from OBP

Note : Using the FCode utility may require to set the following variable :

{0} ok setenv fcode-debug? true

Note : It's probably a good idea to 'reset-all' before any operation at the OBP level.

1. List the device paths

{6} ok show-devs
/os-io
/ramdisk-root
[output omitted]
/pci@0,600000/pci@0/pci@2/network@0,1
/pci@0,600000/pci@0/pci@2/network@0
/pci@0,600000/pci@0/pci@1/network@0,1
/pci@0,600000/pci@0/pci@1/network@0
/pci@0,600000/pci@0/pci@0/scsi@0
/pci@0,600000/pci@0/pci@0/scsi@0/disk
/pci@0,600000/pci@0/pci@0/scsi@0/tape
[output omitted]
/packages/SUNW,probe-error-handler

2. Select the controller where you want to create a hardware RAID volume.

{0} ok select /pci@0,600000/pci@0/pci@0/scsi@0

3. List the physical drives on the selected controller.

{0} ok show-children

MPT Version 1.05, Firmware Version 1.31.00.00

Target 0
Unit 0   Disk     FUJITSU MBD2147RC       3702    286739329 Blocks, 146 GB
SASAddress 500000e1163fc8b2 PhyNum 0
Target 1
Unit 0   Disk     FUJITSU MBD2147RC       3702    286739329 Blocks, 146 GB
SASAddress 500000e1163fca22 PhyNum 1
Target 2
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a025429 PhyNum 2
Target 3
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a02209d PhyNum 3
Target 4
Unit 0   Removable Read Only device     TEAC    DV-W28S-V       J.0B
SATA device PhyNum 4

4. Check if any HW RAID configuration already exists

{0} ok show-volumes
No volumes to show

5. Create the mirrored volume via the Fcode commands

{0} ok 0 1 create-im-volume
Target 0 size is 286607360 Blocks, 146 GB
Target 1 size is 286607360 Blocks, 146 GB
The volume can be any size from 1 MB to 139945 MB
What size do you want? [139945]
Volume size will be 286607360 Blocks, 146 GB
PhysDisk 0 has been created for target 0
PhysDisk 1 has been created for target 1
Volume has been created

6. Check the configuration. Note the Resync operation

{0} ok show-volumes
Volume 0 Target 0 Type IM (Integrated Mirroring)
Degraded Enabled Resync In Progress
2 Members                                         286607360 Blocks, 146 GB
Disk 0
    Primary Online
    Target 8        FUJITSU MBD2147RC       3702
Disk 1
    Secondary Online Out Of Sync
    Target 1        FUJITSU MBD2147RC       3702

{0} ok show-children

MPT Version 1.05, Firmware Version 1.31.00.00

Target 0 Volume 0
Unit 0   Disk     LSILOGICLogical Volume 3000    286607360 Blocks, 146 GB
Target 2
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a025429 PhyNum 2
Target 3
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a02209d PhyNum 3
Target 4
Unit 0   Removable Read Only device     TEAC    DV-W28S-V       J.0B
SATA device PhyNum 4

7. Check the status from Solaris

Note : you must need to un-select the device before booting Solaris.

{0} ok unselect-dev
{0} ok boot
Boot device: /pci@0,600000/pci@0/pci@0/scsi@0/disk@2,0:a File and args:
SunOS Release 5.10 Version Generic_142909-17 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.

# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  136.6G N/A     SYNC     OFF    RAID1
                0.0.0   136.6G          GOOD
                0.1.0   136.6G          GOOD

Manage a Hardware Mirrored Volume of the Default Boot Device

raidctl blocks the creation of a hardware RAID volume if any of the member disks currently have a file system mounted.
Since the boot device always has a mounted file system when booted, an alternate boot medium must be used, and the volume created in that environment.
This means network or DVD media must be used to create the mirrored volume via raidctl.
The alternative option is to create the volume from OBP via the FCode commands as described later in this section.

Create the Mirrored Volume from Solaris

1. Boot the server from Solaris 10 Update 9 (or later) media (local DVD or network) in single user mode.
Ex :

{0} ok boot net -s

2. When running Solaris, check the status of any RAID devices.

# raidctl
Controller: 0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.2.0
Disk: 0.3.0

3. Check the disks available

4. Create a mirrored volume

# raidctl -c c0t2d0 c0t3d0
Creating RAID volume will destroy all data on spare space of member disks, proceed (yes/no)? y
Volume c0t2d0 is created successfully!

# raidctl -l c0t2d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t2d0                  136.6G N/A     SYNC     OFF    RAID1
                0.2.0   136.6G          GOOD
                0.3.0   136.6G          GOOD

5. Format and configure (format / type / label) the disk

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
       2. c0t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
Specify disk (enter its number): 2
selecting c0t2d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
...
Specify disk type (enter its number)[20]: 0
c0t2d0: configured with capacity of 136.49GB
<LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
selecting c0t2d0
[disk formatted]
format> label
Ready to label disk, continue? yes

7. Install / Re-install Solaris on this volume

Ex : from the network image

{0} ok boot net - install

Create the Mirrored Volume from OBP

1. Before dropping to OBP, check the disks available

2. Select the controller where you want to create a hardware RAID volume.

{0} ok show-devs
/pci@1,700000
...
/pci@0,600000/pci@0/pci@0/scsi@0
/pci@0,600000/pci@0/pci@0/scsi@0/disk
/pci@0,600000/pci@0/pci@0/scsi@0/tape
...
{0} ok select /pci@0,600000/pci@0/pci@0/scsi@0

3. List the physical drives on the selected controller.

4. Check if any HW RAID configuration already exists

{0} ok show-volumes
No volumes to show

5. Create the mirrored volume via the Fcode commands

{0} ok 2 3 create-im-volume
Target 2 size is 286607360 Blocks, 146 GB
Target 3 size is 286607360 Blocks, 146 GB
The volume can be any size from 1 MB to 139945 MB
What size do you want? [139945]
Volume size will be 286607360 Blocks, 146 GB
PhysDisk 0 has been created for target 2
PhysDisk 1 has been created for target 3
Volume has been created

6. Confirm that the freshly created volume is created as expected

{0} ok show-volumes
Volume 0 Target 2 Type IM (Integrated Mirroring)
Degraded Enabled Resync In Progress
2 Members                                         286607360 Blocks, 146 GB
Disk 1
    Primary Online
    Target 8        HITACHI H103014SCSUN146GA160
Disk 0
    Secondary Online Out Of Sync
    Target 3        HITACHI H103014SCSUN146GA160

Note : the Volume status is "Resync In Progress". No need to wait for the sync to complete before proceeding with the Solaris installation.

7. Install / Re-install Solaris on this volume

Ex : from the network image

{0} ok boot net - install

8. When the domain is installed, from Solaris, the configuration is :

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
       2. c0t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0

Specify disk (enter its number): ^D
# raidctl
Controller: 0
        Volume:c0t2d0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0
# raidctl -l c0t2d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t2d0                  136.6G N/A     SYNC     OFF    RAID1
                0.2.0   136.6G          GOOD
                0.3.0   136.6G          GOOD
# df -k
Filesystem            kbytes    used   avail capacity Mounted on
/dev/dsk/c0t2d0s0    136825259 4434702 131022305     4%    /

Note : the Sync operation may take some time to complete.
Ex with S10U9 installed on 146GB disks

Jun 21 10:12:50 Volume 2 is resyncing
Jun 21 11:16:54 Volume 2 is |enabled||resyncing||optimal|
Jun 21 11:16:54 Volume 2 is |enabled||optimal|

Delete a Hardware Mirrored Volume used for Default Boot Device

From OBP, using the Fcode commands, it's possible to remove the boot device from the HW Raid control.
Note : to delete the volume using the raidctl command, boot the server from Solaris 10 Update 9 (or later) media (local DVD or network) in single user mode.

1. On a domain using c0t2d0 as the boot device

# df -k
Filesystem            kbytes    used   avail capacity Mounted on
/dev/dsk/c0t2d0s0    136825259 4434702 131022305     4%    /
# raidctl -l
Controller: 0
        Volume:c0t2d0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0
# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
       2. c0t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0

2. From the OBP, select the controller, check the physical drives and volumes available

{0} ok select /pci@0,600000/pci@0/pci@0/scsi@0
{0} ok show-volumes
Volume 0 Target 2 Type IM (Integrated Mirroring)
Optimal Enabled
2 Members                                         286607360 Blocks, 146 GB
Disk 1
    Primary Online
    Target 8        HITACHI H103014SCSUN146GA160
Disk 0
    Secondary Online
    Target 3        HITACHI H103014SCSUN146GA160

3. Delete the existing volume used for the boot device

{0} ok 0 delete-volume
The volume and its data will be deleted
Are you sure (yes/no)? [no] yes
Volume 0 has been deleted
{0} ok show-volumes
No volumes to show

4. Using the same alias, it's possible to boot on the disks used for the Volume

{0} ok unselect-dev
{0} ok boot /pci@0,600000/pci@0/pci@0/scsi@0/disk@2,0:
Boot device: /pci@0,600000/pci@0/pci@0/scsi@0/disk@2,0: File and args:
SunOS Release 5.10 Version Generic_142909-17 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.

# raidctl -l
Controller: 0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0
# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
       2. c0t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
       3. c0t3d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@3,0

Deleting a Hardware RAID Volume

Delete the Hardware Volume from Solaris

1. Check the current configuration and status

# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  136.6G N/A     OPTIMAL OFF    RAID1
                0.0.0   136.6G          GOOD
                0.1.0   136.6G          GOOD

2. Any activity on the volume must be stopped in order to delete the volume

# raidctl -d c0t0d0
Deleting RAID volume c0t0d0 will destroy all data it contains, proceed (yes/no)? yes
Array or disk in use.
# umount /RAID

3. As soon as there is no more activity on the Volume, it can be deleted

bash-3.00# raidctl -d c0t0d0
Deleting RAID volume c0t0d0 will destroy all data it contains, proceed (yes/no)? yes
Volume c0t0d0 is deleted successfully!

With the following console logs :

scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Volume 0 deleted.
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk 0 deleted.
scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
      Physical disk 1 deleted.

4. Check the resulting configuration

# raidctl
Controller: 0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0

5. The disks should be formatted again to return to their original configuration, prior to being member of the HW Volume

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
    ...
   Specify disk type (enter its number)[19]: 0
c0t0d0: configured with capacity of 136.71GB
<FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
selecting c0t0d0
[disk formatted]
format> disk

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
Specify disk (enter its number)[0]: 1
selecting c0t1d0
[disk formatted]
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
    ...
Specify disk type (enter its number)[19]: 0
c0t1d0: configured with capacity of 136.71GB
<FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
selecting c0t1d0
[disk formatted]
format> disk

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t1d0 <FUJITSU-MBD2147RC-3702 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0

Delete the Hardware Volume from OBP

1. List the device paths

2. Select the controller where you want to create a hardware RAID volume.

{0} ok select /pci@0,600000/pci@0/pci@0/scsi@0

3. Check the existing HW RAID configuration

{0} ok show-volumes
Volume 0 Target 0 Type IS (Integrated Striping)
Optimal Enabled
2 Members                                         573214720 Blocks, 293 GB
Disk 1
    Member 0 Online
    Target 8        FUJITSU MBD2147RC       3702
Disk 0
    Member 1 Online
    Target 1        FUJITSU MBD2147RC       3702

4. Delete the existing Volume

{0} ok 0 delete-volume
The volume and its data will be deleted
Are you sure (yes/no)? [no] yes
Volume 0 has been deleted

5. Check that the volume does no longer exist

{0} ok show-volumes
No volumes to show
{0} ok show-children

MPT Version 1.05, Firmware Version 1.31.00.00

Target 0
Unit 0   Disk     FUJITSU MBD2147RC       3702    286739329 Blocks, 146 GB
SASAddress 500000e1163fc8b2 PhyNum 0
Target 1
Unit 0   Disk     FUJITSU MBD2147RC       3702    286739329 Blocks, 146 GB
SASAddress 500000e1163fca22 PhyNum 1
Target 2
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a025429 PhyNum 2
Target 3
Unit 0   Disk     HITACHI H103014SCSUN146GA160    286739329 Blocks, 146 GB
SASAddress 5000cca00a02209d PhyNum 3
Target 4
Unit 0   Removable Read Only device     TEAC    DV-W28S-V       J.0B
SATA device PhyNum 4

Note : From Solaris, make sure to re-configure the disk (format / type).

Activate a Hardware RAID Volume after the MBU replacement

The MBU is hosting the RAID controller so when it's replaced, it's no longer possible to boot off any existing RAID volume until the volume is re-activated from OBP via the OBP command 'activate-volume'.

After the MBU has been replaced, the disks/volumes are no longer listed

{0} ok probe-scsi-all
/pci@0,600000/pci@0/pci@0/scsi@0

MPT Version 1.05, Firmware Version 1.31.00.00

Target 4
Unit 0 Removable Read Only device TEAC DV-W28S-V J.0B
SATA device PhyNum 4

{0} ok show-volumes
show-volumes ?

After selecting the device, the volume is reported but it's inactive

{0} ok show-devs
/pci@1,700000
...
/pci@0,600000/pci@0/pci@0/scsi@0/disk
...
{0} ok select /pci@0,600000/pci@0/pci@0/scsi@0

{0} ok show-volumes
Volume 0 Target 82 Type IM (Integrated Mirroring)
Optimal Enabled Inactive
2 Members                                         585805824 Blocks, 299 GB
Disk 1
    Primary Online
    Target 0        FUJITSU MBD2300RC       3702
Disk 0
    Secondary Online
    Target 1        FUJITSU MBD2300RC       3702

Use the 'activate-volume' command to activate the existing volume.

{0} ok 0 activate-volume
Volume 0 is now activated

{0} ok show-volumes
Volume 0 Target 0 Type IM (Integrated Mirroring)
Degraded Enabled Resync In Progress
2 Members                                         585805824 Blocks, 299 GB
Disk 1
    Primary Online
    Target 8        FUJITSU MBD2300RC       3702
Disk 0
    Secondary Online Out Of Sync
    Target 1        FUJITSU MBD2300RC       3702

Note : When dealing with multiple volumes, make sure they are activated in descending order.

{0} ok 1 activate-volume
Volume 1 is now activated
{0} ok 0 activate-volume
Volume 0 is now activated

It's now possible to boot off the volume.
Activating the volume causes to mirror to resync.

{0} ok unselect-dev
{0} ok probe-scsi-all
/pci@0,600000/pci@0/pci@0/scsi@0

MPT Version 1.05, Firmware Version 1.31.00.00

Target 0 Volume 0
Unit 0   Disk     LSILOGICLogical Volume 3000    585805824 Blocks, 299 GB
Target 4
Unit 0   Removable Read Only device     TEAC    DV-W28S-V       J.0B
SATA device PhyNum 4

{0} ok boot
Boot device: disk:a File and args:
SunOS Release 5.10 Version Generic_142909-17 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.

# raidctl -S
0 "LSI_1068E"
c0t0d0 2 0.0.0 0.1.0 1 SYNC
0.0.0 GOOD
0.1.0 GOOD

# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  279.3G N/A     SYNC     OFF    RAID1
                0.0.0   279.3G          GOOD
                0.1.0   279.3G          GOOD

Aug 18 21:07:02 m3000 scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
Aug 18 21:07:02 m3000 Physical disk (target 1) is |online|
Aug 18 21:07:02 m3000 scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
Aug 18 21:07:02 m3000 Volume 0 is |enabled||resyncing||optimal|
Aug 18 21:07:02 m3000 scsi: /pci@0,600000/pci@0/pci@0/scsi@0 (mpt0):
Aug 18 21:07:02 m3000 Volume 0 is |enabled||optimal|

bash-3.00# raidctl -l c0t0d0
Volume                  Size    Stripe Status   Cache RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t0d0                  279.3G N/A     OPTIMAL OFF    RAID1
                0.0.0   279.3G          GOOD
                0.1.0   279.3G          GOOD

Attachments

This solution has no attachment