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 reported increasing SMART errors on Disk 4, so I quickly ordered a replacement.
With the new drive in hand, I accidentially pulled Drive 1. Quickly realizing my mistake (30-45 seconds) I reseated Drive 1 and pulled Drive 4 and swapped it for the new drive. Yes, Google now tells me that was not the best course! Unfortunately, the new drive was DOA (a first for me!). Left it to resync overnight, not realizing the issue with the new drive.
Next day, saw there were still errors so pulled the bad "new" Drive 4 and reinstalled the original, hoping this would at least return the NAS to working order while I replaced the faulty drive.
Through multiple reboots, I receive the error: "Volume scan failed to run properly." and "The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media-u6 XFER backup-u6"
So now all of the shares are inaccessible. The user share will mount, but shows no files.
I've opened a support ticket #26094210, but perhaps the community can help as they have in the past. mdgm solved an issue with too many logs on my NV+--I'm still grateful for that assist!
Thanks,
Christopher
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!
10 Replies
Replies have been turned off for this discussion
As you likely realize now, when you reseated drive 1 the NAS treated it as a drive replacement, and started rebuilding the array. During the rebuild period, you don't have RAID redundancy. Since you pulled drive 4 before the rebuild finished, you lost the volume.
I think you'll need support on this.
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!
We have this same problem with our Pro 6 but we NEVER pulled a drive while the array was rebuilding.
Here's the chronology of events:
1) drive 5 reported errors and eventually died altogether
2) drive 6 started reporting errors but wasn't dead when we pulled 5 and replaced it
3) the array started rebuilding but eventually failed with an error and drive 6 was marked dead and noticed 5 was marked as a hot spare and the volume went into read only life support mode (very puzzling as 4 drives are plenty for at least RAID5 and we're using FLEX RAID2 or something to it doesn't make sense)
4) we don't have another drive yet so we reseated 5 and booted back up and it began to rebuild and we were able to work again for about 3 hours, drive 6 was just marked dead
5) the rebuild failed again and yet again the unit went into life support mode with 5 as a hot spare so we shut down and this time reseated both 5 and 6 and booted back up
6) the unit failed a volume check now (and has ever since) and again put the volume into life support mode with 5 as a hot spare
7) we shut down and pulled drive 6 and reseated 5 and booted back up and had the same problem
8) we shut down again and reseated 5 and put 6 back in and booted back up and now the volume isn't being recognized at all (and hasn't been since)
We still have the old failed drive 5. I'm going to try to put that back in to see if that makes a damn bit of difference but am not hopeful. The total data footprint here is laughable. It's like 500GB TOPS and we have 6 2TB drives in this sucker.
So we NEVER pulled a drive while a rebuild was happening ever. Now the unit is totally down and tech support is totally pessimistic of being able to help because 2 drives are failed. We now need level 3 support at an additional $200 (and we already added a support contract for ~$300 to get back in the graces of tech support help) for a "maybe but not likely able to help". They suggested we call the number when we made the decision to go forward with level 3 support and that the tech helping us was going home for the weekend and when I called, the automated number hangs up when we tell it we're calling about a ReadyNAS storage product and it says to file a support ticket online. SO we have NO HELP THIS ENTIRE WEEKEND and this is the repository of all data for 2 companies. We are dead in the water but do have backups that we're looking into now, but does anyone have any suggestion on how to move forward? If this were a regular server I was maintaining, Linux or Windows with a RAID 6 array with failed drives I'd be doing some Linux scripting with dd and attempting to rebuild the data given the amount we need is SO SMALL ANY 1 DRIVE SHOULD CONTAIN A COMPLETE FRIGGING COPY WITH OVER 70% FREE SPACE!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
