NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ v2 - volume scan failed to run properly - after replacing failed drive
Hi, I have a ReadyNAS NV+ v2, running RAIDiator 5.3.12 firmware. I replaced the drive in bay #4 after seeing these warnings in the logs (newest entry shown first): Disk failure detected. Detected ...
Yes, this is all the output I get when running df -h
root@readynas:/var/log# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 567M 3.3G 15% /
tmpfs 16K 0 16K 0% /USB
When I run fdisk, I can see the 4 3TB drives listed:
root@readynas:/var/log# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 266306 2147483647+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 266306 2147483647+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 1 267350 2147483647+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 1 267350 2147483647+ ee GPT
Disk /dev/md0: 4293 MB, 4293906432 bytes
2 heads, 4 sectors/track, 1048317 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
Here is the contents of /etc/fstab in case that helps:
root@readynas:/var/log# cat /etc/fstab
/dev/md0 / ext3 defaults,noatime 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/md1 swap swap defaults 0 0
/dev/c/c /c ext4 defaults,acl,nodelalloc,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,noatime 0 2
fdisk won't show anything useful here. But it's clear from the df -h that the system hasn't mounted the data volume.
Do you have a backup of the data?
Unfortunately I don't have a backup of the data, so hoping to be able to figure out how to get access to it.
wsopko wrote:
Unfortunately I don't have a backup of the data, so hoping to be able to figure out how to get access to it.
Understood. I am thinking you have issues on multiple disks. Unfortunately the DM disks (particularly the 3 TB models) are problematic in RAID arrays.
One option is to use Netgear's data recovery service ( https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service ).
Some folks have reported success with a recovery tool called ReclaiMe. That has the benefit that you can see what it will recover before you purchase it. It does require that you be able to connect your drives to a Windows PC.
These are expensive options, but I think any data recovery is going to cost you.
Thanks for all the help, appreciate it!
I looked into both data recovery options, I'm working towards using ReclaiMe, just need to get some hardware together for that option.
Do you think it is worth me trying to put the old drive back into bay #4? My thought is that this old drive may still be good. The array was functioning fine before I swapped drive #4 out, despite it showing SMART errors. My thought is that drive #3 was the one that was caused the problem, as it showed the read errors. Do you know if there is any harm to cold booting the NAS with the old drive #4 in it? My concern with doing this is that the NAS will think that it is a new drive, and start the sync process. Has anyone had experience putting an old drive back into a ReadyNAS?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
