Forum Discussion

Aspirant

Dec 06, 2019

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...

Gyttja

Aspirant

Dec 14, 2019

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?

BastianWtal

Aspirant

Jan 11, 2020

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

Sandshark
Sensei
Jan 12, 2020
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.