When checking status of RAID-5 volumes, you need to check both the RAID-5 state and the slice state to fully understand the state of the volume and the possibility of data loss if the volumes are not in an Okay state. See Overview of Checking Status of RAID-5 Volumes for details.
RAID-5 volume initialization or resynchronization cannot be interrupted.
From the Enhanced Storage tool within the Solaris Management Console, open the Volumes node and view the status of the volumes. Choose a volume. Then, choose Action⇒Properties to see more detailed information. For more information, see the online help.
Use the metastat command to display the status of a RAID-5 volume.
# metastat [-s diskset] [volume]
Specifies the name of the disk set on which to perform the command.
Specifies the volume to display.
For each slice in the RAID-5 volume, the metastat command shows the following:
Specifies the device name of the slice in the stripe.
Specifies the block on which the slice begins.
Specifies whether the slice contains a state database replica
Specifies the state of the slice.
Specifies whether the slice is being used to hot spare a failed slice
# metastat d10 d10: RAID State: Okay Interlace: 32 blocks Size: 10080 blocks Original device: Size: 10496 blocks Device Start Block Dbase State Hot Spare c0t0d0s1 330 No Okay c1t2d0s1 330 No Okay c2t3d0s1 330 No Okay
The metastat command output identifies the volume as a RAID-5 volume. This information is indicated by the “RAID” notation after the volume name. For each slice in the RAID-5 volume, the output shows the following:
The name of the slice in the stripe.
The block on which the slice begins.
An indicator that none of these slices contain a state database replica.
The state of the slices. In this example all slices are in the “Okay” state.
If a slice is a hot spare replacement for a failed slice.