NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ stuck on "Booting Please wait"
I'm having a very similar issue, though removing the disks had no effect. I had to move the NV+ as it was too loud in the location it was, so I shut it down correctly (waited for it to turn off by itself). Then once I had moved it, by the handle, to its new location, about two metres away, I turned it on again.
Once I turned it on and attached it to the network in its new location It said on the front panel that it was either reinstalling or updating FW, I can't remember exactly, but I assumed it was just doing that as it hadn't been rebooted in over a year. Once it stopped displaying that it went to 'Booting Please wait' and then just 'Booting' and never left that state.
I've tried everything I dare to try, I downloaded and reinstalled the OS (reset button 5 seconds), I reseated and successfully tested the memory, I tried USB booting (power button 20 seconds), I tried bypassing the volume check (power button 5 seconds), none of these things had any effect and it remains in the Booting phase. How can I proceed, based on the condition that the data is infinitely more important than the device?
Many thanks.
Once I turned it on and attached it to the network in its new location It said on the front panel that it was either reinstalling or updating FW, I can't remember exactly, but I assumed it was just doing that as it hadn't been rebooted in over a year. Once it stopped displaying that it went to 'Booting Please wait' and then just 'Booting' and never left that state.
I've tried everything I dare to try, I downloaded and reinstalled the OS (reset button 5 seconds), I reseated and successfully tested the memory, I tried USB booting (power button 20 seconds), I tried bypassing the volume check (power button 5 seconds), none of these things had any effect and it remains in the Booting phase. How can I proceed, based on the condition that the data is infinitely more important than the device?
Many thanks.
28 Replies
Replies have been turned off for this discussion
- The thing is that to get the data off safely it is important to diagnose if there is a hardware issue first.
- Ok this is pretty strange and so I'm going to go step by step.
I thought I'd give it another go and try to revive the NAS. so I tried booting without one HDD plugged in, first with disk 3 ejected, on which it hung as it always has, and then with disk 4 ejected. Miraculously, it booted when disk 4 wasn't in. However, the LED of disk 3 was blinking. I checked RAIDar and it said disk 3 was dead. Now I've put in a fresh disk into bay 3, put disk 4 back in its original place, but it again refuses to boot, and isn't visible on RAIDar. Advice? - Trying to replace a disk in RAID-5 array when another disk is already removed is a great way to destroy your data. You seem amazingly resistant to following the original advice - label the disks by slot, and run disk diagnostics on them. And you are taking a risky path instead.
If you are determined not to run diags, then try powering down again, remove disk 4, reinsert the original disk 3, and try rebooting. If if works, then back up the data. Check the SMART+ stats on the three remaining disks, and let us know if you see anything concerning. And buy a replacement for disk 4.
If it doesn't work, then follow mdgm's advice - power down the NAS, connect the drives to a windows system, and run the vendor diagnostics. - I thought the purpose of the thing was that if one disk failed (in this case disk 3) then I can put in a fresh one and it'll rebuild itself? I've been careful to not have two disks missing at once. I'll run the diags, but I know at least that one disk is dead. What I don't understand is why a disk failure can result in the thing not booting, isn't the point of this that it should fail gracefully? Otherwise it's not much more use than a single disk alone, as a failure of a single disk in this case has rendered my data inaccessible.
- I'll take the disks with me tonight and run the diags on them. If disk 3 is fubar though, and it won't boot with a fresh disk in its place, then how can I proceed?
- If you have multiple disk failures, then you are in a bad spot as far as data recovery goes.
Sometimes it is possible to "clone" a failing disk to a new one. However, that isn't always possible - certainly it isn't if the disk isn't readable at all. Even if it is mostly working, there is almost always some file system corruption/lost files. - AFAICT it's just disk 3 that's bad as that's the one that showed orange in RAIDar for the brief moment I was able to get the NAS to boot, with disk 4 removed.
- The fact that it tried to boot with disk 4 removed suggests that disk 4 has failed - and in a way that would likely prevent cloning.
Disk 3 might also be degraded - the diagnostics should provide some useful information. - What I don't understand is that the whole system was working perfectly fine until I had to reboot it. I'll run the diagnostics tonight and have more info soon.
- Ok you were all right. Disk 4 is so dead it won't even show up in SeaTools, and threw a S.M.A.R.T. error before my machine even booted. All others passed a SMART and a generic short read test. What's the usual procedure in case of a disk failure?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
