NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Disk shows Dead. Volume shows fine.
I have X-Raid with dual redundancy configured. A disk failed on me and I went to pull out the bad drive. Stupid me for not checking, but I pulled out disk 6 when disk 4 was the dead drive. I was n...
There's no important data on the swap partition. That's just used for temporarily storing what's normally stored in RAM if the RAM doesn't have sufficient space.
So you can safely do what the error message suggested:
# mdadm --zero-superblock /dev/sdf2
then
# mdadm --manage /dev/md1 --add /dev/sdf2
If sdf2 is marked as a spare in md1 (you can tell this by checking the output of # cat /proc /mdstat ) you can force it to be used properly by doing e.g.
# mdadm --grow /dev/md1 -n6
Thanks mdgm-ntgr. The partion table of /dev/sdf looks just like the other disks.
tesla6:~# sgdisk -p /dev/sdf Disk /dev/sdf: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 2DC189AC-6A83-46DC-97FA-1640ED4DD832 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 8-sector boundaries Total free space is 4141 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 5 9437256 3907024064 1.8 TiB FD00 6 3907024072 5860529038 931.5 GiB FD00
Here is disk e just as an example, but they all look like this.
tesla6:~# sgdisk -p /dev/sde Disk /dev/sde: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 33F0A993-B387-4386-9D6A-E00107FF4CE7 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 8-sector boundaries Total free space is 4141 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 5 9437256 3907024064 1.8 TiB FD00 6 3907024072 5860529038 931.5 GiB FD00
However, I get an error while attempting to add the missing disk into the swap array.
Any ideas?
tesla6:~# mdadm --manage /dev/md1 --add /dev/sdf2 mdadm: /dev/sdf2 reports being an active member for /dev/md1, but a --re-add fails. mdadm: not performing --add as that would convert /dev/sdf2 in to a spare. mdadm: To make this a spare, use "mdadm --zero-superblock /dev/sdf2" first.
There's no important data on the swap partition. That's just used for temporarily storing what's normally stored in RAM if the RAM doesn't have sufficient space.
So you can safely do what the error message suggested:
# mdadm --zero-superblock /dev/sdf2
then
# mdadm --manage /dev/md1 --add /dev/sdf2
If sdf2 is marked as a spare in md1 (you can tell this by checking the output of # cat /proc /mdstat ) you can force it to be used properly by doing e.g.
# mdadm --grow /dev/md1 -n6
That did it!
Once I zeroed it out I was able to add it to md1. It took mabye 15 seconds to recover (by watching "cat /proc/mdsat") and then everything looked good in mdstat. Once I logged into FrontView it showed the volume and all disks were healthy.
Thanks for the help and thanks for the lesson. I hope this helps someone else in the future.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
