NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS NV+ failed downloading logs
My long-running lightly used/loaded NV+ has been powered-down for 6+ months while I was away for the summer, and upon successful startup I first DL'ed a CONFIG file, and then I decided to download th...
To summarize, I discovered that while my ReadyNAS was not booting to completion, during the quotacheck and/or Check FS process it WAS talking on the network and accepting SSH logins. So while it still was "Booting..." and busy w/those I was able to log-on and to look-around var/log/ and var/log/frontview and var/log/frontview/backup and delete some large log files which amazingly solved the problem. Back to normal now w/no issues.
Thanks to StephenB and Sandshark for helping to assuage my anxiety through this process. Except that the NV+ normally just works day-in and day-out I'd be better at troubleshooting the thing!!!
:smileylol:
Thanks, but if they test-out OK, what would be next do you think?
I have read a number of threads here on "Booting..." and "logs full" and am disappointed simply downloading the system log could cause the RND4000 to lose its mind. I think mine is only half loaded so it's not a "disks too full" problem, not to mention that the thing has been completely powered-OFF for 7 months, before which it worked fine.
Indeen I'm inclined at this point to start-over from scratch if I can figure that out, since the last thing I did before powering-off last May was to make a backup.
tomupnorth wrote:
I think mine is only half loaded so it's not a "disks too full" problem,
To clarify this: The fullness of the data volume isn't relevant. The fullness of the OS partition is what matters. The OS partition on the NV+ is only 2GB, so it can fill pretty easily.
That said, at this point I have no idea whether that's the issue in this case or not.
tomupnorth wrote:
Thanks, but if they test-out OK, what would be next do you think?
Indeen I'm inclined at this point to start-over from scratch if I can figure that out, since the last thing I did before powering-off last May was to make a backup.
If the disks do check out ok, then starting over from scratch is reasonable.
After testing the disks, other options would be to
- try an OS reinstall. While that could resolve the issue, I don't think it is very likely to do that. Still, you could try it.
- boot up in tech support mode, and attempt to make a more complete diagnosis. Since you have a full backup, personally I'd just go with starting over. Somewhat painful, but certain.
StephenB wrote:
To clarify this: The fullness of the data volume isn't relevant. The fullness of the OS partition is what matters. The OS partition on the NV+ is only 2GB, so it can fill pretty easily.I've had this for 11+ years, replaced the PSU once, bought a replacement (spare) chassis, but the doggone thing runs mostly untouched by me (I use it for backups) so the rare problems throw me for a loop. And all the good support sites seem to be gone; if you have handy a link or notes on "starting from scratch" by all means post StephenB!
And did NOT know about the "OS partition" thing. Makes sense, thanks.
OMG I just tried plugging the drives into my spare chassis, having first looked in my records to see if I'd updated it to 4.1.16 (I had), and it behaved identically to the other one except in this case while it was starting its "quota check" I saw that it responded to ping. So I tried (again) to SSH into it and it worked!!!!!?!!!???!!! Scrambling for my old notes I managed, while it was continuing to quotachk, to goto /var/log and to frontview and backup dirs and delete some big logfiles. At least, I think 5 or 6 worth 80Mb each perhaps.
While doing this I saw the LCD come-up as normal and so I tried Frontview and another OMG, I was able to login. Logs show 5 sets of identical two-line messages:
"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."
Immediately followed by:
"RAID sync started on volume C."
So I'm logged-in right now and the Act LED is fast-flashing and presumably it's doing a RAID sync. In the meantime I see my files on the network!
Not sure what the magic sauce was here, unless it was my having deleted large files before the Quota check was done and the system tried to boot?
Anyway I'm letting it run and hopefully it completes the sync and the activity LED goes out.
Whew, it feels I may have dodged a bullet.
I think deleting those files was the secret sauce, and shows that an over-full OS partition was the problem. Once it's all done, you should probably go back in and see if there is anything else that you can delete. But more important is eliminating what caused it. Are you running any apps that might have created those log files (and perhaps more)? While the anitvirus in OS6 has been known to fill the OS partition, I know of no standard RAIDiator process that would.
Hi Sandshark, not running any special apps...I managed to run puTTY in SSH mode and forgot to check the "keep log" option before starting, so details are lost, but in looking now at my local_commands.log it seems I deleted these:
syslog
daemon.log
backup_002.log
backup_001.log
Less than 400Mb total I would say.
But I would also say now that I am going to have to set-up some reminders to not only download logs regularly, but also to make certain to Clear also, though iirc Clear All Logs doesn't actually clear ALL, so I will try to SSH in more regularly to look-see.
To anyone who might have the same problem and come-across this thread, the magic I believe was to catch the RN while it was doing the startup quotacheck, where it appears bash is running and you can sneak-in with SSH.
BTW as somewhat of an aside, I stumbled across the procedure for disassembling the NV+ to access the CMOS battery. My goodness you have to take the whole thing completely apart to pull the mainboard and access the battery! After 10 years that battery has to be dead! So I am going to replace the battery in my original chassis today, and then move the disks back and expect things will be normal. I expect the battery in my backup chassis to be dead as well, especially as it is not normally connected to power.
I have had odd problems with PCs when that battery dies; am surprised my NV+ even boots with a dead battery. Must do something or it wouldn't be in there, right?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
