× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Root disk nearly full (82%)...

owensr
Aspirant

Root disk nearly full (82%)...

Looked though all the other posts on this common issue but can not find anything I can safely delete. Details are:

 

root@NETGEAR-NAS:~# du -hsx /* | sort -rh
2.1G /var
559M /apps
426M /usr
169M /data
31M /frontview

 

So issue in var or apps or usr...

In var issue is:

 

root@NETGEAR-NAS:/var/lib/mysql# ls -lrtah ibdata1
-rw-rw---- 1 mysql mysql 990M Dec 21 08:47 ibdata1

 

and

 

root@NETGEAR-NAS:/var/lib/clamav# ls -lrtah daily.cld main.cld
-rw-r--r-- 1 root root 443M Sep 18 11:27 main.cld
-rw-r--r-- 1 root root 171M Dec 18 12:30 daily.cld

 

But not sure I can delete or purge any of those?

 

In apps issue is:

 

root@NETGEAR-NAS:/apps/.xdg/cache/tracker# ls -lrth meta.db
-rw-r--r-- 1 root root 501M Sep 19 14:38 meta.db

/apps is not mounted on root...

 

Again anything I can do about this?

 

/usr all looks like the normal linux libs etc... that I know I can not delete!

 

/data is all in /data/rsyslog - I did delete these - but they steadliy re-appear.

 

 

Model: RN2120v2|Readynas 2120v2 1U 4-Bay Diskless
Message 1 of 6
owensr
Aspirant

Re: Root disk nearly full (82%)...

Just realised that /apps was mounted not on / but on the other disks so does not matter...

So just ways of purging the other files would be of interest!

Message 2 of 6
owensr
Aspirant

Re: Root disk nearly full (82%)...

Removing post as made no sense!

Message 3 of 6
StephenB
Guru

Re: Root disk nearly full (82%)...

First, if you want to analyze what's in root, it's best to remount it.  There are several mount points in it, and often files are "underneath" the mounts, and therefore hidden.

 

# mount --bind / /mnt

 

You can later on unmount it with

# cd /
# umount /mnt 

Also, in most systems /data is also a mount point (for the data volume).  So check /mnt/data after you remount it, and make sure rsyslog is where you think it is.

 

 


@owensr wrote:

 

root@NETGEAR-NAS:/var/lib/mysql# ls -lrtah ibdata1
-rw-rw---- 1 mysql mysql 990M Dec 21 08:47 ibdata1

 

/data is all in /data/rsyslog - I did delete these - but they steadliy re-appear.

 


A stock OS-6 ReadyNAS doesn't use rsyslog or mysql at all.  You must have installed an app (or package) at some point that does. Given the file date on mysql, and the fact that rsyslog keeps coming back, that added software must still be running.  There used to be a third-party app called LogAnalyzer - if you installed that, you should uninstall it. 

 

There are two options here:  

  1. Track down the packages/apps that were installed, and uninstall them.  Then delete /data/rsyslog and /var/lib/mysql. (A variation on this is to do a factory default, rebuild the NAS, and restore the data from backup).
  2. Move the two folders into a share on the data volume.  Then create soft links in /data and /var/lib that point into those folders.  The files will continue to grow, but of course the data volume is much larger than the OS partition.
Message 4 of 6
owensr
Aspirant

Re: Root disk nearly full (82%)...

I think at some point I renamed data to data2. So data2 is my main volume and data is a root mounted directory.

Only app I have installed is iDrive backup software.

 

I looked at the contents of the mysql database and is a database called:

Syslog

And has one massive table called:

SystemEvents

 

That is the full 1gig. Seems to have every event since 2016! And is still being populated.

I will just truncate that table - as will fix issue for a few years.

But would be good to know what is pushing data into it?

 

There is a chance that I installed other apps a while ago that I have since uninstalled.

 

 

Thanks

Message 5 of 6
StephenB
Guru

Re: Root disk nearly full (82%)...


@owensr wrote:

 

There is a chance that I installed other apps a while ago that I have since uninstalled.

 


If so, something likely didn't uninstall correctly.

 


@owensr wrote:

 

I will just truncate that table - as will fix issue for a few years.

But would be good to know what is pushing data into it?

The most likely cause is the old LogAnalyzer app - likely not uninstalled correctly. You could try to track that down by looking in apt-history in the log zip file.

 

As I mentioned, using soft links will let you move the folders onto the data volume.  That will protect the OS volume from filling (which can corrupt your configuration files).

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 987 views
  • 0 kudos
  • 2 in conversation
Announcements