Recently our HP MSA suffered a VDisk Failure, reporting the following messages:
Virtual-disk is not fault tolerant.
Event 55: A disk drive reported a SMART event
Event 314: There is a problem with a FRU.
There did not seem to be much information online as to how to resolve the issue. The Physical Hard Disk Drive had not failed, but the vdisk array was in a degraded state.
The first thing that needs to be done, is the meta-data on the leftover disk needs to be cleared before it can re-join the RAID as either a disk or a dedicated spare.
Clearing Disk Meta Data
Each disk has metadata that identifies whether the disk is a member of a vdisk, and identifies other members of that vdisk. If a disk’s metadata says the disk is a member of a vdisk but other members’ metadata say the disk isn’t a member, the disk becomes a leftover. The system overview and enclosure overview pages show the disk’s How Used value as LEFTOVR. A leftover disk’s Fault/UID LED is illuminated amber.
Before you can use the disk in a new vdisk or as a spare, you must clear the disk’s metadata.
To Clear meta data from leftover disks
- In the Configuration View panel, right-click the system and then select Tools > Clear Disk Metadata.
- In the main panel, select disks to clear metadata from.
- Click Clear Metadata. When processing is complete a success dialog appears.
Re-Join Physical Disk to VDisk RAID
- In the HP MSA Storage Managment Utility, rRight click on the affected vdisk and select Configuration > Manage Dedicated Spares
- Your disk should appear in the list of available drives with a state of AVAIL. Tick the drive, then click the Modify Spares button.
- The disk will be re-joined to the array. Initially it may be listed as a spare, but the MSA will automatically re-join the disk as an active member of the RAID if this is how it was originally configured.
- The array will begin the Reconstruction process automatically. This can take a very long time depending on the size of your drives.