ReadyNAS 314 - root volume 99.67% full - cannot connect

Question

My ReadyNAS 314 recently stopped booting at 86%. I performed a disk test through the boot menu. Now it boots but I cannot connect to it via the web interface nor via SSH. RAIDar shows the system as healthy. I did a firmware reset, but nothing changed. I restarted in support mode, but still SSH keeps getting `connection refused`. When I try to access the webiste, I get a 404 fir the /admin page.

Sandshark · Answer

When the root volume gets too full, some configuration files can get corrupted and temporary files cannot be created. The system was probably warning you for a while that this was happening, and you shouldn't have ignored it if it was. There are a couple things that can fill it rapidly, though.

Do not attempt an OS-reinstall or USB recovery. They will just make it worse.

If you are comfortable with the Linux command line, you can go in and find and delete what has filled the OS partition using the support mode boot option. You'll also want to figure out what caused it and fix that, since it will likely just happen again. Plex is one notorious thing that can cause this, BTW. You can find multiple posts on that on the forum. Just don't rely on the internal search engine, as it's abominable. Search using Google.

If you are not comfortable with that, then Netgear paid support is your best bet.

Enlil · Answer

Thanks for your response, Sandshark!I'm pretty certain that I know what process filled up the drive. I cleaned up previously and thought I had disabled it, but must have gotten that wrong.My biggest issue right now is how I get cli access to the system. As I said in three original post, SSH gets refused and the admin page gives me a 404

Sandshark · Answer

So, did you do a search for the answer as I suggested?

You have to go into tech support mode via the boot menu and then you can telnet into the NAS. The user name is root, the password is infr8ntdebug.

At that point, you are in a very stripped down version of the OS. You first need to mount the OS partition.

# start_raids
# btrfs device scan
# btrfs fi show
# mount /dev/md0 /mnt

From there, the steps you took to free space via SSH should work. If configuration files have been corrupted, that may not fully fix the problem, though.

JBDragon1 · Answer

You know, I've found using the program WinSCP, you can access your NAS filesystem like you would your Windows Directory and so it's easier then SSH into the drive and manually going around looking for files.&nbsp; But you can easily delete something you shouldn't.&nbsp; So you have to be careful.&nbsp; I kind of mangled by 516.&nbsp; I've done it before and semi fixed it.&nbsp;&nbsp;&nbsp;This is one of the biggest issues.&nbsp; You can have 30TB of storage, but you are limited to 4GB of storage for the system that you are SSH into.&nbsp; You can easily fill it up, and/or screw it up if you don't know what you are doing. Including not being able to log into your NAS!!!!&nbsp; Are you trying to install a bunch of apps?&nbsp; I was going this route for Sonarr,Radarr, and nzbget.&nbsp; it eats up space.&nbsp; If you don't config things right, then their config files and other data could eat up that small 4GB area.&nbsp; It's smaller that that of course with the system files.&nbsp; So really around 2.5GB or so. free.&nbsp;I then was told about DOCKER.&nbsp; &nbsp;So Docker CLI should be one of the apps you can install.&nbsp; What this allows is installing these apps outside of 4GM system in their own containers.&nbsp; So it's harder so screw up your system folder.&nbsp; Not Impossible. I was trying to get things working right, and I kept having issues of things going into that 4GB system folder.&nbsp; But since I knew the paths, I could delete those files easily using WinSCP.&nbsp; I can look around and go, ops, that doesn't belong there.&nbsp;Now there was ways I guess to deal with Docker in a Interface.&nbsp; &nbsp;I found, once I figured it out, it was really a snap, and SSH into my ReadyNAS 516, and using Docker commands, was pretty easy after I figured out the right way for PATHS on the ReasyNAS.&nbsp; I kind of had a brainfart.&nbsp; &nbsp;If you can't just install an app using a DEB file like I do for PLEX and Tautalli which is a great Monitoring and tracking tool for PLEX, though they also both can be installed using DOCKER also if you wanted.&nbsp; It was completely new to me a couple weeks ago and took a couple weekends to figure it out and get it all working.&nbsp;All that Docker stuff is outside of the 4GB system partition not taking up any of that space.&nbsp; Not screwing up your system files.&nbsp; It's also simpler to get the apps to auto startup on their own when the NAS boots up.&nbsp; It's similar for the other Apps using docker also.&nbsp; So instead of trying to install apps using SSH the old fashion way and screwing up your 4GB system directory, move to Docker if you can.&nbsp; &nbsp;&nbsp; This link helped me.&nbsp; &nbsp;Kind of shows you how to go about it. It really is pretty simple.&nbsp; Some minor changes to their settings and away you go.&nbsp;https://www.smarthomebeginner.com/install-radarr-using-docker/&nbsp;&nbsp;&nbsp;&nbsp;

Forum Discussion

ReadyNAS 314 - root volume 99.67% full - cannot connect

4 Replies

Related Content

Lost my Volume Readynas 3138 Pulled Drives

Volume Expansion question

ReadyNAS GUI Volumes Bug

ReadyNAS RN316 showing Volume Is read-only

Volume lost on ReadyNas 104

NETGEAR Academy

ProSupport for Business