NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RobW_73
Apr 17, 2019Aspirant
ReadyNAS 214: System Volume root useage 90%
System: Netgear ReadyNAS 214.
Firmware; 6.9.5
Storage: 8tb (free 3.25tb).
Started to see lots of alerts coming through;
"System volume root's useage is 90% This condtion should not oc...
- Apr 17, 2019
RobW_73 wrote:
Concur. Been reading some other topics. I haven't used it much. I have a Mac - so using the shell more. But not massively experienced in this area.
Well, if you enable ssh on the NAS, you can then connect using terminal. The command is ssh root@nas-ip-address The root password is the same as the NAS admin password.
From there you can see if the issue is from plex by entering the following:
# mount --bind / /mnt # cd /mnt # find . -name chunk*.m4s
If you see those chunk<whatever>.m4s files in the output of the find command, then the issue is plex, and you want to delete them. You can use cd to navigate to the relevant folders, and then delete these files with the rm command
# rm chunk*.m4s
Be careful on the typing - especially since there is a wildcard (*) in the command. That lets you delete all the chunk files in a single command.
If you don't find any of these files, then the problem isn't plex - and we need to figure out where the space is going. Enter
# du -csh /mnt/*
That will give you some idea of the space usage. copy the results to this thread.
FWIW, on my NAS I see
root@NAS:/mnt# du -csh /mnt/* 0 /mnt/1 0 /mnt/apps 6.4M /mnt/bin 0 /mnt/boot 0 /mnt/data 24K /mnt/dev 11M /mnt/etc 30M /mnt/frontview 0 /mnt/ftp_ban.tbl 0 /mnt/home 4.0K /mnt/homes 33M /mnt/lib 4.0K /mnt/lib64 0 /mnt/media 0 /mnt/mnt 4.6M /mnt/opt 0 /mnt/proc 28K /mnt/root 0 /mnt/run 9.9M /mnt/sbin 0 /mnt/srv 0 /mnt/sys 0 /mnt/tmp 202M /mnt/usr 604M /mnt/var 899M total
I have a different model, but your results should be similar.
Usually there is just one massive subfolder. You descend into that with cd, and then repeat the du command. At some point you are likely to find one folder with just a couple of large files(perhaps just one) That accounts for the space. We need to find out what those files are.
ls -alh is one way to see the size of all files in a particular folder, so you can use that in conjunction with the du command.
When done, enter these commands
# cd // # umount /mnt
This undoes the mount at the beginning.
RobW_73
Apr 17, 2019Aspirant
Concur. Been reading some other topics. I haven't used it much. I have a Mac - so using the shell more. But not massively experienced in this area.
StephenB
Apr 17, 2019Guru
RobW_73 wrote:
Concur. Been reading some other topics. I haven't used it much. I have a Mac - so using the shell more. But not massively experienced in this area.
Well, if you enable ssh on the NAS, you can then connect using terminal. The command is ssh root@nas-ip-address The root password is the same as the NAS admin password.
From there you can see if the issue is from plex by entering the following:
# mount --bind / /mnt # cd /mnt # find . -name chunk*.m4s
If you see those chunk<whatever>.m4s files in the output of the find command, then the issue is plex, and you want to delete them. You can use cd to navigate to the relevant folders, and then delete these files with the rm command
# rm chunk*.m4s
Be careful on the typing - especially since there is a wildcard (*) in the command. That lets you delete all the chunk files in a single command.
If you don't find any of these files, then the problem isn't plex - and we need to figure out where the space is going. Enter
# du -csh /mnt/*
That will give you some idea of the space usage. copy the results to this thread.
FWIW, on my NAS I see
root@NAS:/mnt# du -csh /mnt/* 0 /mnt/1 0 /mnt/apps 6.4M /mnt/bin 0 /mnt/boot 0 /mnt/data 24K /mnt/dev 11M /mnt/etc 30M /mnt/frontview 0 /mnt/ftp_ban.tbl 0 /mnt/home 4.0K /mnt/homes 33M /mnt/lib 4.0K /mnt/lib64 0 /mnt/media 0 /mnt/mnt 4.6M /mnt/opt 0 /mnt/proc 28K /mnt/root 0 /mnt/run 9.9M /mnt/sbin 0 /mnt/srv 0 /mnt/sys 0 /mnt/tmp 202M /mnt/usr 604M /mnt/var 899M total
I have a different model, but your results should be similar.
Usually there is just one massive subfolder. You descend into that with cd, and then repeat the du command. At some point you are likely to find one folder with just a couple of large files(perhaps just one) That accounts for the space. We need to find out what those files are.
ls -alh is one way to see the size of all files in a particular folder, so you can use that in conjunction with the du command.
When done, enter these commands
# cd // # umount /mnt
This undoes the mount at the beginning.
- RobW_73Apr 20, 2019Aspirant
Definitely plex. Had thousands of *.ts and *.m4s files. All deleted.
Might have made an error in deleting the *.ts files. Luckily - i have made a backup (last night) so can restore.
Otherwise - thank you. I quite fancy doing more stuff at the command line now.
EDIT: Out of interest, is there a way to increase the system root size. 4Gb seems a little small. If there is id like to increse it to about 50Gb.
EDIT2: upon further investigation im having to rebuild my plex library. Should not have deeleted the *.ts files. Oh, well. A learning oppotunity.
- StephenBApr 20, 2019Guru
RobW_73 wrote:
EDIT: Out of interest, is there a way to increase the system root size.
Unfortunately no.
RobW_73 wrote:
EDIT2: upon further investigation im having to rebuild my plex library. Should not have deeleted the *.ts files. Oh, well. A learning oppotunity.
Were they in the data volume or in root? Do you remember the path?
- RobW_73Apr 20, 2019AspirantShame about not being able to increase the root file system.
Think it was /mint/media*
Will double check though.
Related Content
NETGEAR Academy

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