NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Duo won't boot after 4.1.9 upgrade- #19121497
My ReadNAS Duo V1 has been turned into a virtual boat anchor after doing a standard upgrade to OS 4.1.9. I can't see it on RAIDar 4.3.4, I can't access it on Windows Explorer (Windows 7-64) although I can ping it via a command prompt. Initially it crashed Windows Explorer which I had to apply a Microsoft hot fix to repair. Early in the fault finding process I removed one of the RAID 1 disks (disk 2). Some details are…
RAID 1 (2X 1 TB drives, 75% full), ReadyNAS Duo v1, Netgear RNDN 3700 router, Windows 7-64 home premium.
Upgrading from OS 4.1.8 to 4.1.9 after the OS upgrade I couldn't see the ReadyNAS using RAIDar so I upgraded to RAIDar 4.3.4, initially couldn't see the ReadyNAS using the new version of RAIDar either. Now I can only see the ReadyNAS on RAIDar for about 10-15 min after power on, then the device becomes unavailable to RAIDar and Windows Explorer. I have powered it off and on again multiple times each time the blue Power LED flashes for up to 15 min, with disk activity lights flashing, the blue Power LED lights solid for a short time before beginning to flash again for as long as I leave it on. The unit is unresponsive to powerdown via the power button and I have to pull out the power plug to powerdown. I have re flashed the OS using the usual procedure with the expected indicators as it boots up again and eventually settles to the same situation as I have described above.
I have reported the fault to Netgear telephone support, he told me that as the unit is not long out of warranty is not much they can do, in spite of the fact that I was doing what Netgear advise and upgraded my system to the latest version of the operating system. They referred me to e-mail support over a week ago and I have heard nothing more.
Netgear's qualified upgrade has crashed my network storage device, and many others according to this forum. I believe it is Netgear's responsibility to ensure that we get access to our data again and end up with functioning network storage devices.
Meantime can anyone please advise me the next step to making sure that I don't lose my data and have a functioning network storage device again?
Thanks in advance, Sean
RAID 1 (2X 1 TB drives, 75% full), ReadyNAS Duo v1, Netgear RNDN 3700 router, Windows 7-64 home premium.
Upgrading from OS 4.1.8 to 4.1.9 after the OS upgrade I couldn't see the ReadyNAS using RAIDar so I upgraded to RAIDar 4.3.4, initially couldn't see the ReadyNAS using the new version of RAIDar either. Now I can only see the ReadyNAS on RAIDar for about 10-15 min after power on, then the device becomes unavailable to RAIDar and Windows Explorer. I have powered it off and on again multiple times each time the blue Power LED flashes for up to 15 min, with disk activity lights flashing, the blue Power LED lights solid for a short time before beginning to flash again for as long as I leave it on. The unit is unresponsive to powerdown via the power button and I have to pull out the power plug to powerdown. I have re flashed the OS using the usual procedure with the expected indicators as it boots up again and eventually settles to the same situation as I have described above.
I have reported the fault to Netgear telephone support, he told me that as the unit is not long out of warranty is not much they can do, in spite of the fact that I was doing what Netgear advise and upgraded my system to the latest version of the operating system. They referred me to e-mail support over a week ago and I have heard nothing more.
Netgear's qualified upgrade has crashed my network storage device, and many others according to this forum. I believe it is Netgear's responsibility to ensure that we get access to our data again and end up with functioning network storage devices.
Meantime can anyone please advise me the next step to making sure that I don't lose my data and have a functioning network storage device again?
Thanks in advance, Sean
25 Replies
Replies have been turned off for this discussion
- NetGear tech support
- What is the typical response time from Support. It's been 36 hours since I logged the call and I haven't heard anything. Is this expected?
- Same issue here-- after auto-upgrade to 4.1.9, NFS mounts are read-only. Will downgrade fix the problem?
- How is NFS mounts read-only the same as the NAS not booting?
You could try downgrading to 4.1.8 or updating to 4.1.10 beta. You may then need to reset the ownership and permission on the share via the Advanced Options tab. - Hi cbreving
You can post the digit code in your support ticket case - I am having no luck with Netgear Support on my case # 19205239.
It has been 3 1/2 days with no reply to my four messages.
Today I called support and they said they can't contact the engineer. They said send him another message. Hoping someone gets back to me soon. - Remote host still unreachable.
Whether the WAN ip was changed? Or the system was powered off?
You also can install the teamviewer, then post the ID#/password in case#19205239. Then we can remote access your pc. - Same problem here. I will not update my other Duo until this is resolved. Details:
Issue with Firmware update for:
ReadyNAS Duo RND2000-200WWB serial # 24M3037701D1A
This chassis was replaced on March 21, 2012 under warranty on RMA # 1086906
I opened a new topic with this subject: Firmware upgrade fail #19255699
Edited this original message to avoid double posting. - Hi RNASguy
Please boot your device to telnet mode and forward the port 23 for us. Then post the wan ip in case#19255699. You also can have a phone to netgear call centre. machv wrote: I'm just off on holiday for the next 4 days so I'll set this up on my return. If there is some more detailed instruction as to how to set up port forwarding to you I would be grateful.
As of this morning my Nas is now booting up normally and back on my home network.
The L3 Tech support says that when he Telnetted into the NAS, he could see that disk 1 had failed, so asked me to remove it and reboot it back into telnet mode. After I did that he said nothing else was wrong so I could boot it up normally.
I'm glad it's back and (with a new drive soon to be on order) I can get it back to being our NAS RAID back up array but what I still don't get is:
why didn't I get an email notification of the drive failure?
why didn't the NAS join the network in this state?
is it just coincidence that after 4.1.9 the drive failed?
I asked these questions of the L3 support and he couldn't answer them.
So it's a mixture of "yay!" and *concern* this morning. I've got less faith in the stability of the product, now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
