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
- First, If you configue the correct "Alert", the logs would send to you. You also can check the disk status in page "status"-"Health".
The second, bad disk will caused the system boot failed. System will check all disks when booting.
The last, It is no related with firmware 4.1.9. You can check the disk with disk vendor's tool. No firmware can caused fine disk to bad disk physical. - Hi Rabbie
It's reassuring that the firmware shouldn't be the issue. :) However something is not right with 4.1.9 as this thread is demonstrating.
I have configured the alerts when I first got my Duo. I have received disk warnings in the past as well as power shutdown notifications, etc. - I didn't receive any of these while this disk was failing. I also checked the logs and that said nothing about a failing disk. I think I even bypassed the disk check when trying to figure out what was wrong (hold down power for 5 seconds, until the disc lights flashed once) and the NAS still failed to mount. - Disks can and do fail at any time and unfortunately SMART doesn't always detect problems before a disk fails. It's one of many reasons that backups are important. The NAS would have failed to boot either because it hung because of the bad disk or simply because with a bad disk installed a boot process would be risky.
When you've just put the NAS in telnet mode if you have RAIDar open and refresh it regularly and hover the mouse over the disk LEDs you can see the ATA error count on disks and get an indication if one has failed. As in telnet mode the NAS doesn't boot off the disks it usually (but not always) doesn't hang in this mode when a bad disk installed. mdgm wrote:
When you've just put the NAS in telnetmode if you have RAIDar open and refresh it regularly and hover the mouse over the disk LEDs you can see the ATA error count on disks and get an indication if one has failed.
Ah, now there's a good tip. Thank you. :)
I'm off to talk to Seagate now to get them to replace this faulty disk (as it's in it's three year warranty).- I have the same problem after update to 4.1.10. What do I do ?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
