NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Fried(?) ReadyNAS NV+ #19179228
I have a ReadyNAS NV+ (3x500GB) that has performed without problem for five years. Yesterday morning I left it unattended while copying a large file to the device from a WinXPPro machine. When I returned the file transfer had been interrupted midstream with a "xxx not available" error message, the NV+ had shut down, and the room smelled of something burning. The NV+ would not restart (surprise!) and, having to leave for a day, I simply disconnected it. This event was not preceded by any sort of warning message.
If I had to guess I would judge from the smell that there's an electrolytic capacitor in the power supply that went bad. So I have four questions. (1) Is there some quick way of verifying if my suspicion is correct, and of replacing the cap if that is what happened? (2) Given that the failure occurred in the middle of i/o activity, what are the chances that the drives are undamaged? (3) Assuming that the drives are undamaged, or that any errors induced by the device failure are recoverable, could I replace just the enclosure (assuming I can track one down) with some reasonable expectation that the data on the drives will show up intact when installed in a new enclosure? (4) If the answer to (3) is yes, should I have the same expectation if I replaced the enclosure with version 2; that is, do the old and new versions use identical (or sufficiently similar) protocols in formatting and communicating with the drives?
I guess I would also be interested in whether others have experienced a failure of this sort, though my primary concern is with recovering the data on the array. I should also add that it is not utterly critical, as much of it has been routinely backed up to an external usb/sata drive.
Any help anyone could offer would be appreciated. Thanks.
Ted
If I had to guess I would judge from the smell that there's an electrolytic capacitor in the power supply that went bad. So I have four questions. (1) Is there some quick way of verifying if my suspicion is correct, and of replacing the cap if that is what happened? (2) Given that the failure occurred in the middle of i/o activity, what are the chances that the drives are undamaged? (3) Assuming that the drives are undamaged, or that any errors induced by the device failure are recoverable, could I replace just the enclosure (assuming I can track one down) with some reasonable expectation that the data on the drives will show up intact when installed in a new enclosure? (4) If the answer to (3) is yes, should I have the same expectation if I replaced the enclosure with version 2; that is, do the old and new versions use identical (or sufficiently similar) protocols in formatting and communicating with the drives?
I guess I would also be interested in whether others have experienced a failure of this sort, though my primary concern is with recovering the data on the array. I should also add that it is not utterly critical, as much of it has been routinely backed up to an external usb/sata drive.
Any help anyone could offer would be appreciated. Thanks.
Ted
24 Replies
Replies have been turned off for this discussion
- I should add that the delayed automated replies to the email inquiries did not even assign a case number.
- If your NAS is registered you can open a case at my.netgear.com and you will get a case number.
- Thanks. I'll give it a try.
- Case number is 19179228,
- Update. After two days engaged in quota check the device disappeared from Raidar and appeared to halt at 7%, An attempt at shutdown eventually appeared to succeed, with the power switch and all drive and activity LEDs off, but the status display still lit. Having nothing else to do I pulled the plug, then reconnected the device and tried again. Again it started to boot, then proceeded to report "Resynching volume 2," then reported "Quota check," during which time it was again visible on Raidar and reporting the same volume and drive data as before (similar, maybe identical temperatures, same ATA error counts (6, 0, and 1)). This time it disappeared from Raidar and appeared to halt the quota check at 0.4% after less than 8 hours. Forced shutdown proceeded similarly: the machine went dark, except for the status display.
- I would suggest you power off the NAS while you wait for a response from support. Keep us updated here as well on the progress of your case.
- Thank you. Will do. Do you know, by the way, whether Raidar always reports real-time information form the device, or whether it is possible that it is reporting the last good information that the device had to report? If it is the former, then it certainly seems as though the drives in the array and the data are intact. Thanks again.
- To RTSwiss,
There was an earlier discussion re NV+ v1 Power supply here.
viewtopic.php?f=20&t=64431
The problem you have now, from your Aug 11th post, is that power went when data was been written to disks.
ATA errors are where disk commands are not complied with.
I would boot and select "Skip Volume check ". If unsuccessful, contact Tech support.
Remote access of SSH mode would need to be arranged.
Regards, Marto,
Netgear Tech support - I do have a case logged in at Tech Support but have thus far received only an acknowledgement two days ago and and notification 1 day ago that they will need more time. Since then nothing. When I originally restarted the device with a single bare drive, it booted normally, and before I shut it down I thought it advisable to authorize it to perform a volume scan on start up. Short of powering it down and rebooting it with a bare drive once again to reset that switch, can you think of any way to tell it to skip the volume check on boot? I should add that I would occasionally check the smart data on the drives, and to the best of my recollection the ATA errors reported for the 320ES are about (probably exactly) what the ATA error count was on that drive before the P/S failure. I do not think that either 630AS had reported any errors; it's at least conceivable that the ATA error now reported on one of the the 630ASs occurred when the P/S failed.
- Shut down; replaced array with a bare drive and rebooted with no problem; shut it down without checking boxes for volume scan or quota check on startup. Replaced array and restarted. Same result. Device is now once again engaged in a quota check; will not respond to web inquiry; will respond to ping; will respond to Raidar. The Raidar data seem fishy: it has been reporting, for the past several days, exactly unvarying values for fanspeed; device temperature; and each drive temperature (right down to the 45.5F/113.9C temperature for the device as a whole). These values did change when a single drive was installed, but with the array reinstalled the reported values are exactly what they were three days ago. If there is no change by morning I guess I will follow mdgm's advice, shut it down, and hope to hear from Tech Support in finite time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
