After firmware upgrade, ReadyNAS NV+ won't boot #19086813

[ImperfectTommy]

I got a notification for a new firmware upgrade from my ReadyNAS NV+. I rebooted the machine, the firmware installed, and now the NAS gets stuck with the LED stating "Booting...". I tried to re-install the firmware and to reset to factory defaults with no effect. I would be grateful for additional suggestions. I miss having a NAS.

Thank you!

[mdgm]

Please power down, disconnect power for a few minutes or so, reconnect power and attempt to power on the NAS.

If it still won't work open a tech support case at my.NetGear.com and post the case number

[merlin-vienna]

I had the same problem. Power down didn´t help. Opened Case #: 19030084

[ImperfectTommy]

Tech support case # 19086813

[garyr]

Tech support case # 19109311

[makingsa]

I have exactly the same issue.

Case number : # 19225250 raised.

[socks]

Same issue.

#19259638

[badjaeb]

Whats the latest on this issue? Not sure if I should upgrade? I was just about to upgrade firmware to v4.1.9 as am having access issues now that we moved to Win S2008 Domain. Release notes indicate v4.1.9 has "Updated CIFS service, better functionality with Windows 2008R2 domains."

[mdgm]

Skip 4.1.9 and go to 4.1.10 beta: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222

I didn't have the problem of my system not booting when updating to 4.1.9 so I'd suspect it might be a coincidental issue that users are facing.

What version of RAIDiator are you currently running badjaeb?

[badjaeb]

Currently at RAIDiator 4.1.8 . How fresh is this beta? Will give it a try at your recommendation. Am using an alternate backup destination for now but this NAS is one of our backup destinations and I would like to resolve the issue and get it back in service. Wanted to get it updated to eliminate this as possible cause form my issue.

Having access problems to NAS with windows explorer since upgrade to Windows 7 and S2008. Was hopping the upgrade would resolve the issue due to comment in 4.1.9 release notes. May also be due to some new OS security settings. Have already turned off GP settings "Microsoft network client: Digitally sign communications (always)and (if server agrees) Enable to Disable as was told this had resolved the same access issue at another site.

[badjaeb]

Should have followed and checked out the link before asking the beta question mdgm. Still going to give the beta a try to see if resolves my issue and will post results. Won't use as a backup destination till an official firmware release of 4.1.10 though.

[badjaeb]

No reboot issues upgrading to 4.1.10-T3 It resolved the access issue from a domain workstation but still can not access it from the DC server.

[garyaj]

Looks like this issue isn't going away soon. My tech support case number is: 19499909.

[NickHark]

I have the same problem.

Here's the reply I got from online submission:

This is Sheena from NETGEAR 2nd Level Technical Support.

Since the Support Warranty for the NETGEAR ReadyNAS RND4000 has been expired, you have an option of purchasing a contract to get phone support. For only $299 contract, you can get the following:

1. Extended Hardware Warranty up to September 24, 2015 on both Chassis, HDDs (if bundle with the NAS), and Power Supply instead of having the Hardware Warranty up to January 12, 2014 only
2. Extended 3 Years Support Warranty (24 x 7 Phone Support)
3. Next Business Day Replacement on both Chassis, HDDs (if bundle with the NAS), and Power Supply

If ever you will consider this contract, please send me an e-mail so that I can call you back to process this and assist you with the issue.

Sincerely,

Odd, I thought they would attempt to help me fix their problem.

I tried reinstalling the FW with the same result.

I'll probably research reinstalling the last stable version from a thumbdrive?

[OOM-9]

Lets try to keep the case # posts down. Having one case number per thread will help prevent any confusion when reading through the threads.

In the meantime, you can work with the support agent or try the usb boot, to see if you are able to recover the flash:
http://www.readynas.com/kb/faq/boot/how ... ash_device

@NickHark - PM inbound to see what is going on with that support (or lack there of)