NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro 6 - Volume scan failed to run properly
Hi -- Long time ReadyNAS user with very few problems to report. Just ran into one, sadly. I have a ReadyNAS Pro Business Edition [X-RAID2] with 6 disks running RAIDiator 4.2.28. FrontView rep...
A follow-up : I did indeed need support, but they were able to restore the volume with 5 good disks out of the six. They had to escalate to level 3 and remote in, but were able to get everything working again. The NAS was well past warranty, but the $75 per-incident support was money well spent.
And for the record, Netgear support was stellar. Every person I spoke to was competent, knowledgeable and polite. They called back when they said they would and didn't miss a beat, regardless of the handoff between four different people (or more, for all I know). Great job, ReadyNAS Support Team!
I never intended on that hot spare. We have XRAID2 and for whatever reason (this never has happened before when one drive failed, was replaced, while another was giving trouble) AFTER the rebuild failed it set the new good drive 5 was set as a hot spare for no frigging reason. The 4 drives were showing all the data in the volume just fine, but it was read only due to life support mode. Why wouldn't it rebuild with 5 I have no idea. We still have the old drive 5, but in theory, we'd only need one new drive to replace the dead drive 6.
There has GOT to be a way to recover this because we DID HAVE RAID 6 YESTERDAY! How can the entire volume be lost with RAID 6 and/or why the hell would it go from RAID 6 to RAID 5 with a hot spare just because drive 6 just died?
SarahS3074 wrote:
There has GOT to be a way to recover this because we DID HAVE RAID 6 YESTERDAY!
You didn't say anything about RAID-6 in your earlier post. You are saying you had set up XRAID2 with dual redundancy? By default it is only single redundancy.
Netgear Support can tell you exactly what raid mode you were in from your logs.
SarahS3074 wrote:
I never intended on that hot spare.
Understood. My explanation (which assumed single redundancy btw) is that the resync failed because drive-6 failed while it was running. So drive 5 was never added to the array. Of course I only have the information in your post to go on.
Again, Netgear support should be able to tell you what happened.
It is XRAID2 and it did say RAID6 (which I thought defaultly WAS dual redundancy).
Here's some output from dmesg that leads me to believe it's RAID6 still (from the logs we sent to support who are completely pessimistic on being able to help and decided to go home for the weekend):
md/raid:md1: device sda2 operational as raid disk 0
md/raid:md1: device sdd2 operational as raid disk 3
md/raid:md1: device sdc2 operational as raid disk 2
md/raid:md1: device sdb2 operational as raid disk 1
md/raid:md1: allocated 4272kB
md/raid:md1: raid level 6 active with 4 out of 4 devices, algorithm 2
RAID conf printout:
--- level:6 rd:4 wd:4
disk 0, o:1, dev:sda2
disk 1, o:1, dev:sdb2
disk 2, o:1, dev:sdc2
disk 3, o:1, dev:sdd2
md1: detected capacity change from 0 to 1073610752I just put in the old bad drive 5 to see if that'd help and it didn't (volume scan still fails and no volume found at all), tho now Frontview seems to show all 6 drives as healthy/available for use. We do have backups of most of our key data but I'm still FLOORED that this happened with 4 perfectly healthy drives in a RAID6 configuration.
The net here is that the explanation (and options for resolving it) require analyzing the logs.
SarahS3074 wrote:
It is XRAID2 and it did say RAID6 (which I thought defaultly WAS dual redundancy).
XRAID2 by default uses single redundancy (RAID5 if you have > 2 disks). You can choose to add a disk for extra redundancy if you wish - telling it to use RAID6. That's a key piece of information, that was missing in your first post. My original explanation assumed the default single redundancy setup.
Well for what it's worth arrays md0 and md1 (the core array for the partition housing the main /etc and other folders for the OS, and the array for the swap partitions respectively) both show as RAID 6 arrays. But somehow md2 is RAID 5 (which is and was the problem). Because of the chronology of events, it's clear to me that it WASN'T RAID 5 Thursday morning when we pulled the dead drive 5 out and installed the new one and a resync began. That morning, BEFORE we pulled drive 5 we saw drive 6 show up as dead as well (or dying, I can't remember at this point). Nonetheless, we're in the predicament that we're in and we are faced with attempting to clone the now dead drive 6 to a good drive and put it in and see what we can do about reconstructing the RAID 5 array without drive 5.
In short, this shouldn't have happened with 4 perfectly working drives in a RAID 6 array, I should've been getting life support errors and that's only until it realized a perfectly good drive was inserted ready for it to just be 1 drive down. This has happened to us before and wasn't an issue at all.
Never once have I complained that RAID should be our backup, by the way, the need for offsite backup is NOT lost on me whatsoever and is why we are able to have SOMETHING in place at this point.
Thanks for the help, and for what it's worth Netgear support is quite useful when they're open and actively responding.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
