RN104 stuck on "Boot from USB" after upgrade to 6.4.2

[Sigbjorn]

In february I upgraded from 6.4.1 to 6.4.2 using the web interface. 

Everything appeared to go as normal until the restart after upgrading. 

Everytime I connect power to the RN104 I get "Boot from USB   Failed!"

I attempted to get to the boot menu to maybe get read-only mode to copy the files but even if I start with the SYS button pressed I just get the same. "Boot from USB Failed!"

I attempted to use a USB Recovery and I get the following:

On some USB memory sticks I go straight to "Boot from USB Failed" (I read that some memory sticks are not compatible so I assume this is normal)

On some USB memory sticks I get "Boot from USB" - "Booting.." - "ReadyNAS  USB Recovery" and power of after approximately 30 seconds.  (I assume this means the recovery should have worked, or should it be longer?) 

After power button is pressed the same repeats  "Boot from USB Failed!"

I tried using 6.4.1  or 6.5.0  instead of 6.4.2 on the USB Recovery, but the results were always identical.

The result is the same if I try with disk in the RN104 or if I try without any disks.

All files have been backed up using a Linux PC and the instructions given on this community so I know the disks are ok.

Is there anything more I can try in order to get the RN104 running again or must I dump it and buy a new NAS?

I tried looking at the log files to see if I saw anything. the last log file i found was   /var/log/readynasd/fwbroker.log which ended like this :

Feb 28 2016 17:19:07 INFO:PROGRESS: PENDING: progress=99
Feb 28 2016 17:19:12 INFO: request method POST
Feb 28 2016 17:19:12 INFO: dpv_=dpv_1456676094000, njl_id_=njl_id_2289, type=FirmwareProgress
Feb 28 2016 17:19:12 INFO:PROGRESS: PENDING: progress=99
Feb 28 2016 17:19:17 INFO: request method POST
Feb 28 2016 17:19:17 INFO: dpv_=dpv_1456676094000, njl_id_=njl_id_2291, type=FirmwareProgress
Feb 28 2016 17:19:17 INFO:PROGRESS: PENDING: progress=99
Feb 28 2016 17:19:21 INFO:START_DOWNLOAD_DEMON: complete=60002304
Feb 28 2016 17:19:21 INFO:START_DOWNLOAD_DEMON: write firmware file to the disk bytes=60002304
Feb 28 2016 17:19:21 INFO:START_DOWNLOAD_DEMON: Checking file for md5...
Feb 28 2016 17:19:22 INFO:CHECK_MD5_SUM: local=ed5a86f8aa782e6a1ab8823c922ef479 remote=ed5a86f8aa782e6a1ab8823c922ef479
Feb 28 2016 17:19:22 INFO:CHECK_MD5_SUM: MD5 OK! Create link in /etc/.flash_update -> .flash_update_file
Feb 28 2016 17:19:22 INFO:retrieve update information: version=6.4.2, size=60002304, descr=ReadyNASOS Update, url=http://kb.netgear.com/app/answers/detail/a_id/30263
Feb 28 2016 17:19:22 INFO: GETFW: READY, REBOOT IN TIMEOUT
Feb 28 2016 17:19:22 INFO: request method POST
Feb 28 2016 17:19:22 INFO: dpv_=dpv_1456676094000, njl_id_=njl_id_2293, type=FirmwareProgress
Feb 28 2016 17:19:22 INFO:retrieve update information: version=6.4.2, size=60002304, descr=ReadyNASOS Update, url=http://kb.netgear.com/app/answers/detail/a_id/30263
Feb 28 2016 17:19:22 INFO:PROGRESS: SUCCESS

[JennC]

Hello Sigbjorn,

It is best to contact support center for this concern.

Regards,

[FireChief]

I have the SAME problem!
Just saying "contact suport" doesn't work, I realy need a fix for this now that doesn't mean sending it away.

PS: Tried support but my NAS is 11 months old so it seems I have to pay???

[StephenB]

---

@FireChief wrote:

I have the SAME problem!

---

And USB recovery failed for you also?  

---

@FireChief wrote:

 I realy need a fix for this now that doesn't mean sending it away.

---

Well, that might not be possible.  Support is likely the fastest way to tell, and they do a lot of work remotely.

---

@FireChief wrote:

PS: Tried support but my NAS is 11 months old so it seems I have to pay???

---

Software support is limited to 3 months from purchase, so you probably will need to pay.  They do have per-incident support available.

[FireChief]

Yes USB recovery failed... it boots to USB, does it's thing and shuts down like it is meant to but when powered

up again I still get failed to boot from USB.

Tell me what the reasoning is behind charging your valued customers to get something fixed that was caused by an update? Something that
has rendered this device completely useless?

[StephenB]

---

@FireChief wrote:

Tell me what the reasoning is behind charging your valued customers to get something fixed that was caused by an update? Something that
has rendered this device completely useless?

---

I agree that is hard to swallow.  It's possible that they won't charge if you complain enough (being very clear this is caused by an update).  

You seem to think I work for Netgear.  I don't - I am just a user who happens to be a mod.

[bbani]

I have the same exact problem, after updating the firmware using the Web interface. 

It reboots to "Boot from USB" and then "Boot from USB failed" if i fail to insert a recovery USB. 

Even if i put in the recovery USB, it goes to "Booting..." and then "ReadyNAS USB Recovery" and then powers down after a few minutes. Removing the USB, and power on the unit, results again in "Boot from USB". 

I've tried different firmware versions, from 6.4.1 to 6.4.2 to 6.5.1. Same results. 

Need Hardware RMA. 

[BrianL2]

Hi bbani,

I have responded to the similar thread that you've started. As posted, try other USB flash drives or contact our support team.

Kind regards,

BrianL
NETGEAR Community Team

[bbani]

The solution is to contact Support and beg and plead that it is a hardware failure due to faulty Netgear firmware update. Then find your receipt and qualify for an RMA to return the unit and get a replacement. Don't waste valuable hours playing with it like i did thinking you can troubleshoot it back to health. 

Best regards.

[BrianL2]

Hi bbani,

I've responded to the other thread. Let's be hopeful that the upgrade process (try the manual update) will be a success on the replacement unit.

Kind regards,

BrianL
NETGEAR Community Team

[JennC]

Hi bbani,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. 
If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” so others can be confident in benefiting from the solution. 
 
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
 
Regards,

[bbani]

Netgear accepted this hardware failure as an RMA due to the failure of a netgear supplied firmware that bricked the system. 

New hardware arrived next business day, drives booted up fine, and the unit is working now. Old unit was sent back. 

Thank you. 

[JennC]

Hi bbani,

Thank you for getting back. If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” so others can be confident in benefiting from the solution. 
 
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
 
Regards,