× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Gyttja
Aspirant

Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Hi,

 

I have a readynas RNDP6000 / ReadyNas Pro 6 with 6 disks.

A while ago I use the mothod found on this forum to upgrade it to OS6, worked like a charm. 

Now I have a disk that crashed and the system shut itself off to protect the raid array.

I put in a new disk and tried starting it up again.

 

The thing is, it wont boot anymore, the screen just says readynas, and nothing happens. Not even if you keep it on for hours. 

I also tried to boot the recovery menu (Holding the reset button on the back with a paperclip and start the device). But it wont come up.

Is there a different way to get to the boot menu beacouse its OS6 now (I only needed the boot menu before with the old OS, so I use the same method but am not sure if thats still the same with OS6).

 

Or shall I try to boot from a USB stick with recovery software, of so, wich recovery software do I need? the original Radiator 4.2 Recovery tool:| https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool

 

Or one for OS6, and if so what is the one to use? Beacouse I can find a lot for specific types of nas systems, but of course not the one for RNDP6000 as it does not officially support OS6.

 

Please help as I really like to keep using my readynas.

PS, if the disks will get formatted its not a biggy, I have all my data still on my computer, and use the Readnas as backup system.

Model: RNDP6000|ReadyNAS Pro 6 Chassis only
Message 1 of 10
StephenB
Guru

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?


@Gyttja wrote:

The thing is, it wont boot anymore, the screen just says readynas, and nothing happens. Not even if you keep it on for hours. 

This actually sounds like a power supply failure to me.  If the supply is only outputting 5 volts, then you will see this symptom.

 

Try powering down, and removing all the hard disks (labeling by slot).  Then power up, and see if the system still does this, or if it boots and displays no disks on the LCD.  

 

You can also try accessing the boot menu (which is done the same way it was before), and see if that responds.

 

The PSU can be replaced, @Sandshark is a good resource on doing that.

Message 2 of 10
Gyttja
Aspirant

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Seems like you are right.

Disks out is same simptons, makes no difference at all.

 

I will try to figure out how to replace the powersupply.

Message 3 of 10
Gyttja
Aspirant

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

 

@Sandshark 
Do you know it this one whould work? As I can only find the one you recomend for very high prices in europe.

https://www.megekko.nl/product/0/1735615/FSP-Fortron-FSP300-50GHS-85-300W-SFX-Wit-power-supply-unit?...

It is suggested in this tread:

https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Old-Legacy/RNDU6000-doesn-t-boot-Stuck-on-quo...

Message 4 of 10
Gyttja
Aspirant

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Oh wait, is this the one I need?
https://azerty.nl/product/seasonic/3323326/ssp-300tbs-voeding-intern-tfx12v-2-3?utm_source=nl.hardwa...

 

Or this:

https://www.megekko.nl/product/0/129444/Inter-Tech-Argus-TFX-300W-300W-TFX?r=googleshopping&gclid=Cj...

 

 

Or this one:

https://www.alternate.nl/html/product/1354550?utm_source=GoogleShopping&utm_medium=cpc&utm_campaign=...

 

It states that the 20pin connecter has 35cm line lengt. Maybe I save on the 20pin extending cable than? Or do I still need that?

And I need to make one extra 4 pin connector, not a problem, I make it myself or maybe I still have some sata to 4pin converters laying aroung.

Message 5 of 10
Sandshark
Sensei

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?


@Gyttja wrote:

 

@Sandshark 
Do you know it this one whould work? As I can only find the one you recomend for very high prices in europe.

https://www.megekko.nl/product/0/1735615/FSP-Fortron-FSP300-50GHS-85-300W-SFX-Wit-power-supply-unit?...


The specs look good (better then the original), and it has enough Molex connectors.  You will need a 24-pin ATX extension.  The fan is not going to line up perfectly, but should work well enough.

 

None of the others you listed are SFX format; so they won't work.

 

There are a lot of things that can cause that symptom, though the supply is most common at this age point.  If you have a spare standard ATX supply available, you can install it externally just to make sure that is the problem.  Or, you can use it just long enough to get your files off the NAS and onto a new one.

Message 6 of 10
Gyttja
Aspirant

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

I ended up buying this one:

https://www.spire-corp.com/power-supplies/jewel-sfx-300w-pfc-sp-sfx-300w-pfc/specs/

 

Everything fits without having to make any changes to it.

The power supply seems to work as it should, as the Nas starts with the readynass on the screen again.

 

As fix it didnt work though, still the same problem, only readynas on the screen, also when I use the reset button (doesnt need to be connected to the netwerk right?).


I also spotted a little battery on the mainboard, switched that one as well for a new one. 

Did not make a difference.


(luckaly I can still send the power supply back).

Any other ideas?

Message 7 of 10
Sandshark
Sensei

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Unfortunately, there are a number of things that can result in that symptom, the power supply just being the most common.  The best next step is to install a VGA connector to the internal VGA header to give you access to the BIOS and boot screens.  If you want to try an OS re-install, you need to create an OS4.2 sytyle USB with a renamed OS6 update file on it.  But if thet were your problem, you would most likely see progress messages on the display..

 

The abttery opon;y keeps the time of day clock running when power is off, so shold nto have been a part of the problem.

 

The necessary VGA cale is a pretty common 16-pin dual-row header to 15-lin VGA, as was used on many dual-display cards years ago for the scond VGA connector.  Here is a good picture of how it plugs in: https://www.ixsystems.com/community/threads/freenas-on-readynas-pro-6.24666/ .

Message 8 of 10
BastianWtal
Aspirant

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?

Is it completly death or is SSH maybe working? If SSH is working you might wish to try to perform an ReadyNAS Bios update (the bios update isn´t done via firmware) as explained here: https://www.admin-enclave.com/en/articles/linux/484-upgrade-the-bios-from-an-readynas-device.html

 

Message 9 of 10
Sandshark
Sensei

Re: Readynas RNDP 6000 with OS6 with crashed disk wont boot anymore, how to recover?


@BastianWtal wrote:

IIf SSH is working you might wish to try to perform an ReadyNAS Bios update (the bios update isn´t done via firmware) as explained here: https://www.admin-enclave.com/en/articles/linux/484-upgrade-the-bios-from-an-readynas-device.html

 


Why would you think that a motherboard BIOS issue would in any way be related to a system working one day and not the next, and would be an error that allowed most of the OS to run (to give SSH access), but not all?.

 

The procedure you linked to is out of date, being for Debian Wheezy based ReadyNASOS 6, where it is now based on Jessie, though the process would be similar.

 

IMHO, this is really terrible advce.  Best result, if done properly, is no effect in almost every case.  Worst result, if done improperly, is a bricked device.  If there is a desire to update the motherboard BIOS, do it on a functioning system.  It certaily should not be attempted in this instance without some additional indication that this could be the problem (which can be gained looking at the boot screens via the VGA header).

 

And as for that update "not being done via firmware", what do you think is executing when you SSH into the box?  While it's "just" the Linux base for the firmware (which is the vast majority of it), no Netgear-specific programs, it is the "firmware" nonetheless.  And the apt-get installs new packages into that firmware.

Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 1064 views
  • 0 kudos
  • 4 in conversation
Announcements