This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
While you have the OS partition remounted, you should also look in /mnt/media. Look for files in the USB_HDD* folders there - the ones in /mnt should be empty.
That warning message appears when your ReadyNAS System Volume capacity reaches 80% and up. This means that an app installed or logs that uses your System volume is filling up the space and this is not normal since the app or logs should not be using the System volume.
I would suggest contacting Support through my.netgear.com so they can assist you on getting this corrected. You will have to purchase a contract if your 90 days support is expired.
Otherwise, accessing the NAS through SSH and removing the files filling up the space is another resolution. This will need you to be comfortable using it.
Yes Data volume is different from System root volume.
System is actually 4GB in size. Unfortunately, clearing the system logs and or running volume maintenance may not affect the system volume since it is actually targeting the data volume.
It is really advisable to contact Support for proper assistance or use the Community guide on clearing up System root volume but only if you are comfortable using SSH.
It is really advisable to contact Support for proper assistance or use the Community guide on clearing up System root volume but only if you are comfortable using SSH.
I agree. If you aren't already familiar with linux commands, you should use support. Ask for per-incident support. Don't purchase the gearhead support - it's not what you want for this.
So is this a new problem thats occured with a firmware update ?
The threshold for the error is 80%. It's likely that the files have been building up for some time.
The ReadyNAS does clean up some files, but sometimes logs can still build up. Also, some apps will use OS partition space incorrectly. Plex for example will sometimes leave behind temporary files when it does real-time transcoding. The NAS application doesn't try to remove those (since it didn't put them there, and has no idea what they are). There are a couple of other common causes.
Support can easily fix this. But if you wait too long, the NAS can misbehave, and eventually it will fail to boot. So it's best to take care of it now.
While you have the OS partition remounted, you should also look in /mnt/media. Look for files in the USB_HDD* folders there - the ones in /mnt should be empty.
So is this a new problem thats occured with a firmware update ?
Ive had my NAS for several years now with no problems before, or is it the fact that its been several years ??
A firmware update can be the "tipping point", as the downloaded update is stored in the root partition, but it's not the root cause. Sounds like you are on the right track to finding the files that are filling the partition. But what you really need is a solution to eliminate their creation. If it's PLEX, I have not seen one. But, perhaps, a directory on the OS partition needs to be replaced with a symbolic link to one in the apps directory.
@Sandshark wrote: If it's PLEX, I have not seen one.
The Plex package for ReadyNAS does use /apps for the library, etc.
But sometimes it leaves behind chunk*.m4s files in the root partition. It's safe to simply delete these. Per some posts in the plex forum, they apparently are left when transcoding is aborted or fails. Why they are in the root partition in the first place is unknown.
This isn't unique to the ReadyNAS package, it's been reported with other NAS and also the Windows server.
But sometimes it leaves behind chunk*.m4s files in the root partition. It's safe to simply delete these. Per some posts in the plex forum, they apparently are left when transcoding is aborted or fails. Why they are in the root partition in the first place is unknown.
This isn't unique to the ReadyNAS package, it's been reported with other NAS and also the Windows server.
So, are they always in the same directory, and is that directory uniquely used by PLEX? If both answers are "yes", then it should be possible to also move their creation to /apps. Of course, PLEX should do that on its own and should also clean up after itself..
@Sandshark wrote: So, are they always in the same directory, and is that directory uniquely used by PLEX? If both answers are "yes", then it should be possible to also move their creation to /apps. Of course, PLEX should do that on its own and should also clean up after itself..
Clearly plex should clean them up. But let's see if this it really the issue here, and get rid of any of these files.
You total HERO !!!!!!! thank you so much for your help it was full fo .m4s files.
sucessfuly deleted, also there were a lot of numbered chunk files ..............i deleted these also.
The sys volume is now down to1.2gb
Do you think these files are created every time you use Plex ?
Or possibly not shutting it down properly ?
It seems impossible to contact Netgear to ask about support....... you just get directed to the support portal and told to purchase Gearhead support package. this seems to be the only option.
Thanks for your patience and help, it was no where near as daunting as i thaught .
