NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JohnT123456
Mar 19, 2019Aspirant
System volume root's usage is 90% RN102
Please can someone help, I am a total novice with these things. I have read some of the post about the same issue, it talks of SSH mumbo jumbo...lol. I have switched SSH on in the admin GUI so shoul...
- Mar 19, 2019
Be careful here, as there are support implications in trying to fix this yourself. Typing the wrong thing can do damage, and require you to do a factory default to recover. So I recommend backing up the NAS first. https://kb.netgear.com/30068/ReadyNAS-OS-6-SSH-access-support-and-configuration-guides
You first disable the AntiVirus service - which it sounds like you have already done.
The second step is to enable SSH in the NAS web ui in system->settings. If your password is still set to password, you also need to change it to something else.
Now you need a program to connect to the NAS using SSH. Windows 10 has a program built in (called ssh). So do Macs (terminal). For other windows versions you need to install putty from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html (and you can also use putty on Windows 10 if you like).
Then you use that program to connect to the NAS:
- ssh root@nas-ip-address on Windows 10 (entered on the Windows 10 search bar)
- launch terminal, enter ssh root@nas-ip-address on the mac
- launch putty, make sure ssh is selected as the connection type. Enter the nas-ip-address and click open. Enter root as the username.
Use the real NAS IP address of course. It's important to log in as root. Don't log in as admin. When you see the password prompt, enter the NAS admin password (root and admin use the same password).
If you have trouble launching one of these programs, then you can post back (or just google for more info).
Be careful on the typing of the commands below. Be sure to use the correct slash direction, etc.
After you are logged in, you enter
cd /var/lib/clamav ls -lsh
You should now see a folder listing, with some folders that look like clamav-<very long string>.tmp
If you don't see these tmp folders, then post back and tell us what you do see.
If you do see these tmp folders, then you remove them by entering
rm -r clamav-*.tmp ls -lsh
You should now see a second folder listing, and those tmp folders should be gone.
asimb has posted a screen shot illustrating these commands: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/System-volume-root-s-usage-is-xx-This-condition-should-not-occur/m-p/1722860#M178464
I'm taking the liberty of re-posting that screen shot here.
I recommend leaving the AntiVirus service off - at least for now.
Leventh
Nov 07, 2023Apprentice
Dear StephenB
I got the same issue on my RN214 about couple days ago, log shows;
Nov 07, 2023 08:00:30 | Volume: System volume root's usage is 86%. This condition should not occur under normal conditions. Contact technical support. |
I disabled AV and ssh to clean tmp files but it doesn't have these files and /var/log itself taking too much space, could you help?
- LeventhNov 07, 2023Apprentice
root@UniNAS214:~# mount --bind / /mnt
root@UniNAS214:~# cd /mnt
root@UniNAS214:/mnt# du -d1 -h
4.0K ./sys
4.0K ./boot
12K ./dev
112K ./tmp
31M ./frontview
4.0K ./mnt
231M ./usr
4.0K ./data
8.8M ./etc
4.0K ./proc
16K ./lost+found
4.0K ./run
1.8G ./var
301M ./root
4.0K ./media
11M ./sbin
29M ./lib
798M ./opt
4.0K ./apps
4.0K ./home
4.0K ./srv
6.0M ./bin
3.2G .
root@UniNAS214:/mnt# cd /var
root@UniNAS214:/var# du -d1 -h
78M ./cores
159M ./cache
4.0K ./tmp
8.0K ./www
4.0K ./mail
94M ./backups
16K ./netatalk
1.1G ./log
4.0K ./local
9.5M ./readynasd
445M ./lib
4.0K ./opt
16K ./spool
4.0K ./ftp
1.8G .
root@UniNAS214:/var#
root@UniNAS214:~# cd /var/log
root@UniNAS214:/var/log# du -d1 -h
44K ./apt
76K ./frontview
57M ./journal
4.0K ./fsck
288K ./readynasd
973M ./apache2
648K ./samba
1.1G .
root@UniNAS214:/var/log# ls /mnt/var/log -alhS
total 200K
-rw-r--r-- 1 root root 286K Nov 7 18:39 lastlog
-rw-rw-r-- 1 root utmp 82K Nov 7 18:39 wtmp
-rw-r--r-- 1 root root 27K Nov 5 18:20 dpkg.log
-rw-r--r-- 1 root root 24K Nov 6 06:37 faillog
-rw-r----- 1 root root 8.1K Nov 5 19:09 proftpd.log
-rw------- 1 root root 6.2K Nov 7 19:55 tallylog
-rw------- 1 root utmp 4.2K Nov 5 16:17 btmp
drwxr-xr-x 9 root root 4.0K Sep 5 2022 .
drwxr-xr-x 16 root root 4.0K Jul 30 14:59 ..
drwxr-x--- 2 root adm 4.0K Aug 25 2018 apache2
drwxr-xr-x 2 root root 4.0K Aug 22 2022 apt
drwxr-xr-x 3 root root 4.0K Dec 11 2012 frontview
drwxr-xr-x 2 root root 4.0K Apr 30 2016 fsck
drwxr-sr-x+ 3 root systemd-journal 4.0K Feb 17 2023 journal
drwxr-xr-x 2 admin admin 4.0K Feb 19 2023 readynasd
drwxr-xr-x 2 root root 4.0K Oct 28 21:09 samba
root@UniNAS214:/var/log#
- StephenBNov 07, 2023Guru - Experienced User
Here's what I see on my RN202:
root@RN202:/mnt# du -d1 -h 6.0M ./bin 4.0K ./proc 4.0K ./boot 11M ./sbin 24K ./tmp 16K ./lost+found 4.0K ./run 31M ./frontview 4.0K ./sys 12K ./dev 8.9M ./etc 4.0K ./media 3.9M ./opt 4.0K ./apps 4.0K ./mnt 4.0K ./data 4.0K ./home 217M ./usr 29M ./lib 325M ./var 4.0K ./Data-2 40K ./root 4.0K ./srv
Biggest differences appear to be in /opt and /var/log
root@RN202:/mnt/opt# du -d1 -h 2.2M ./readycloud 740K ./p2p 204K ./xcloud 24K ./remote 748K ./replication 3.9M
root@RN202:/mnt/var/log# du -d1 -h 53M ./journal 480K ./readynasd 3.3M ./frontview 4.0K ./fsck 260K ./samba 4.0K ./apache2 24K ./apt 57M .
On /opt, you might want to provide some more details on what is in there.
On /var/log - it all appears to be apache 2 logging. Did you try clearing the logs from the NAS web UI? If you have, then what are you seeing in /var/log/apache2? (it's hard to read your info on that).
- LeventhNov 07, 2023Apprentice
ReadyNAS RN214
Yes, I did clearing logs on web UI, details are above next to this post.
Could it be related with ZeroTier One App.?
...and deeper root of the log;
root@UniNAS214:/var/log# cd ./apache2
root@UniNAS214:/var/log/apache2# ls -l
total 996680
-rw-r--r-- 1 root root 1020595319 Nov 7 21:41 other_vhosts_access.log
root@UniNAS214:/var/log/apache2# du -h
974M .
root@UniNAS214:/var/log/apache2# ls -alh
total 974M
drwxr-x--- 2 root adm 4.0K Aug 25 2018 .
drwxr-xr-x 9 root root 4.0K Nov 7 20:01 ..
-rw-r--r-- 1 root root 974M Nov 7 21:42 other_vhosts_access.log
root@UniNAS214:/var/log/apache2#
- LeventhNov 07, 2023Apprenticeroot@UniNAS214:/var# cd ./log
root@UniNAS214:/var/log# du -h
44K ./apt
4.0K ./frontview/backup
76K ./frontview
57M ./journal/54ed0b8fe2e24784b2ba2f953e9a9c17
57M ./journal
4.0K ./fsck
292K ./readynasd
974M ./apache2
652K ./samba
1.1G .
root@UniNAS214:/var/log#- StephenBNov 07, 2023Guru - Experienced User
Leventh wrote:
root@UniNAS214:/var# cd ./log
974M ./apache2As I said above, this is the issue in /var/log. If you cleared the logs from the NAS web ui, then you should go into this folder and take a closer look. Likely you can truncate any log file that is in there.
Note I asked for more details on /opt, not /var/log. Yours has ~320 MB more stuff in it than mine.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!