Array will stop and I do not have the option to re-start, I reboot to fix !

[TKB]

 

 

I need help my server will work for about 2 to 3 days, then I will get array must be started. The only fix I know of is to restart the server but after restart I have to reset up Sonarr, Radarr, Sabnzbd and Plex

I am also getting an error under plugin

Warning: file_put_contents(): Only -1 of 1565 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 139

Do this mean that I am out of disk space, I am not very good with this and my friend that was teaching me pass away and I have no one to help me fix his problem I have also attach an old diagnost because I can not get the diagnost to run only when I reboot.

Thanks for any help you can give me.

 

ladybugg-diagnostics-20211228-1209.zip

[Squid]

First thing you should do is delete Headphones.plg from /config/plugins on the flash drive and reboot.  PhAzE plugins haven't been compatible with the OS since 6.2.0

[TKB]

I removed Headphones.plg on the flash drive and reboot but my setting for Sonarr, Radarr, Sabnzbd and Plex did not keep I will re set them up again. is there anything else I need to do to keep my setting?

[trurl]

You're also using a deprecated version of the CA Backup plugin. Remove it and install the new one from the Apps page.

 

13 hours ago, TKB said:

my setting for...

Do you mean the settings for each container, or do you mean the settings within each application?

 

Why do you have 500G docker.img? 20G is often more than enough. Making it large won't fix anything

 

You have docker.img in /mnt/user, instead of actually in a specific user share. Not clear which disk it might be on. Most of your disks are very full.

 

Appdata has some files on cache, but you don't have a cache drive, so you must have accidentally created a path to /mnt/cache, probably in some container's host path to /mnt/cache/appdata.

 

And that would explain why application settings wouldn't persist since this would be a path in rootfs (RAM).

[TKB]

My friend setup everything now she is gone, I am not very techie with server but I understand a little.  I will make the changes and let you know. and it is the settings within each application.  I am almost out of space waiting on a new hard drive to come in. I have been moving some of the file to clear up space.  500G for docker.img not sure that what's my friend setup tried to get him to teach me but that did not happen.  Thanks for all your help.

[trurl]

13 minutes ago, TKB said:

I am almost out of space waiting on a new hard drive to come in.

Ideally you would configure dockers/VMs to use a fast pool (SSD cache) instead of putting them on the parity array. They won't perform as well on the slower parity array, and will keep array disks spunup since they always have files open.

 

In any case you should start over with your docker configuration. The usual place for docker.img is in the system share. You should delete and recreate it there as 20G instead of 500G, then reboot since you have accidentally created cache in RAM where it won't persist.

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

Then you can use Previous Apps to reinstall your containers. But you should take them one at a time and figure out which are specifying a host path to /mnt/cache/appdata and change to /mnt/user/appdata.

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

 

[TKB]

thanks I will order a SSD and get started thanks for every. and he did have a 500G laying around and he just used spare parts but it have been great till now.