NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Error message "System volume root usage is 90%"
Out of the blue sky I get this message from my ReadyNAS RN628X: "System volume root usage is 90%. This condition should not occur under normal conditions. Contact technical support.". What does this ...
ronaldvr2132 wrote:
In this folder there is also a file called core-readynasd (way lesser in size by the way) can I delete that file as well without consequences?
Yes.
ronaldvr2132 wrote:
One last question: I was warned that with no space available I run the risk that the NAS configuration files can get corrupted. Is this something I can check if this corruption already occured?
There's no bullet-proof check. If you can see the shares list in the admin web ui, you are probably ok. Also look in system->settings->services and make sure the services you use are all marked with the green bar.
Hi ronaldvr2132,
This message means that the OS partition is getting full. This is usually caused by apps installed on the OS partition. Have you tried installing any apps through SSH?
If you are comfortable in accessing the NAS via SSH, you can take a look on that said partition through that method. Otherwise, It would be best if you contact NETGEAR support so they can check your NAS and free the OS partition.
Regards,
Thank you JohnCM_S for coming back to me. As to the possible cause: I don't have any apps installed on my RN628X. The only thing that I can think of is that it has something to do with either the antivirus or indexing functionalioty that I am using or maybe back-ub jobs that were not started or interrupted because of a bad line to my other RN628X. Other then that I can't think of anything else. And as to the usage of my RN628X I am way below what the RN628X is designed for in terms of users, number of files, file changed in a certain time period etc.. Out of curiosity how big is the OS partition and can that be increased? And as to SSH into the RN628X. I might know womeone who can assist me is there some documentation on this? Thanks again!
In the meantime I have asked a collegue to look at the usage and he could not see anything extrordinary. But he saw some big files including a file with the name e-aurndb-write-db which seems to be 2.8Gb. In the meantime my NAS has only 38MB free at the root level and is eating up space in a very fast manner without knowing why. I saw some back-up jobs that were cancelled (probably due to a bad line connection) can that be a cause? As a precaution I switched off the anti virus service and the file search (indexing) service. Will a reboot help or should I not do such a thing? Very worrying and annoying this by the way!
ronaldvr2132 wrote:
In the meantime I have asked a collegue to look at the usage and he could not see anything extrordinary. But he saw some big files including a file with the name e-aurndb-write-db which seems to be 2.8Gb. In the meantime my NAS has only 38MB free at the root level and is eating up space in a very fast manner without knowing why.
Move e-aurndb-write-db out of root (putting into a share on the data volume). That should free up enough space immediately to give you breathing room to continue analysis.
Don't create a new share (that might fail with no root space - and corrupt your configuration). Instead move it to an existing share with ssh. After you have space, you can create a temp share, and move it again.
ronaldvr2132 wrote:
In the meantime I have asked a collegue to look at the usage and he could not see anything extrordinary. But he saw some big files including a file with the name e-aurndb-write-db which seems to be 2.8Gb. I saw some back-up jobs that were cancelled (probably due to a bad line connection) can that be a cause?
Sometimes if the USB drive unmounts during a back-up, the system will write files to the USB mount point. If that happened, these would be files that are also on the data volume somewhere. What is the path to these files?
Note that it is handy to remount the OS partition as /mnt (which drops the mount points in root) when you do this kind of analysis.
# mount --bind / /mnt
Then examine /mnt. When done, just umount /mnt.
Hi StephenB thanks for the suggestion. Before we move the file can you let me know what the file is for? Can we move it without interuption of he system? And should the file be soo big?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
