NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Duo v2 will not boot after firmware upgrade
My ReadyNAS Duo v2 (RND2000-200NAS) was working fine prior to the most recent firmware upgrade (5.3.13). I was able to back up files via rsync from PC and laptop. I could browse media files on the home network. The web interface was totally functional. Everything was working perfectly on firmware 5.3.12.
Then I received an email from NETGEAR stating that they found a security vulnerability in 5.3.12, and they recommended upgrading to 5.3.13. So I went into my web interface and navigated to the upgrade option. Sure enough, the ReadyNAS reported that a new firmware version (5.3.13) was found, and it proceeded to download and install it.
My Duo v2 never came back online after that. When it rebooted, the USB/Backup LED was flashing quickly. Every time I reboot, that's all that happens. The Backup LED comes on solid for one second, then starts flashing forever. In the meantime, the fan turns on and the drives spin up, but nothing more ever happens.
I read many NETGEAR KB articles online about USB recovery drives, and that's what NETGEAR Support recommended as well. NETGEAR Support unfortunately referred me (via a link in an email) to the USB recovery information for x86-based devices, where you run usbrecovery.exe and it creates the recovery drive. My Duo v2 is ARM-based, and the process for creating the USB recovery drive is manual (as far as I know - I haven't seen a similar usbrecovery.exe for ARM-based devices).
For the manual creation of the USB recovery drive, I found the files "uImage-recovery" and "initrd-recovery.gz" from a KB article, and I also copied a recent "uboot.bin" that was also referenced in the KB article. I then copied the 5.3.13 firmware to the drive. When I rebooted with the drive, I could see the USB drive being read in chunks. After the 3rd or 4th read (maybe 2 minutes into the process), the ReadyNAS would power down on its own. However, rebooting without the USB drive would yield the same blinking Backup LED.
I purchased a USB to TTL cable, and now I have the pleasure of viewing the serial console output and interacting with U-Boot. I can see that, when I have the USB recovery drive inserted, the ReadyNAS loads the kernel (uImage-recovery) and a ramdisk (initrd-recovery.gz). It then boots the kernel, and then it seems to flash the firmware, and finally it performs a clean shutdown.
However, when I boot without the USB drive inserted, it errors out fairly quickly. The USB device scan fails to find a storage device (which is correct, since I don't have it inserted), so the bootcmd (which is basically "usb start", "fatload kernel" (fails, no usb), "fatload ramdisk" (fails, no usb), "bootm 0x1200000 0x2000000". The final messages are "## Booting image at 01200000 ..." and "Bad Magic Number". Again, this makes sense, since I'm trying to boot without the USB drive. It's as if the firmware upgrade succeeded, but the bootcmd was never changed - so it's always trying to boot from the USB drive.
That's basically a summary of where I'm at right now. I cannot get the ReadyNAS to boot from anything other than the USB drive, and since the USB drive has a recovery kernel and recovery initrd on it, it just upgrades the firmware each time, and then restarts.
I would love to get my Duo v2 running properly again.
26 Replies
Replies have been turned off for this discussion
hello
if you want to do USB recovery for your DUO V2 device,please download the tools from below URL link
Hi Deniro,
Thank you for sending along the Duo V2 USB recovery tool. Even before I ran the tool, I took a look at the files associated with the Duo V2 within the archive. The uImage-recovery and initrd-recovery.gz files were both identical to the files that I already had on my USB drive.
Still, I decided to run the recovery tool. I re-formatted the drive and selected my device. Sure enough, the recovery tool copied the exact uImage-recovery and initrd-recovery.gz files that I already had. It then copied the 5.3.13 firmware file (RAIDiator-arm-5.3.13) that I already had on the drive. So, I believe I already had the correct files on my USB drive, after reading many other KB articles.
The recovery tool confirms that I had the correct files.
I will try booting with the USB drive once I'm back at my ReadyNAS device, but I can guarantee that it will do the same thing as before: It will boot from the USB drive, load the kernel, load the ramdisk, update the firmware, and shut down. I'll remove the USB drive and attempt to boot up again, and the boot will fail because it is always trying to boot from the USB drive.
I'll relay the results to you once I try the USB drive again, but since the recovery files are identical to before, I expect no change in results.
Is your backup button stuck pressed in? If the backup button is pressed in it'll always try to boot off USB every boot.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
