Hi, Just did, what seemed to be, a successful update of my Ultra 6 from 4.2.31, to 6.10.0 (Hotfix 2). After completing the update (OS 6 seemed to be running just fine) i did a manual shutdown of the NAS to add all my drives (only had 1 drive in for the installation). When i added 3 drives back to the NAS it failed the boot process and is not stuck at "ReadyNas". I am not able to access the bootmenu, via Reset + Power. I suspect it has happened because the 3 drives i added was part of my original X-Raid aray from my 4.2.31 installation, and that this somehow corrupted the installation on the one drive i had installed (which was also part of the same aray). As i am not able to access the boot menu, i assumed that a USB restore is the only way. But it would seem that the USB 4.2 Recovery tool is so old that it can't run from Windows 10, and i got no older OS on hand - i understand that process here would be to use the old USB tool with a renamed img file of the latest 6.10.0. Anyone with some good ideas how to proceed here?

Realized i was missing MV C++ 2005 to run the Recovery tool. Created 5 different USB sticks now, all of different ages and within the size, fat32 etc. but can't get any of them to work with Backup + Power... bad luck with USB sticks or potentially another issues (considering i am not able to access the Boot Menu either)?

Sounds like probably a bad disk (or not properly inserted) not a problem with the internal flash.USB Boot Recovery shouldn’t be run unless reasonable steps are taken first to confirm the problem is likely with that as USB Boot Recovery does have a likely side effect.

Hi Grizzi， Can you try this link below? https://kb.netgear.com/29952/How-do-I-use-the-USB-Recovery-Tool-on-my-ReadyNAS-OS-6-storage-system

To add to this, i did replace the memory at about the same time as i did the update - yes this was likely a bad move as it could now be 2 or more issues. I did run a memory test for a few cycles with no issues, and did boot up in 4.2.31 for a few hours, and there were no issues. However, i did also have to take out the mobo do replace the memory, which ofc means disconnection the HD extension board, so hopefully i have not done some damage to this (i.e. some issues with the discs). I did test the disc i am using in my other computer (WD Reds), and there seems to be no issue. Also swapped it with another WD red, and get same problem. I also swapped memory back again the original, to test, but it didn't make a difference, so i am back to the new memory.

Hi, USB recovery for OS 6 would not work, as this is a legacy device. So based on what i am reading, if i need to do USB recovery, i need to use the 4.2 method, which i did get running, but it is not booting from the USB, which i bet it tied to the same issue with not being able to boot to the boot menu either.

Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win10

39 Replies

Replies have been turned off for this discussion

Grizzi
Aspirant
May 05, 2019
Realized i was missing MV C++ 2005 to run the Recovery tool. Created 5 different USB sticks now, all of different ages and within the size, fat32 etc. but can't get any of them to work with Backup + Power... bad luck with USB sticks or potentially another issues (considering i am not able to access the Boot Menu either)?
- mdgm
  Virtuoso
  May 05, 2019
  Sounds like probably a bad disk (or not properly inserted) not a problem with the internal flash.
  
  USB Boot Recovery shouldn’t be run unless reasonable steps are taken first to confirm the problem is likely with that as USB Boot Recovery does have a likely side effect.
  - Grizzi
    Aspirant
    May 05, 2019
    To add to this, i did replace the memory at about the same time as i did the update - yes this was likely a bad move as it could now be 2 or more issues.
    
    I did run a memory test for a few cycles with no issues, and did boot up in 4.2.31 for a few hours, and there were no issues.
    
    However, i did also have to take out the mobo do replace the memory, which ofc means disconnection the HD extension board, so hopefully i have not done some damage to this (i.e. some issues with the discs).
    
    I did test the disc i am using in my other computer (WD Reds), and there seems to be no issue. Also swapped it with another WD red, and get same problem.
    
    I also swapped memory back again the original, to test, but it didn't make a difference, so i am back to the new memory.
Icewaterhot
NETGEAR Employee Retired
May 05, 2019
Hi Grizzi，

Can you try this link below?

https://kb.netgear.com/29952/How-do-I-use-the-USB-Recovery-Tool-on-my-ReadyNAS-OS-6-storage-system
- Grizzi
  Aspirant
  May 05, 2019
  Hi,
  
  USB recovery for OS 6 would not work, as this is a legacy device. So based on what i am reading, if i need to do USB recovery, i need to use the 4.2 method, which i did get running, but it is not booting from the USB, which i bet it tied to the same issue with not being able to boot to the boot menu either.