I've started getting the error "Unable to write to disk1" with the suggested fix "Drive mounted read-only or completely full."

 

Disk 1 is a USB drive that I only have connected in order to run an array - I don't store anything on it, but its needed to run the docker and VM engines, which is what I use the server for. Anyway its only about 5% full, so hard to see why that would be the issue.

 

I saw some comments in the linked FAQ that its often linked to docker. In my case I'm using a Docker directory rather than an image, and its on the cache pool (which again has plenty of space).

 

So I'm slightly unsure what to check for next. I've attached diags - any help much appreciated.
 

server-diagnostics-20230911-1451.zip

USB device is dropping offline, try a new port, USB 2.0 preferred, or a different flash drive.

I'm using a Dell Optiplex 7060 Micro, which sadly doesn't seem to have any 2.0 USB ports. I can try a different flash drive though - should I be using a USB 2 one?

You can try, may be more reliable.

"Interestingly" I was unable to Stop the array. Even after I've removed the array USB drive, its still showing as Online in the GUI, Docker is still running etc. I'm slightly nervous about rebooting, but I'm guessing whatever state its gotten into is the cause of the error.

I'll probably leave it as is for now, and once I have a new USB 2.0 drive I'll reboot and see what happens.

8 minutes ago, Nuuki said:

array USB drive

USB not recommended for array or pools for many reasons

54 minutes ago, trurl said:

USB not recommended for array or pools for many reasons

For sure. I realise I'm pushing things a bit, but there's no data on the drive itself, and as I understand it its the only viable way to ru Unraid as a container / VM server. Maybe another hypervisor solution would be better, but I really like Unraid. So if it gives me the occasional headache its not a huge issue, so long as the core is stable and reliable (which it is).