This post is more than 5 years old
1 Rookie
•
12 Posts
0
10083
August 4th, 2016 03:00
Data Domain DD880 - Disk showing "Available" ( V ) instead of "Spare" ( S ) after faulty disk replacement
Hi all,
I hope someone can help on that issue.
After a failed disk replacement the new disk comes as Available state instead of Spare state.
Here is an output of the Disk Show State command:
Enclosure Disk
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
--------- ------------------------------------------------
1 s . . .
2 . . . . . . . . s . . . . . s .
3 . . . . . . . . . . . . . . s s
4 . . . . . . . . . . . . . . s s
5 . . . . . . . . . . . . . . s
6 . . . . . . . . . s . . . . . s
7 . . v . . . . . . . . . . . s .
8 . . . . . . . . . . . . . . s s
9 . . . . . . . s . . . . . . .
10 . . . . . . . . . . . . . . s
11 . . . . . . . . . . . . . . s s
12 . . . . . . s . . . . . . . .
13 . . . s . . . . . . . . . . s .
--------- ------------------------------------------------
Legend State Count
------ --------------- -----
. In Use Disks 171
s Spare Disks 20
v Available Disks 1
Total 192 disks
Thanks for your time.
richbinstead
62 Posts
0
August 5th, 2016 05:00
Hi Bobby.P,
When you replace a failed disk and the new disk is inserted, the DataDomain system will:
- Examine the newly inserted disk for any partitions that exist.
- If there are no partitions on the disk, then a number of partitions will be created. In one partition, specifically partition 3, will we create a DataDomain superblock. This disk will then become a spare disk as indicated by the 's' state above.
- If partition 3 exists, it is checked for the presence of a superblock. If a superblock exists and the superblock shows the information from another system, the disk will become a foreign or unknown.
- If partition 3 exists but there is no superblock, the disk will become a 'v' available disk.
So the disk you inserted seems to have had partition 3 already created.
The other disk you inserted that immediately became a spare indicates it had no partitions installed upon it.
Therefore as srishenoy mentioned, a disk fail followed by a disk unfail should resolve the 'v' issue and force DataDomain to recreate the partitions and superblock information.
I hope this helps explain why.
cheers, Rich.
Bobby Petrov
1 Rookie
•
12 Posts
0
August 4th, 2016 07:00
Hi Srishenoy,
We did not perform that command.
However we noticed that the faulty drive was with part number 0955287-02 and the replacement drive we used was p/n: 0955287-01.
Could that be the reason the system did not recognized it as a Spare, and would the fail -> unfail command sort it out.
P.S. Worth mentioning is that we now have replaced it with the identical part number (0955287-02) and the disk came up as Spare disk.
Bobby Petrov
1 Rookie
•
12 Posts
0
August 5th, 2016 05:00
Hi Rich,
Will give it a try on the next failed drive and will update you how it went.
Cheers,
Bobby