NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rsilva1
Nov 11, 2012Aspirant
ReadyNAS NVX problems replacing disk
Hi,
Yesterday I received a notification that one of the disks in my ReadyNAS NVX was dead and required replacement.
I had a spare disk of the same kind (it is the 3TB Hitachi that is listed in the HCL), so I performed a replacement (with the unit on).
I got two more notifications. First "Disk removal detected. [Disk 3]" and then "Data volume will be rebuilt with disk 3".
After this, nothing happens. The volume is not being rebuilt and both Frontview and RAIDar report disk 3 as dead. I left if for some time after reading that it sometimes needs a few minutes to start the rebuild, but nothing happened.
I had also read that sometimes rebooting the unit is necessary, which I did, but still the unit is marked as dead and rebuild does not start (I still get the "Data volume will be rebuilt with disk 3" message).
The disk that was reported dead actually seems to be just fine. I tried it on my PC, created new file systems and everything works fine. A long smart test did not reveal any issues either.
I then tried to re-insert the original disk (after removing all partitions) and same thing happens. I get the notifications that the disk was removed and that a the data volume will be rebuilt.
Left it overnight, but nothing happened. It did not rebuild.
The data on the unit is still accessible, so that is not the problem, but I have no redundancy.
I tried many other things:
It basically reports no partitions
- dmesg reports
- I even tried putting in another disk, that I know works fine, but with a smaller capacity (1TB). It was detected by the system, I got a notification that the disk was too small for the current volume, but Frontview still reported the disk as dead, but with the old capacity and model number.
I have had the unit for about 2 years and have performed expansion from 1TB to 2TB and later 3TB for each of the 4 drives. Never had any issues and I also replaced 2 failed disks during this time and that also worked fine.
Any clues on what might be the problem?
Is there a way to force the unit to mark the disk as not present/missing?
Thanks.
Yesterday I received a notification that one of the disks in my ReadyNAS NVX was dead and required replacement.
I had a spare disk of the same kind (it is the 3TB Hitachi that is listed in the HCL), so I performed a replacement (with the unit on).
I got two more notifications. First "Disk removal detected. [Disk 3]" and then "Data volume will be rebuilt with disk 3".
After this, nothing happens. The volume is not being rebuilt and both Frontview and RAIDar report disk 3 as dead. I left if for some time after reading that it sometimes needs a few minutes to start the rebuild, but nothing happened.
I had also read that sometimes rebooting the unit is necessary, which I did, but still the unit is marked as dead and rebuild does not start (I still get the "Data volume will be rebuilt with disk 3" message).
The disk that was reported dead actually seems to be just fine. I tried it on my PC, created new file systems and everything works fine. A long smart test did not reveal any issues either.
I then tried to re-insert the original disk (after removing all partitions) and same thing happens. I get the notifications that the disk was removed and that a the data volume will be rebuilt.
Left it overnight, but nothing happened. It did not rebuild.
The data on the unit is still accessible, so that is not the problem, but I have no redundancy.
I tried many other things:
- - Removed disk 3, restarted the unit. Frontview reports disk 3 as dead (with the capacity and model number), when it should be “missing” or “not installed”
- Inserted replacement disk. Shut down unit, powered it on again.
- This is the output of fdisk (through an ssh session on the unit)
~# fdisk -l /dev/sdc
fdisk: device has more than 2^32 sectors, can't use all of them
Found valid GPT with protective MBR; using GPT
Disk /dev/sdc: 4294967295 sectors, 2047G
Logical sector size: 512
Disk identifier (GUID): 8b974a2e-8823-42a2-ba93-113c35cb58fd
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Number Start (sector) End (sector) Size Code Name
It basically reports no partitions
- dmesg reports
sdc: unknown partition table
sdc: unknown partition table
sdc: unknown partition table
sdc:
- I even tried putting in another disk, that I know works fine, but with a smaller capacity (1TB). It was detected by the system, I got a notification that the disk was too small for the current volume, but Frontview still reported the disk as dead, but with the old capacity and model number.
I have had the unit for about 2 years and have performed expansion from 1TB to 2TB and later 3TB for each of the 4 drives. Never had any issues and I also replaced 2 failed disks during this time and that also worked fine.
Any clues on what might be the problem?
Is there a way to force the unit to mark the disk as not present/missing?
Thanks.
14 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredYou are running 4.2.16 or later so your disks would use GPT not MBR. fdisk is for use with the MBR partitioning scheme only.
So do e.g.
MDGM-NAS:~# sgdisk -p /dev/sdc
What brand and model disks are these? - rsilva1AspirantHi,
The disks are the Hitachi Deskstar HDS723030ALA640. As I mentioned, I have had 4 of them running for quite some time and the replacement disk I inserted is exactly the same.
You are right about fdisk (which is actually part of busybox), but it still reports the partitions. If I run it for sd[abd] I can see 5 partitions. In any case, this is the output of sgdisk:~# sgdisk -p /dev/sdc
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 74A6315F-A55E-4CE3-8177-6991CFEC5D96
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5860533101 sectors (2.7 TiB)
Number Start (sector) End (sector) Size Code Name
The same command for sda shows~# sgdisk -p /dev/sda
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): AE4A83A1-B2AB-40E3-9FA5-6407FB062EAB
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 4145 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 1953520131 927.0 GiB FD00
6 1953520136 3907024064 931.5 GiB FD00
7 3907024072 5860529038 931.5 GiB FD00 - mdgm-ntgrNETGEAR Employee RetiredIf you do e.g.
# hdparm -I /dev/sdc
does it report the correct info for the disk you have inserted? - rsilva1AspirantYes, the serial number seems to be correct.
If I compare (diff) the output for sda and sdc, I see only the expected differences in Serial number, device identifier and unique ID plus "DMA Setup Auto-Activate optimization", that has an asterisk to its left on the working disk, but not on the replacement one. - mdgm-ntgrNETGEAR Employee RetiredWhat about
# smartctl --all /dev/sdc
Does that report any issues with the disk? - rsilva1AspirantNo errors reported. Even the disk that was originally marked as dead seems to be fine.
I connected it to my PC and ran a smart test, no errors were found. I did the same thing on the replacement disk (that was brand new) and there were no errors for that one either.
It seems that for some reason, the unit is not clearing the "dead" marking for the disk and, therefore, does not start the synchronisation.
As the hdparm command proves, the system does recognise that a new disk has been inserted. Every reboot results in a notification that "Data volume will be rebuilt with disk 3."
As mentioned in my original post, I even removed the disk and restarted without disk in the hope that it would show up as "not installed" or "empty", but it did not. - mdgm-ntgrNETGEAR Employee RetiredRemove the disk while the NAS is on. Wait and see if the disk removal is detected (may take half a minute or so). Then wait a bit more and put the disk back in while the NAS is on.
- rsilva1AspirantI did that earlier today. I removed the disk, got the "Disk removal detected. [Disk 3]" notification. Waited for about 10 minutes and put the disk back.
That resulted in a "New disk detected. [Disk 3]" message, followed by "RAID event detected - Data volume will be rebuilt with disk 3".
Still frontview and RAIDar both report the disk dead and the rebuilding did not start.
By "a bit more", how long do you have in mind? Do you think 10 minutes are not enough? - mdgm-ntgrNETGEAR Employee RetiredYou may not need to wait at all before adding the disk after the disk removal notification appears. Just wanted to see if it made a difference.
What do you see on the display on the NAS itself. After adding a disk you can sometimes see things like Testing Disk etc. before anything is shown in RAIDar or Frontview - rsilva1AspirantOn the NAS, I would see "testing disk" after inserting the new disk. I can't remember the exact message, but then it said something like "test passed" or disk OK.
After a few minutes the "disk failed" (or was it dead?) message comes back up (on the NAS display, that is).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!