NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas duo v2 not starting after power failure
We had yesterday powerfailure and now the unit will not boot correctly nor is visible in Raidar. After power up; Power button LED, USB and backup status LED, disk 1 LED, and disk 2 LED gets lights ...
Hi John,
After 10 different USB's I ve got two different outcomes. Neither though would solve the issue.
First just to confirm that the files you refered where on thelink that Marc_V had posted (not sure do the links copy here correctly.
Here is the link for the files.
And refered to file usbrecovery.v1.0 (for V2 devices).rar
Under this file i copied directly the three files to the USB formatted to single partition and FAT32 ( I did not run any usbrecovery tool...should I have ?)
\usbrecovery.v1.0.T1\marvell\Duov2 : ulmage-recovery
\usbrecovery.v1.0.T1\marvell : RAIDiator-arm-5.3.13
\usbrecovery.v1.0.T1\x86 : intrid.gz ( this though was avail in folder x86_32Bit but seemed to be exactly same size)
Powering the unit on with USB inserted into front and keeping the BackUp button pressed (approx 15 seconds) two different variants happened.
1.) The Activity led above BackUp button would blink, after 3-5 seconds also the USB drive light would blink maximum additional 5 seconds total and the unit would do a reeboot. If I continued to press still BackUP button it would do a same recycle. If releasing the button it would reeboot and return to the original fail state ( all leds light as in my original post)
2.) With 3 USB's the The Activity led above BackUp button would blink much longer and the drive was also blinking like 20 seconds but the drive would go silent , but backup light would continue blinking. I gave it approx 20 minutes , but it would not power it self off ( As I understood from the documenst that it would do if it was successful).
So just before going and buying a new NAS unit can you confirm that I did the process correctly.
Thank you very much already for all the help you have given to me.
Soiski71 wrote:\usbrecovery.v1.0.T1\x86 : intrid.gz ( this though was avail in folder x86_32Bit but seemed to be exactly same size)
The initrd.gz is for x86 ReadyNAS (the 32-bit and 64-bit x86 units use one initrd.gz file but different kernels). You have a Marvell ARM ReadyNAS. I think the file you need is called initrd-recovery.gz (or something like that) not initrd.gz.
Edit: It's called initrd-recovery.gz and is in the marvell folder.
So you need
initrd-recovery.gz, uImage-recovery and the firmware image on the USB key.
Thank you John and mdgm,
Finaly got it working correctly with the correct files (running through the usbrecovery program.) The recovery/update took approx 1.5 minutes and then the unit powered down (indicating succesfull recovery upload). Unfortenately when reeboting after the same issue persists. POWER, DSK LED1 and DSK LED2 and USB would lit up. Pushing backup would just shut down all led's. Same if pressing reset in start. Unable to power down unit from power button. RAIDAr never sees the unit online (even though ethernet light is blinking/shows activity).
Just one final question. I did the recovery with out the HDD's in bay as I want to be able to restore the files and do not want (by accident) screw the files on my venture :). Might that have any effect ?
Soiski71 wrote:Just one final question. I did the recovery with out the HDD's in bay as I want to be able to restore the files and do not want (by accident) screw the files on my venture :). Might that have any effect ?
It means that the OS was not re-installed to the drives. But you aren't far enough in the boot process for that to matter.
Does the unit turn on via the power button, or just because you plugged it in? Does it turn off if you press and hold the button?
The problem could be just the power supply, and a replacement is pretty cheap if you want to give it a try. But it is more likely something else.
Hi sandshark.
The unit powers on normally from the power button. Only the powerdown does not happen from long / 2 x pushing the power button. I agree with you that most likely it is "something else" than the power unit.
Hi StepehnB,
The unit newer gets to network (Raidar does not see it) nor can I see it getting any IP on switch so WebUI can not be used.
Power Up was never the issue, but seems that it does not go through bootup correctly (see original post).
Best regards, Sami
I just tried the long press on my own DuoV2 with no drive installed and, unlike every other ReadyNAS I have owned, it doesn't respond to it. While I did buy it used, I have no reason to believe that that's not simply the way it is designed. Only way to shut it down is pull the power. Unlike all others I know of, it also does not turn on when power goes out and is restored. Since the NV+ V2 is it's sibling, it may behave the same (not important to you, but others read the forum for help).
I thought this could be important because all NAS use a separate internal power (the only one on all the time) for the power circuit and NIC (so WoL works) and the problem could be the internal voltage converter/regulator. But I no longer think that's a factor.
That the USB recovery did seem to work indicates that most everything (probably all) CPU-wise is working. That it won't properly boot, get an IP address, and be seen by RAIDar even with no drives and at least show a diagnostic message there is puzzling, because the thing that usually causes that on healthy hardware is corrupt flash, which the USB recovery should have fixed.
Your LED pattern starts out looking like you are in the boot menu, but pushing the backup button should turn off all the LEDs except power, then cycle through the menu options. It still sounds like a corrupt flash, which makes me wonder just how much gets checked in USB recovery for it to be declared "successful" and trigger a shut-down. Then again, maybe there is something with the flash that makes it look like it was successful but does not survive a power cycle. I suppose it could be a RAM issue in an address range that USB recovery doesn't get to. But, unfortunately, the DuoV2 memory is soldered in.
Last ditch effort would be to try another power brick, but I'm really expecting that's not going to fix it.
Thank you to all who have helped me to diagnose my problem. This is a great forum where knowledgable people are helping each others without asking anything back. This is so rare these days. Kudos to you all.
I have opted to let my old trusted old war horse to greener pastures. I have saved the data from the drives with R-Linux ( Yes, learned also this from other forum postings :)
Thank you and Bye !
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
