I've got a ReadyNAS NV+ that I've had for about ten years. It's done what I've wanted to and been fairly dependable, except for power supplies.
I got two replaced by Infrant under warranty, but recently had to replace it again. This time I had to buy one as evidently, Infrant doesn't have any more. The supply I got was from a listing on this site. It plugged in and fired up smartly. One of the things I did notice when replacing the supply is the rated output is twice what the old one was. Anyway, I have no idea if this has any affect on the current issue, but you never know.
The NAS is locking up randomly. The lights are on, but no activity. No drive access, no web access, no admin page access and no response to a long power button press.
Is there any way to figure out why this is occuring? I've looked at the logs, but there is nothing there.
This time I had to buy one as evidently, Infrant doesn't have any more
Infrant hasn't existed for 10 years - you mean Netgear. Your NAS has been out of production a long time, so they are no longer replacing PSUs in units identified in the old service action.
System log messages to give an indication of the activity, 8 times in the last 2+ months:
Sun Dec 17 06:22:14 EST 2017 Backup finished. [Job 001] Sat Dec 16 19:46:25 EST 2017 Fan will be recalibrated over the next few minutes. Sat Dec 16 15:57:54 EST 2017 System is up. Sat Dec 16 15:49:31 EST 2017 Volume scan found no errors. Sat Dec 16 14:38:18 EST 2017 Rebooting device... Sat Dec 16 14:38:17 EST 2017 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Sat Dec 16 14:32:28 EST 2017 System is up. Sat Dec 16 14:22:44 EST 2017 RAID sync started on volume C. Sat Dec 16 14:21:21 EST 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Mon Dec 11 00:33:01 EST 2017 Backup finished. [Job 003] Sun Dec 10 00:12:50 EST 2017 Backup finished. [Job 001] Fri Dec 8 00:06:23 EST 2017 Backup finished. [Job 005] Thu Dec 7 00:06:36 EST 2017 Backup finished. [Job 007] Wed Dec 6 00:31:29 EST 2017 Backup finished. [Job 006] Tue Dec 5 00:29:56 EST 2017 Backup finished. [Job 004] Mon Dec 4 00:05:53 EST 2017 Backup finished. [Job 003] Sun Dec 3 00:12:46 EST 2017 Backup finished. [Job 001] Fri Dec 1 00:06:24 EST 2017 Backup finished. [Job 005] Thu Nov 30 00:06:36 EST 2017 Backup finished. [Job 007] Wed Nov 29 00:30:50 EST 2017 Backup finished. [Job 006] Tue Nov 28 05:21:26 EST 2017 Backup finished. [Job 004] Mon Nov 27 00:05:57 EST 2017 Backup finished. [Job 003] Sun Nov 26 03:21:41 EST 2017 Backup finished. [Job 001] Fri Nov 24 01:49:24 EST 2017 Backup finished. [Job 005] Thu Nov 23 00:38:23 EST 2017 Backup finished. [Job 007] Wed Nov 22 11:29:01 EST 2017 Backup finished. [Job 006] Mon Nov 20 09:18:57 EST 2017 Backup started. [Job 004] Mon Nov 20 00:05:56 EST 2017 Backup finished. [Job 003] Sun Nov 19 06:16:11 EST 2017 Backup finished. [Job 001] Fri Nov 17 00:06:22 EST 2017 Backup finished. [Job 005] Thu Nov 16 20:29:12 EST 2017 System is up. Thu Nov 16 20:20:51 EST 2017 Volume scan found no errors. Thu Nov 16 19:13:01 EST 2017 Rebooting device... Thu Nov 16 19:13:00 EST 2017 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Thu Nov 16 18:28:02 EST 2017 System is up. Thu Nov 16 18:18:44 EST 2017 RAID sync started on volume C. Thu Nov 16 18:17:30 EST 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Mon Nov 13 00:33:18 EST 2017 Backup finished. [Job 003] Sun Nov 12 00:12:49 EST 2017 Backup finished. [Job 001] Fri Nov 10 00:06:26 EST 2017 Backup finished. [Job 005] Thu Nov 9 00:06:37 EST 2017 Backup finished. [Job 007] Wed Nov 8 00:07:49 EST 2017 Backup finished. [Job 006] Tue Nov 7 03:39:59 EST 2017 Backup finished. [Job 004] Mon Nov 6 00:05:53 EST 2017 Backup finished. [Job 003] Sun Nov 5 00:12:49 EDT 2017 Backup finished. [Job 001] Fri Nov 3 00:06:24 EDT 2017 Backup finished. [Job 005] Thu Nov 2 00:06:35 EDT 2017 Backup finished. [Job 007] Tue Oct 31 21:13:50 EDT 2017 RAID sync finished on volume C. The volume is now fully redundant. Tue Oct 31 20:30:10 EDT 2017 System is up. Tue Oct 31 20:20:50 EDT 2017 RAID sync started on volume C. Tue Oct 31 20:20:37 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Tue Oct 31 20:12:49 EDT 2017 System is up. Tue Oct 31 20:03:22 EDT 2017 RAID sync started on volume C. Tue Oct 31 20:03:07 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Mon Oct 30 17:15:19 EDT 2017 System is up. Mon Oct 30 17:06:00 EDT 2017 RAID sync started on volume C. Mon Oct 30 17:04:57 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Mon Oct 30 00:06:01 EDT 2017 Backup finished. [Job 003] Sun Oct 29 00:12:46 EDT 2017 Backup finished. [Job 001] Fri Oct 27 01:50:29 EDT 2017 Backup finished. [Job 005] Thu Oct 26 00:06:36 EDT 2017 Backup finished. [Job 007] Wed Oct 25 18:31:29 EDT 2017 Backup finished. [Job 006] Wed Oct 25 08:14:26 EDT 2017 Backup finished. [Job 004] Mon Oct 23 00:05:54 EDT 2017 Backup finished. [Job 003] Sun Oct 22 06:14:22 EDT 2017 Backup finished. [Job 001] Fri Oct 20 10:34:40 EDT 2017 System is up. Fri Oct 20 10:25:33 EDT 2017 RAID sync started on volume C. Fri Oct 20 10:25:19 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Fri Oct 20 08:52:35 EDT 2017 System is up. Fri Oct 20 08:43:25 EDT 2017 RAID sync started on volume C. Fri Oct 20 08:42:27 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Fri Oct 20 00:06:26 EDT 2017 Backup finished. [Job 005] Thu Oct 19 00:38:21 EDT 2017 Backup finished. [Job 007] Wed Oct 18 00:44:10 EDT 2017 Backup finished. [Job 006] Tue Oct 17 19:09:26 EDT 2017 RAID sync finished on volume C. The volume is now fully redundant. Tue Oct 17 17:49:29 EDT 2017 System is up. Tue Oct 17 17:40:23 EDT 2017 RAID sync started on volume C. Tue Oct 17 17:39:17 EDT 2017 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Mon Oct 16 00:32:52 EDT 2017 Backup finished. [Job 003] Sun Oct 15 00:12:49 EDT 2017 Backup finished. [Job 001] Fri Oct 13 00:06:25 EDT 2017 Backup finished. [Job 005] Thu Oct 12 00:06:39 EDT 2017 Backup finished. [Job 007] Wed Oct 11 00:32:35 EDT 2017 Backup finished. [Job 006] Tue Oct 10 00:28:48 EDT 2017 Backup finished. [Job 004]
Are you seeing anything more interesting in the system log (and kernel.log) in the zip file? There might be some clues on where it went non-responsive, and what was going on around that time.
Sorry to disappear. The problem waned, and then reoccured. I've looked through the logs, but there is a plethora of stuff there, and frankly nothing jumped out at me.
I had the issue reoccur about an hour before leaving on an extended trip and just disconnected power to the box.
Since returning, it hasn't exactly been a good boy. I've had to restart twice and the last time it's syncing, but doesn't seem to be completeting the sync.
I'm pretty certain I have the whole thing backed up thank goodness, as it's looking like another NAS box is in my future.
And while the ReadyNAS has overall been a success, just the fact that it regularly eats power supplies is a strong motivation to seek a replacement from another vendor or perhaps a homebrew. I'm on PS #3 and they are no longer readily available, thanks Netgear, so some DIY is involved now in replacement due to the non-standard conntection details, again thanks Netgear.
And while the ReadyNAS has overall been a success, just the fact that it regularly eats power supplies is a strong motivation to seek a replacement from another vendor or perhaps a homebrew.
Your NAS hardware design goes back to ~2007, current ReadyNAS don't use the non-standard pinouts. Several of the smaller desktop models use power bricks that are easily replaced.
Well, that's not particularly helpful to the problem at hand.
To be honest, for 5-6 years after I bought the unit, support was exemplary. One of the PSU's was replaced outside of the 5 year warranty.
I wasn't expecting to get another one for free, but since this is/was a widely recognized problem, it would have been really helpful if there would have been some sort of "official" guidance from Netgear as to a proper replacement and modification procedure for the PSU. When the first two PSU's died, there were components that were visibly damaged (smiked). The third one had no such evidence.
Support wise, things all kinda went south about the same time that the old forum was deprecated. There were a lot of folks from corporate on the old forum that provided a lot of really good support. And then it went poof. Gone into the ether. Not just disabled, but deleted. I'm guessing the suits got involved. The new forum is, in my mind, significantly harder to navigate and find useful information.
Unfortunate.
In any event, I now have a storage unit that randomly locks up without any sort of indication why. So, I'm in the market for another one as there has been no assistance here whatsoever to try and resolve the problem. I'm not convinced that it doesn't have something to do with the PSU installed at the last failure. Although marketed as a replacement, there were some fundamental differenences with the OEM one.
This is probably the date the file was uploaded to our server.
It's not practical for us to keep on producing replacement parts indefinitely. This model was replaced in our product lineup way back in November 2011.
You can rewire a standard PSU but it may not fit in the case.
Improvements were made to the PSU design over time and in light of problems identified that could lead to premature failure in the batch of units covered by the Service Action.
Failures at this point, over 10 years after that batch was produced could hardly be considered premature.
PSUs are one of those components that can and do fail at any time in any PC.
If you manage a large number of PCs: after the disks, the PSU would be one of the next most likely components to fail.
The old posts haven't been deleted, but rather some old posts that haven't been viewed in a long, long time have been archived. I can still retrieve any information that was on the old forum as needed.
It just shut itself off while attempting to delete the file in question.
Were you using ssh?
There could be some filesystem corruption. I suggest backing up the NAS - other than the problem file(s) - and then do a factory reset, rebuild the NAS and restore the files from the backup.
Have you looked at the disk health (disk_smart.log)?
You can send in your logs if you like. It does sound like a hardware issue of some kind (It could be the PSU you installed as you suspect but it could be something else) which is not at all surprising when you consider the age of the unit.
StephenB did ask back in December if there was anything of interest in the logs and seeing you didn't respond to that for a long time we assumed that there was no further response needed.
Seeking help on the community is very much driven by your own desire to pursue a resolution.
If your unit's about 10 years old (probably more like 11 years now if you bought an Infrant branded unit) then it's probably been out of warranty for most of that time (the warranty was originally 1 year for NV+ v1 systems).
We discontinued the NV+ (v1) several years ago now back in 2011 and still did firmware updates for quite some time after that with security fixes. It's beyond the security maintenance period now.
Engineering's focus is on what they can change which is improvements to the ReadyNAS OS 6 firmware. It's been nearly 5 years since we introduced our first products that shipped with ReadyNAS OS 6.
I don't think any manufacturer is going to be able to do a lot with troubleshooting a possible hardware issue after 10+ years for a product that had a 1 year warranty.
Now you could find the replacement you've bought last well for you or you could not. Your NV+ unit has lasted very well. Over 10 years is a good run.
We now have a 5 year limited hardware warranty on our Business products.
