ReadyNAS Ultra 6 - stuck at "ReadyNAS" boot

I have been able to prove that I can get 2 devices in this "READYNAS" lock state.

All steps traceable, and for me it happened after upgrading to 6.10 and setting the power timer on both devices to cycle down in the evening and come up in the morning, where both failed with the same VDP wipe.

However, Marc_V  helped in recovering both devices.

My respect and thanks!

Hello,

I'm exactly in the same user case that tschutte ; my ReadyNas Pro 6 (RNDP600U) is stuck on "READYNAS" on boot.

As tschutte , the ReadyNas was in 4.2.31 and I upgrade to 6.9.5 with usb recovery tool and after update to 6.10.7 with Web Interface.

All was fine, network, volumes, shares, users ...

I shutdown the ReadyNas to move it in an other place and when it started, it stay lock with "READYNAS" display.

Now I'm not able any more to boot on a usb key or go in the boot menu to reset Factory Default.

Help will be appreciated :

tschutte : How did get out of this ReadyNas stuck mode ?

Marc_V : What are sequences or manipulation to go in Boot Menu ou Recovery Mode or OS Install Mode ?

Many Thanks for your help.

Thierry.

tschutte had a corrupted VPD file, which is an encrypted file in the boot flash that contains information on the model and serial number and only Netgear can create. It's used to prevent folks from creating a "do it yourself" ReadyNAS from generic hardware and running unlicensed ReadyNAS software on it.

There are many things that can result in the unit not getting past the "ReadyNAS" display.  AFAIK, a bad VPD won't prevent you from using the boot menu or doing another USB recovery, so you may have a completely different cause, or at least something additional.  Other corruptions of the data in the boot flash can result in no boot menu and no normal boot, but you should still be able to do another USB recovery and fix that if there's not an underlying hardware issue.  But you do have to use a 4.2.x style USB recovery with an OS6 image, not OS6 style USB recovery.  The one you used to convert the unit (which isn't the way conversion should be done) should work if that's not a part of the problem.

As Sandshark said, I had to recover to a state where I could boot into Technical Support mode.

For me, I put in a scatch temporary disk and recovered into an old OS 4.2 state. Initially recovering into OS 6 was not working for me due to problematic USB sticks. 

Good luck

I had a very clear and specific and reproducible use case that resulted in a corrupt VPD (and it is probably a bug of OS 6 running on old HW). I set the power timer to shut down my 2 devices and then start them up at a certain time. It went down but never came up again.

Thanks to the help of the gentlemen contributing here, I managed to recover both

---

tschutte wrote:

I had a very clear and specific and reproducible use case that resulted in a corrupt VPD (and it is probably a bug of OS 6 running on old HW). I set the power timer to shut down my 2 devices and then start them up at a certain time. It went down but never came up again.

Thanks to the help of the gentlemen contributing here, I managed to recover both

---

I'm glad you were able to recover.

FWIW, this is not a problem I have with my Pro-6.  It is running 6.10.7, and is on a power schedule.