NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 516 : Remove Inactive Volume to use the disk #1,2,3,4,5,6
ReadyNAS 516 : Remove Inactive Volume to use the disk #1,2,3,4,5,6 1st was disk no 5 failed, so i have replaced this disk and resync started before the resynce process finish disk 6 got fail and...
[Sat Jul 8 13:37:27 2017] md: md127 stopped.
[Sat Jul 8 13:37:27 2017] md: bind<sdb3>
[Sat Jul 8 13:37:27 2017] md: bind<sdd3>
[Sat Jul 8 13:37:27 2017] md: bind<sdc3>
[Sat Jul 8 13:37:27 2017] md: bind<sdf3>
[Sat Jul 8 13:37:27 2017] md: bind<sde3>
[Sat Jul 8 13:37:27 2017] md: bind<sda3>
[Sat Jul 8 13:37:27 2017] md: kicking non-fresh sdf3 from array!
[Sat Jul 8 13:37:27 2017] md: unbind<sdf3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sdf3)
[Sat Jul 8 13:37:27 2017] md/raid:md127: device sda3 operational as raid disk 0
[Sat Jul 8 13:37:27 2017] md/raid:md127: device sdc3 operational as raid disk 4
[Sat Jul 8 13:37:27 2017] md/raid:md127: device sdd3 operational as raid disk 3
[Sat Jul 8 13:37:27 2017] md/raid:md127: device sdb3 operational as raid disk 1
[Sat Jul 8 13:37:27 2017] md/raid:md127: allocated 6474kB
[Sat Jul 8 13:37:27 2017] md/raid:md127: not enough operational devices (2/6 failed)
[Sat Jul 8 13:37:27 2017] RAID conf printout:
[Sat Jul 8 13:37:27 2017] --- level:5 rd:6 wd:4
[Sat Jul 8 13:37:27 2017] disk 0, o:1, dev:sda3
[Sat Jul 8 13:37:27 2017] disk 1, o:1, dev:sdb3
[Sat Jul 8 13:37:27 2017] disk 3, o:1, dev:sdd3
[Sat Jul 8 13:37:27 2017] disk 4, o:1, dev:sdc3
[Sat Jul 8 13:37:27 2017] md/raid:md127: failed to run raid set.
[Sat Jul 8 13:37:27 2017] md: pers->run() failed ...
[Sat Jul 8 13:37:27 2017] md: md127 stopped.
[Sat Jul 8 13:37:27 2017] md: unbind<sda3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sda3)
[Sat Jul 8 13:37:27 2017] md: unbind<sde3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sde3)
[Sat Jul 8 13:37:27 2017] md: unbind<sdc3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sdc3)
[Sat Jul 8 13:37:27 2017] md: unbind<sdd3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sdd3)
[Sat Jul 8 13:37:27 2017] md: unbind<sdb3>
[Sat Jul 8 13:37:27 2017] md: export_rdev(sdb3)
Yep, that's it.
sde3 is out of the RAID and sdf3 is out of sync.
Any errors on sdf?
I presume sde is the new one (you can check channel number in disk_info.log). Do you still have the original sde? Is it completely dead or clonable?
Do you have a backup?
This is a Data Recovery situation.
There is usually three ways to attempt fixing the array: clone the old drive you replaced and try to reassemble the array with it, or force the array together, or recreate the array in place. These come with the risk of permanently corrupting the array.
It's always safer to contact a specialist. NETGEAR does provide this type of service as a contract.
Thank you - jak0lantash
yesterday i have inserted disk no.5 which was filed erlier, once i have inserted then resync started then after 28 min disk 6 failed i got this msg on ReadyNAS admin page ...
then after few minnutes getting msg remove invalid volume to use disk 1,2,3,4,5,6
right now there is no all disk showing in normal condition but, i am sad due to my data not accessible ... there is one volume data-0 created with raid file and when i move curser on that got same msg as above and also old volume data as it is showing but raid type unknown
i have contacted to netgear for the data recovery contract its cost is 180 USD, but no garranty to succesfull data recovery ????This line says it all:
- [Sat Jul 8 13:37:27 2017] md/raid:md127: not enough operational devices (2/6 failed)
You should not have simply put Drive 5 back in. You needed to clone it to a fresh drive, then insert that one.
A second drive failed in a single-redundancy RAID when the volume was not yet redundant from the first drive replacement. The only way you may have been able to recover at least some of the data is if one of the failed drives is operational enough to clone it. You have likely made that scenario no longer viable by returning a known-bad drive to the array and had it fail a second time in mid-sync.
If you have a backup, then there is no reason to try that. The NAS is telling you (in a hard to understand message) is that the drives currently in it have data on them, but it cannot assemble a volume from them. It wants you to format or replace them so it can create a new volume (with no data). If you have a backup, your best solution is to do just that and restore the data from backup. If you have no backup, then you are much more likely to be successful in recovery with (paid) help from Netgear.
While not typical, this is not a completely uncommon event, especially when all drives are of similar ages. Sync puts a lot of strain on the drives, and a second failure is always a possibility. This is one of the reasons you see folks here saying "RAID is not a backup". Step one on any drive replacement should always be refresh your backup.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
