NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Urgently need my NAS up and running. Stuck on Please wait, Booting....
Model RND4410
Has been working fine for years. Now when I switch it on it hangs on Booting please wait.
Blue light flashing, disk drives lights don't come on. Device is on and can be heard.
Even trying to hard shutdown (from blue flashing light) nothing happens.
What can I do to boot this device up? Has more than one drive failed thats why it cannot boot? Have I lost data? How can I retreive data from these drives?
17 Replies
Replies have been turned off for this discussion
What status is RAIDar giving you? https://kb.netgear.com/20684/ReadyNAS-Downloads#raidar
Do you have access to a linux system (or a PC that can be booted using a LIVE boot drive)?
When I connect through RAIDar could not find any NETGEAR storage on your network. Check that your storage device is powered on and connected correctly. For more help, visit http://my.netgear.com.
It doesn't even boot.
I have never had problems with this device, do I have to learn Linux to fix this?
Please let me know a step by step procedure to check this.
StephenB what if I take out the disks and reset the device to factory settings, I will not loose data on the disks right?
chrisl1 wrote:
StephenB what if I take out the disks and reset the device to factory settings, I will not loose data on the disks right?
You can't do a factory resets w/o disks installed. A factory reset installs the system onto the disks.
chrisl1 wrote:
Has been working fine for years. Now when I switch it on it hangs on Booting please wait.
Blue light flashing, disk drives lights don't come on. Device is on and can be heard.
Even trying to hard shutdown (from blue flashing light) nothing happens.
Plus RAIDar won't find it.
1. Are you seeing anything at all on the LCD panel?
2. Try removing the disks with the NAS powered down (labeling them by slot as you do this). Then turn on the NAS and see if you get the normal "no disks" status.
The second suggestion is to see if the chassis or power supply is the problem.
- Ok. Stephen. Need to get data off disks. How can disks if they are configured in a RAID structure? In Disk management all options are greyed out except to format. Gosh this is getting complicated
chrisl1 wrote:
Ok. Stephen. Need to get data off disks. How can disks if they are configured in a RAID structure? In Disk management all options are greyed out except to format. Gosh this is getting complicatedWindows can't read the filesystem even if you could mount the RAID.
First test them with vendor tools (seatools for seagate, lifeguard for WDC). The normal tests (short and long) are non-destructive. Steps after that depend on what we learn from the diags.
Also, you should be able to see the SMART stats from those diags. Please capture the reallocated sector and pending sector counts for each disk. The diags use fairly high thresholds for pass/fail on those items, so it's helpful to see the actual data.
chrisl1 wrote:
Ok. Stephen. Need to get data off disks. How can disks if they are configured in a RAID structure? In Disk management all options are greyed out except to format. Gosh this is getting complicatedI assume you have tried booting more than once. I've had odd instances once in a while of a failed boot after a UPS-commanded shut-down and just rebooting again fixed it.
Sometimes, a single drive going bad can take down the whole system. Remove that drive, and the system will boot, but with the volume degraded. That will let you get at your data and replace the drive to get it back to redundant. The problem is that you need to identify the correct drive to remove because booting with the wrong sub-set can kill the entire volume. I'm sure that's where StephenB is going with this first. The manufacturers' tools are the best way to identify the offending drive. If you can boot to the boot menu, you could try the NAS disk test, but it may run into the same problem as a normal boot. The NAS boot test uses the drive's long self-test feature and can take hours. The quick test in the manufacturer's tool takes only minutes and may identify the problem drive.
It is possible to get the data off with a PC and a Linux boot disc, but you have to have a way to connect all the drives to the PC simultaneously. So, lets hope the other method works.
A bad SATA backplane is still a possibility instead of the drives, but that's rare unless there was physical damage. Insufficient power supply voltage with the added load of the drives is another. But if your drives have also been "working fine for years", it's more likely to be one of them.
Sandshark wrote:
The problem is that you need to identify the correct drive to remove because booting with the wrong sub-set can kill the entire volume. I'm sure that's where StephenB is going with this first.Correct. Cloning might also be a possibility if there is more than one failing drive.
Getting diag/disk health info is a critical step.
Guys, I have finally managed to find the bad disk it is making a weezing noise and it shows as 4GB in total instead of 1TB.
Now if I put the labelled disks back into netgear will no data loss occur if I replace the failed drive with a new one, will the volume rebuild with minimal data loss?
Shutting the system down before it goes to check the volume would be ok?
chrisl1 wrote:
Guys, I have finally managed to find the bad disk it is making a weezing noise and it shows as 4GB in total instead of 1TB.
Your NV+ v1 NAS uses a dedicated parity disk, and I believe that is the disk that failed. Those parity blocks are written to an unpartitioned area of the disk.
Was this disk in slot 4? Usually the parity disk is in that slot.
chrisl1 wrote:
Now if I put the labelled disks back into netgear will no data loss occur if I replace the failed drive with a new one, will the volume rebuild with minimal data loss?
Assuming you've correctly identified the failing disk, It should boot up without that disk in place.
In general RAID tends to be all-or-nothing. When you add a disk, the system should resync with no data loss. If that process fails (due to a second failed disk) then you will lose everything.
chrisl1 wrote:
Shutting the system down before it goes to check the volume would be ok?
There is a boot option to skip the volume check, and you should use it in this case. Then make a backup before doing anything else.
See pages 23-24 here: http://www.downloads.netgear.com/files/GDC/RND2110/Duov1_NV+v1_HW_en_06Dec11.pdf
- Hi Stephen
No, It is Disk 2. Should I boot with Knoppix and try copy all data off the disks first before I put the working ones in net gear just in case I have another failed disk ?
chrisl1 wrote:
Should I boot with Knoppix and try copy all data off the disks first before I put the working ones in net gear just in case I have another failed disk ?That is reasonable option. There is a guide here: http://home.bott.ca/webserver/?p=306
chrisl1 wrote:
No, It is Disk 2.It still is possible that is the parity disk - there should be exactly one that doesn't have a partition for the C volume.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
