Greygoose Posted April 28, 2019 Share Posted April 28, 2019 (edited) When i try to run diagnostics from GUI it doesn't allow, it says array unidentified. I run the diagnostics command from terminal and i get this... Warning: file_put_contents(): Only 0 of 838 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 208 done. ZIP file '/boot/logs/tower-diagnostics-20190428-0938.zip' created. Edited May 5, 2019 by Greygoose Quote Link to comment
Greygoose Posted May 5, 2019 Author Share Posted May 5, 2019 its doing it again guys, id really appreciate help Quote Link to comment
Squid Posted May 5, 2019 Share Posted May 5, 2019 On 4/28/2019 at 4:41 AM, Greygoose said: ZIP file '/boot/logs/tower-diagnostics-20190428-0938.zip' created. You'd need to post the file Quote Link to comment
itimpi Posted May 5, 2019 Share Posted May 5, 2019 How much RAM do you have, and how much has been allocated to your VM? Quote Link to comment
Greygoose Posted May 12, 2019 Author Share Posted May 12, 2019 On 5/5/2019 at 6:10 PM, Squid said: You'd need to post the file I looked at this file and it contains the file names but no DATA or information. Quote Link to comment
Greygoose Posted May 12, 2019 Author Share Posted May 12, 2019 On 5/5/2019 at 6:16 PM, itimpi said: How much RAM do you have, and how much has been allocated to your VM? I have 32GB and 12GB allocated to VM's. Quote Link to comment
Greygoose Posted May 12, 2019 Author Share Posted May 12, 2019 This is the docker list on the system, in case you can see any errors Quote Link to comment
Greygoose Posted May 12, 2019 Author Share Posted May 12, 2019 I have attached a new Diagnostics file, this is after the reboot just now (the error happened again). I dont expect it will contain any details as the system is now running fine. until it does it again, randomly. mediaserver-diagnostics-20190512-0951.zip Quote Link to comment
bonienl Posted May 12, 2019 Share Posted May 12, 2019 The error you get implies you run out of capacity in rootfs. Usually happens when something is written to a non-existing folder or a non-existing disk reference Your current rootfs utilization is low, and you can monitor this by the "df -h" command # df -h Filesystem Size Used Avail Use% Mounted on rootfs 16G 996M 15G 7% / The mapping of resilio-sync seems a bit strange. I would expect a folder under /mnt/user /sync --> /mnt/user Quote Link to comment
Greygoose Posted May 14, 2019 Author Share Posted May 14, 2019 ok quick update. I deleted docker.img and restored only some dockers and the error happened over night. i managed to get a diagnostics.img mediaserver-diagnostics-20190514-0530.zip Quote Link to comment
itimpi Posted May 14, 2019 Share Posted May 14, 2019 (edited) Your /var/log location is full which is abnormal. You might want to try running df -h /var/log/* to see what is filling it up. Edited May 14, 2019 by itimpi Quote Link to comment
Greygoose Posted May 19, 2019 Author Share Posted May 19, 2019 hi again, I think i have narrowed down the issue. I stopped all dockers, then added back only the mainly used ones, then i went back to using only a couple and out of them i THINK it is to do with sonar and sabnzb I have added some pics of the setup of sonar Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.