Forum Discussion

Guide

Dec 20, 2021

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 the logs and it hung-up i.e. I lost FrontView and it stopped responding, including no response to the POWER button.

I unplugged the machine and re-plugged, and after it spent some couple hours doing a Quota check, it was again unresponsive. I unplugged/replugged a third time and it said "Booting..." and the Activity LED blinked for a long while, but after letting it go overnight I found it again this morning sitting at Booting...

There's another thread here where this problem arose attempting to download logs, but the resolution wasn't given. I tried booting w/o discs and got ERR: NO DISKS so I don't think it's a hardware problem. But a last attempt to boot w/o a volume check gave me a short blink of Disk 4, then "Booting... Drive 4 sync" and a lot of ACT LED activity (a few hours), and now it sits again with that display still in the window and the blue POWER LED pulsing quickly. I can't SSH in because it apparently hasn't booted to where it's talking on the network, despite that it responds to pings.

Any thoughts on how to proceed would be most welcome.

tomupnorth
Dec 28, 2021
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:

16 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Dec 21, 2021
I'd test the disks next (I do that in a Windows PC, using vendor tools - Seatools for Seagate, and either Lifeguard or Dashboard for WDC). Label by slot as you remove them, so you can restore them to the proper spot.
- tomupnorth
  Guide
  Dec 22, 2021
  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.
  - StephenB
    Guru - Experienced User
    Dec 22, 2021
    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.