I have been using unRAID mostly to run a 24/7 Plex server for the past couple of years without any issue at all. Today, suddenly my Plex server wasn't reachable. I first tried to reboot my router and then reboot the unRAID server and since both didn't help, I had a closer look.

 

I realised that there was a new notification about "Fix Common Problems" which was new (I check every day). There was a "Unable to write to disk2" and a "Background notifications not enabled" error / other comment. I didn't really know what to do. I went to the docker tab and checked for updates and there was indeed an update for the Plex docker. I tried running it but there was another error message - see attachement.

 

I let it be for a bit and checked later again and now there is a second error message "Unable to write to Docker Image" - see other attachment.

 

When I follow the "unraid main" or the "docker settings" button showed in the suggested fix, I don't really know what I'm supposed to do. The disk2 is indeed full (but there are 3 other disks which still have plenty of space). I don't know how the Docker Image is full or corrupted and what I'm supposed to do about it.

28 minutes ago, Huy said:

(I check every day) ... "Background notifications not enabled"

Setup Notifications to alert you by email or other agent as soon as a problem is detected, then you will know before you remember to check.

 

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Thanks for the suggestion, will turn it on.

 

Attached the diagnostics ZIP.

huyraid-diagnostics-20210812-1835.zip

Your system share has files on disk2 instead of all on cache as it should be. Don't know how you got into that state. Perhaps you enabled dockers when you didn't have cache at some point.

 

You shouldn't let any of your disks run out of space or you may corrupt it.

 

Each user share has a Minimum Free setting.

 

Unraid has no way to know how large a file will become when it chooses a disk for it. If a disk has less than Minimum, it will choose another disk.

 

You should set Minimum Free to larger than the largest file you expect to write to the share.

 

Each pool (cache) has a Minimum setting that works in a similar manner. If the pool has less than Minimum, it will choose an array disk when writing a cache-prefer or cache-yes user share (overflow).

 

You should delete and recreate docker.img

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

Before enabling dockers again or indeed using your server for anything you should take care of your disk full situation.

Thanks for your reply. I didn't know about those Minimum Free settings that I have to be cautious with.

 

To be honest, I am not 100% sure in which order I am supposed to do what now. First, delete and recreate docker.img? Or first change Minimum Free settings? How do I take care of my full disk situation? (I use shares and copy files on my server using those shares, so I never actually chose a disk to copy to)

Do you know how to work with files directly on the server instead of over the network?

I sometimes used the webterminal and entered "mc", if that's what you mean?

mc is what I have always used since it is builtin.

 

The disks are at /mnt/disk1, /mnt/disk2...

 

The user shares are at /mnt/user

 

You must be very careful and never work with both disks and user shares at the same time. Linux doesn't know these are different views of the same files, so it is possible to accidentally specify the same file for both source and destination when moving or copying, with the result that Linux tries to overwrite what it is trying to read.

 

You only need to move from disk to disk. For example you could move some movies from /mnt/disk2/movies to /mnt/disk4/movies, or whatever paths are appropriate on your server.

 

You can just disable Docker in Settings until you are ready to delete and recreate.

 

 

Thanks a lot for your help. I moved some files, now I have more than 100GB free on all disks and also changed the Minimum Free space setting on my shares and also on the cache drive. Then, I could update Plex without an error message. But the Plex server still doesn't work - should I create a new topic for it? I get a connection error - it doesn't even open. I didn't change any settings on my router and the Plex server was still running fine 24 hours ago.

2 hours ago, trurl said:

You should delete and recreate docker.img

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F