Have a ReadyNAS NV+ V1 (4x WD 2TB drives) that seems to have an issue.
What steps can I perform to get the device operational again or attempt recovery of my data?
If a drive has failed, can I access the data without replacing the failed drive? (Isn't this what RAID systems do?)
If I replace the drive that is flashing, will the system rebuild / resync it? or will I lose the data?
This is what happened so far:
Accessing the Web Admin page, there was a message that one of the drives had a reset, and that I should peform a RESYNC.
At the time I was still able to access the data from the RAID device mounted on my computer.
I inavertantly clicked 'resync', (had opened menu to look at options) and the system became unresponsive.
The mount disconnected, and after a time the LCD display was off and there was no response from the mounted share (disconnected) and the web admin page would not load.
waited a day, then pressed Power button to turn off system.
Power on and system stuck at rebooting for another day and a half.
press and hold power off.
Power on again and select 'skip disk check' from boot options
System says 'booting.. resyncing volume'
can ping system, shows up on RAIDar widget (Mac OSX), big OK, and all drive lights green.
Shows the correct data usage.. 2530 GB (45%) of 55389 GB used, RAID Level X,
Raidiator 4.1.10
RAIDar app finds device ok.
Again shows all lights green.
Cannot connect to device with file share or web admin.
On the device, disk1 light is flashing, disk2,3,4 lights are solid.
On the device, disk1 light is flashing, disk2,3,4 lights are solid.
Display shows: Booting.. Resyncing volume.
It looks like disk 1 is the drive that's resyncing. That normally won't take more than 24 hours (though it's been a while since I did a resync on my own NV+). That suggests that a drive might be having trouble - but it's not necessarily the drive that is resyncing.
If you hover over disk 1 in RAIDar, you should get some progress information. It'd be helpful to know the progress and the estimated completion time.
On the device, disk1 light is flashing, disk2,3,4 lights are solid.
Display shows: Booting.. Resyncing volume.
It looks like disk 1 is the drive that's resyncing. That normally won't take more than 24 hours (though it's been a while since I did a resync on my own NV+). That suggests that a drive might be having trouble - but it's not necessarily the drive that is resyncing.
If you hover over disk 1 in RAIDar, you should get some progress information. It'd be helpful to know the progress and the estimated completion time.
I hover over the disks (and everything else) in RAIDar and it all seems to show normal .. nothing resyncing.. just disk size, temp, etc.
so you are saying that the flashing light doesn't mean the drive has failed?
Re: ReadyNAS NV+ Stuck on booting - resyncing volume
Yes i have a second NAS.. 2x 2TB mirrored.
The question I have now .. is there anything i can do other than wait?
Was looking into raid data recovery software but didn’t want to buy new drives or software yet.. or pull the drives an plug them into another computer till i know what the best options are.
The question I have now .. is there anything i can do other than wait?
You've waited a couple of days now, correct? At some point you'll need to give up on it. Normally a resync will complete within a day.
You can try shutting down (pulling the plug if necessary), and then booting with only disks 2,3,4 in place. I suggest using the boot menu to skip the volume check if you do that - you don't want the NAS to try and "repair" any file system issues at this point.
If the NAS boots normally (showing a degraded volume, since a disk is missing), then back up all the data on the NAS. If it fails to boot, you could try the other combinations of three disks (1,2,3; 1,2,4; 1,3,4).
Before trying to reinsert disk 1, I'd recommend testing disk 1 with vendor tools in a Windows PC (Lifeguard for Western Digital, Seatools for Seagate) using both the long non-destructive test and the full write zeros (erase) test. Also, download the full log zip file, and look at the smart data and also for disk-related errors in system.log and kernel.log.
