That’s it, the vdisk that had the failed drive will 'claim' the spare and rebuild, this may take a little time. After this process is finished, the vdisk will carry out a 'Media Scub' job.
Clear Disk Metadata
The 'new' drive was marked as LEFTOVR and was flagged with the following warning:
The disk may contain stale metadata. Recommended action: Clear the metadata to rescue the disk.
You see this error because this is a 'recycled' disk, and it still has data on it that refers to the array and/or vdisk that it was in originally. This is the 'metadata' that it is referring to.
Note: From the image above, the disk will be dealing with is disk 8 (make a mental note of that).
With the MSA Selected > Tools > Clear Disk Metadata.
Remember our disk is in in slot 8, so tick it and click clear metadata.
You can now treat this disk as if it were a new disk and add it as a global spare, the failed vdisk will then claim the disk and the RAID should rebuild it without further intervention.
The Virtaul Disk State is QTOF
机房断电设备重启后,硬盘状态正常,多个 VD 变成 QTOF 状态如下:
# show vd Name Size Free Own Pref RAID Disks Spr Chk Status Jobs Serial Number ------------------------------------------------------------------------ vd01 3996.7GB 751.5MB A A RAID5 5 0 64k QTOF 00c0ff10386b0000b519384c00000000 vd02 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000dd19384c00000000 vd03 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL 00c0ff10386b0000f919384c00000000 vd04 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b100002d1a384c00000000 vd05 3996.7GB 751.5MB A A RAID5 5 0 64k QTOF 00c0ff10386b0000c19f554e00000000 vd06 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000ce9f554e00000000 vd07 3996.7GB 751.5MB A A RAID5 5 0 64k QTOF 00c0ff10386b0000da9f554e00000000 vd08 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000fc9f554e00000000 ------------------------------------------------------------------------
# show vd Name Size Free Own Pref RAID Disks Spr Chk Status Jobs Serial Number ------------------------------------------------------------------------ vd01 3996.7GB 751.5MB A A RAID5 5 0 64k OFFL 00c0ff10386b0000b519384c00000000 vd02 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000dd19384c00000000 vd03 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL 00c0ff10386b0000f919384c00000000 vd04 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b100002d1a384c00000000 vd05 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL VRSC 56% 00c0ff10386b0000c19f554e00000000 vd06 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000ce9f554e00000000 vd07 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL VRSC 59% 00c0ff10386b0000da9f554e00000000 vd08 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000fc9f554e00000000 ------------------------------------------------------------------------
# trust vdisk vd01 # show vd Name Size Free Own Pref RAID Disks Spr Chk Status Jobs Serial Number ------------------------------------------------------------------------ vd01 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL 00c0ff10386b0000b519384c00000000 vd02 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000dd19384c00000000 vd03 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL 00c0ff10386b0000f919384c00000000 vd04 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b100002d1a384c00000000 vd05 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL VRSC 56% 00c0ff10386b0000c19f554e00000000 vd06 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000ce9f554e00000000 vd07 3996.7GB 751.5MB A A RAID5 5 0 64k FTOL VRSC 59% 00c0ff10386b0000da9f554e00000000 vd08 3996.7GB 751.5MB B B RAID5 5 0 64k FTOL 00c0ff1035b10000fc9f554e00000000 ------------------------------------------------------------------------