Unsolved
1 Message
0
1561
May 18th, 2020 23:00
Removed disk, hot spare ready disk took over. What happens then?
Hey All,
I hope you can help me with this query:
In our VNX5300, we had a faulty disk: bus 1 enc 0 disk 2.
The hot spare ready disk bus 1 enc 2 disk 13 is now replacing bus 1 enc 0 disk 2.
My question is the following:
Suppose the faulty disk slot bus 1 enc 0 disk 2 (which is now empty, the faulty HDD was removed), is replaced with a new hard disk.
After launching the replace a faulty disk wizard on USM, bus 1 enc 0 disk 2 status becomes unbound, instead of removed (current status).
What happens to bus 1 enc 2 disk 13? Shouldn't it automatically revert back to the hot spare ready state?
If not, should I copy the content of bus 1 enc 2 disk 13 to the unbound bus 1 enc 0 disk 2.
The one pool on the VNX appliance, pool 0, whose disks are mounted in raid 5, contains bus 1 enc 0 disk 2 as a member of this raid. But bus 1 enc 2 disk 13 is not listed in the disks members of the raid 5 of pool 0.
DELL-Sam L
Moderator
•
7.6K Posts
0
May 19th, 2020 14:00
Hello MahaAJ,
Your hot spare drive is now part of your raid5 lun. The replacement drive that went into bus 1 enclosure 0 disk 2 will show as unbound is correct. Here is a video that shows what USM will show after a drive replacement. https://dell.to/2TmPKEz
Please let us know if you have any other questions.
SteveK821
1 Rookie
•
30 Posts
0
May 20th, 2020 06:00
Actually I'm not sure that is correct for the VNX1 Series (e.g. 5300, 5500). The VNX1 Series had defined hot-spare disks, so when you replace the defective disk, the VNX will copy data back from the spare to the new disk. Then the spare returns to being a spare again, waiting for the next disk to fail.
VNX2 (e.g. 5400, 5600) do indeed spare as you have described. There are no defined spare disks, any unbound disk is treated as a spare. When a disk fails, VNX will take an appropriate unbound disk, reconstruct the data on it. Once the failed disk is replaced the new disk becomes Unbound and does nothing.