I have the exact same problem as described here: https://community.netgear.com/t5/Using-your-ReadyNAS/ReadyNAS-NV-V2-ARM-stuck-in-Boot-Normal-Mode/td-p/1377994 After a clean power down, now my NV+ v2 refuses to boot, it automatically goes into the Boot Menu where I can only select "Normal" However, after choosing this option it won't actually boot or do anything else. This occurs without pressing the reset button to get into the boot menu, although the results are exactly the same if I do press the button. It happens with disks in the unit, with disks out of the unit, or with new disks in the unit. Power to the unit seems fine, all the expected lights are on, the fan spins, the displays are active. I am running Raidiator 5.3.12 or .13, not sure exactly which one, but I cannot access the unit to check. I have disks 1 and 2 as RAID-1, and disks 3 and 4 as a separate RAID-1. The disks appear to be ok, I can see the partitions, volumes and files in Linux when individually hooked up directly to a PC. (the beauty of RAID-1) In the linked discussion, the user was able to resolve the problem using a USB recovery key, but the URL to the recovery key file no longer works. I'd like to download and attempt a recovery using the key, if it is available. Thank you.

illmatic wrote: Thanks very much for your help but the unit does not respond to the USB recovery key. How many keys did you try? The ReadyNAS is a bit tempermental on this.

Have you extracted the data from the drives (while you had them mounted in the linux system)? If so, you might try zeroing one of the drives (or some other scratch drive). Vendor tools can do that (both Seatools and WDC's Lifeguard), and of course you can also use dd on the linux system. Then power down, put that zeroed drive in the NAS (with no other drives installed). Then power on the NAS and see if it does a factory install. You could also try booting the system into tech support mode, and see if that gives you an IP address. illmatic wrote: ...how would I view the serial console? Although this link is for an NVX, I think it also applies to the NV+ v2. https://gist.github.com/davewongillies/6481138 Hopefully someone from Netgear (or a v2 owner) will confirm.

illmatic wrote: I have taken a totally empty, unformatted disk -- I deleted all partitions and used a utility to wipe the entire disk -- and inserted it by itself into slot 1 and restarted the NAS. No change. That suggests that the issue is either the NAS chassis or the power adapter. illmatic wrote: How do you boot into tech support mode? If it is part of the boot menu, I cannot access that option. It is part of the boot menu (pages 24-25 here: http://www.downloads.netgear.com/files/GDC/RND2110/ReadyNAS_Duov2_NV+v2_HW_en_23-Mar-12.pdf

Serial console would let you know where it is getting stuck and let you use the u-boot console to check the u-boot environment is intact.

I managed to make a serial connection, after a lot of trial and error. In case someone else needs to do the same, I used a USB-to-TTL cable with 4 strands that I purchased on eBay, it shows up in Windows Device Manager as "Prolific USB-to-Serial Comm Port." Make sure you look at which COM port it assigns, you'll need this. On the READYNAS unit (again, lots of trial and error) from Right-to-Left, I hooked up black (ground), green, white, and left the red (power) wire unconnected. The serial connection setup is: 115200 baud, 8-bit data, parity: none, stop: 1 bit, flow control: none. You will need to set these parameters in both Device Manager and in Putty or TeraTerm. The ouput is at https://justpaste.it/5xhow There isn't any indication of a failure, it just goes into the Boot Menu without really explaining why. Any diagnostic help would be gretly appreciated.

requesting USB recovery for NV+ v2

16 Replies

Replies have been turned off for this discussion

illmatic
Guide
Sep 11, 2018
I will note that USB Recovery files are readily available for OS4 and OS6 but not for OS5:

https://kb.netgear.com/29952/How-do-I-use-the-USB-Recovery-Tool-on-my-ReadyNAS-OS-6-storage-system#Manual_creation_for_ARM_systems

https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool

https://kb.netgear.com/21400/RAIDiator-4-1-USB-Recovery-Tool

Would be great if NETGEAR Support could lend a hand to those of us in the middle, using ARM-based systems on OS5.
Marc_V
NETGEAR Employee Retired
Sep 11, 2018
Hi illmatic

Here is the link for the files.

Hope this helps!

Regards!
- illmatic
  Guide
  Sep 12, 2018
  Thanks for the recovery key files. Unfortunately I am not having success like the poster I referenced above. When I power up while holding the backup button, that button will flash continuously but nothing indicates that it is booting from the USB key. The LED is blank. I tried with a disk in slot 1 and without. I tried 2 different USB drives. I let the READYNAS unit run for a long time. The README is quite limited. The USB itself (after using the tool) has just 3 files on it. Any obvious things I might be doing wrong? Thank you.
  
  photo: https://s8.postimg.cc/guafqgrb9/readynasusb.jpg
  - Marc_V
    NETGEAR Employee Retired
    Sep 12, 2018
    Hi illmatic
    
    It could be incompatible USB keys, you may have to try a few more drives and it should be partitioned using MBR witha single FAT32 partition.
    
    Also, only 3 files is expected including the firmware image. The NAS should reboot/power off once the USB recovery procedure is successful.
    
    Regards
illmatic2
Tutor
Oct 30, 2018
I managed to make a serial connection, after a lot of trial and error.

In case someone else needs to do the same, I used a USB-to-TTL cable with 4 strands that I purchased on eBay, it shows up in Windows Device Manager as "Prolific USB-to-Serial Comm Port." Make sure you look at which COM port it assigns, you'll need this. On the READYNAS unit (again, lots of trial and error) from Right-to-Left, I hooked up black (ground), green, white, and left the red (power) wire unconnected.

The serial connection setup is: 115200 baud, 8-bit data, parity: none, stop: 1 bit, flow control: none. You will need to set these parameters in both Device Manager and in Putty or TeraTerm.

The ouput is at https://justpaste.it/5xhow There isn't any indication of a failure, it just goes into the Boot Menu without really explaining why.

Any diagnostic help would be gretly appreciated.
- mdgm
  Virtuoso
  Oct 31, 2018
  You could have a problem with your reset button. It could be stuck in or a problem inside the case leading to the system thinking the reset button is pressed when it's not.
  
  If you boot holding down the ESC key on a USB keyboard you should get into the u-boot console. From there you should be able to see if the u-boot environment is intact (but don't make any changes unless you know what you're doing).
  
  Have you tried doing USB Boot Recovery with the serial console connected?

Forum Discussion

requesting USB recovery for NV+ v2

16 Replies

Related Content

usb flash recovery 4.1.8.img

USB Recovery

USB Recovery

USB Recovery 4.2 Fails to start

Meldung "Debug: Telnet" nach USB Recovery...

NETGEAR Academy

ProSupport for Business