NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[Solved] ReadyNAS Ultra 4 (RNDU4000) stuck on booting... #24
Hello!
I have traid to find answers on this forum and google, but I could not find anything that work. Hoping for help here :-)
My ReadyNAS Ultra 4 was powered off 1 month due to moving to a new apartment.
When I booted it up it said that it was no partion and no data on the unit. All 4 diskslight were green.
(Good thing I had everything backed up!)
Traid reboot, and factory reset from the GUI.
The factory reset went wrong, and the unit is stuck on "booting".
I traid factory reset from the boot menum but id does not work - it says "ERR: Could not p" in the display." Same issue on OS reinstall from boot menu.
I´m able to boot it up in tech support mode, and reach it by telnet, raidar and ping - but not the GUI.
I belive something is wrong on the FW on the device, and think I need to do a OS reinnstalation from telnet, but I can´t find any guides to this?
Thanks a lot for any tip!
I have traid to find answers on this forum and google, but I could not find anything that work. Hoping for help here :-)
My ReadyNAS Ultra 4 was powered off 1 month due to moving to a new apartment.
When I booted it up it said that it was no partion and no data on the unit. All 4 diskslight were green.
(Good thing I had everything backed up!)
Traid reboot, and factory reset from the GUI.
The factory reset went wrong, and the unit is stuck on "booting".
I traid factory reset from the boot menum but id does not work - it says "ERR: Could not p" in the display." Same issue on OS reinstall from boot menu.
I´m able to boot it up in tech support mode, and reach it by telnet, raidar and ping - but not the GUI.
I belive something is wrong on the FW on the device, and think I need to do a OS reinnstalation from telnet, but I can´t find any guides to this?
Thanks a lot for any tip!
14 Replies
Replies have been turned off for this discussion
- Can you check that at least one of the drives is ok by running vendor tools extended checks on it.
Then insert this disk on its own in the nas and factory default the unit.
If this fails then the OS on the flash is probably corrupt as you are currently thinking.
Do you know what firmware is on it?
The procedure for reinstallation can be done using ssh or telnet but the method is not publicly available. There is a forum member who may be able to help you though, just wait. In the meantime just confirm that it's not an issue with the OS not being able to write to the disk during factory default, by doing what I suggested above. vandermerwe wrote: Can you check that at least one of the drives is ok by running vendor tools extended checks on it.
Then insert this disk on its own in the nas and factory default the unit.
If this fails then the OS on the flash is probably corrupt as you are currently thinking.
The procedure for reinstallation can be done using ssh or telnet but the method is not publicly available. There is a forum member who may be able to help you though, just wait. In the meantime just confirm that it's not an issue with the OS not being able to write to the disk during factory default, by doing what I suggested above.
Thanks a lot. Testing factory reset disk by disk.vandermerwe wrote: Do you know what firmware is on it?
I think it´s running: RAIDiator-x86-V4.2.26- I did try to make a quick test by just factory reset with one drive inn. As soon as it starts to reset it says ERR:Could not p.
Traid with 2 seperat disks now, trying with the other ones as well.
When it says "ERR:Could not p" I belive there is no need to wait any longer? I would guess it will fail any way, right?
Thanks for any reply! :-) - Yes, you must verify that the disk you put in is ok.
It's also worth running a memory test using the boot menu, prior to this just check that the memory is seated properly. vandermerwe wrote: Yes, you must verify that the disk you put in is ok.
I have now traid to to a factory reset with only 1 disk at the time with all 4 disks. All fails with "Err could not p" immediately.
I don´t have any way of testing the disks from here, but I would be very suprised if all 4 disks would fail at the same time.vandermerwe wrote: It's also worth running a memory test using the boot menu, prior to this just check that the memory is seated properly.
I´ve started memory test from the boot menu now after making sure it was properly seated. (I have the original 1024 MB RAM innstalled)
I´ll post back here ones it´s finished.
Thanks for all your help, hoping the someone your talked about could take a look or give som guidance for telnet FW upgrade.- I agree it's highly unlikely all 4 disks would be bad.
- You could try one more thing and that is to try factory default with the drive in bay 2, this will exclude a bad bay.
vandermerwe wrote: You could try one more thing and that is to try factory default with the drive in bay 2, this will exclude a bad bay.
Will try that when the memory-test is done. Thanks for all your help so far!- No worries.
I'm sorry I can't advise you on the method for reinstalling the OS onto the flash, but someone will. I hope it's the solution.
One thing I should have asked is whether the unit is still under warranty? If so you might want to open a support ticket. - As the unit is still under warranty and there is a hardware issue, you should receive assistance from them.
File a support ticket. You may still get assistance here which could be quicker, but support should help you.
You'll need to file the ticket online at mynetgear.com.
They don't necessarily need to have the unit, most things can be fixed remotely.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
