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.
For each slice in the RAID 5 volume, the metastat command shows the following:
“Device” (device name of the slice in the stripe)
“Start Block” on which the slice begins
“Dbase” to show if the slice contains a state database replica
“State” of the slice
“Hot Spare” to show the slice being used to hot spare a failed slice
# metastat 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. For each slice in the RAID 5 volume, it shows 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, that all the slices are okay, and that none of the slices are hot spare replacements for a failed slice.