NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RND4000 volume scan/RAID sync every day
Hi,
I have the ReadyNAS NV+ RND4000, up to date with the latest firmware. It's been running flawlessly for about ten years albeit with only light use. It powers down overnight and there are man...
Thanks, I'd overlooked that option. This is what I'm getting repeated in fs_check.log:
***** File system check performed at Thu Oct 4 17:41:50 GMT 2018 ***** fsck 1.40.11 (17-June-2008) e2fsck 1.40.11 (17-June-2008) c was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information c: 134393/178307072 files (5.6% non-contiguous), 319068372/356589568 blocks
I note the "c was not cleanly unmounted, check forced." line! I'm slightly reassured that it's not something worse data-wise, but given that I'm not aware of any external reasons why there could be spontaneous outages, e.g., power cuts, it leads me to think that the ReadyNAS is fully rebooting itself. In other words, the volume scan is a symptom not the problem in itself.
If I then look in the system.log I can see this (filtered):
Oct 4 07:11:43 nas-01-B6-06 kernel: Boot type/reason: rtc/0/0 Oct 4 10:43:25 nas-01-B6-06 kernel: Boot type/reason: normal/2/0 Oct 4 19:39:41 nas-01-B6-06 kernel: Boot type/reason: normal/0/0
The first of these events was when it woke up in the morning, the second was when I forced a reboot and the third was spontaneous. Thus we can see there is something non-routine going on, but I'm not sure where to go from here. Frontview always shows reasonable operating temperatures and I haven't had issues with any of my other equipment on the same circuit having crashes etc..
Thanks for any advice offered!
Jeff
I guess there could be something going on with the power, but I'm thinking it's more likely to be a failing PSU or maybe a system board component.
Given the age of the NAS, replacing it might be the best option. You could replace the PSU with some effort, but of course we don't really know if that's the cause or not.
Yes I was beginning to think that a replacement might be the way to go...
Today I decided that cleaning up the ReadyNAS might help and it turned out to be full of dust. I vacuumed it all out and it looks good. However, now it won't start up! I'm going to try the battery reset procedure, but tomorrow as I don't have time now. Technology, eh?
OK so the tricky CMOS timer reset procedure hasn't made any difference.
I've had servers in the past that ran continuously for several years and then experienced some major hardware failure when rebooted, but this seems odd given that the ReadyNAS has been totally without power within the last couple of weeks anyway (when I switched off the circuit at the fuse box to do some electrical work). Am I missing some kind of other reset I could be doing? Maybe the battery itself is totally flat?
The battery only preserves the real time clock when the unit isn't connected to the main power. Otherwise it isn't used. the battery is clearly not related to your problem.
tupholme wrote:
I've had servers in the past that ran continuously for several years and then experienced some major hardware failure when rebooted, but this seems odd given that the ReadyNAS has been totally without power within the last couple of weeks anyway (when I switched off the circuit at the fuse box to do some electrical work).
There's not enough information to really figure out what's happening. But it seems pretty clear that your NAS is suddenly rebooting, with no crash information in the logs. It then detects the unclean shutdown, and is resyncing and checking the file system. On top of that we have the isolated temperature alarm during one of the resyncs - which is unexplained.
A brief interruption in the power circuit would of course result in an abrupt shutdown, and a failing supply could do this too. But a failing processor or failing memory could fail in a similar way.
If the NAS is connected to a UPS, you could try directly connecting it to the main power. If not, you could try moving it to a different circuit. You could also try running the memory test. If you haven't opened the case, you might do that, and clean out any dust that might be blocking airflow. If you moved the NAS when it was powered down, you might also check the memory seating.
Though it's a 10 year old NAS. So I think you should consider how much you are willing to invest in trying get it to run reliably.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
