Pequod44

Thanks for the help 👍. Formatted the cache drive and I've started afresh with Docker. It's running okay at the minute so fingers crossed it will continue.

Thanks for the advice. Just to be clear (I'm afraid of making a mistake), I should be making a backup of my Flash drive? I'm assuming that I don't want to make a backup of Appdata or anything because I just want a fresh start with Docker etc. Best practice to take a screenshot of the main tab for drive assignments? Can I reformat from Unraid, or am I best taking the drive out and reformatting it on another machine? (apologies for the silly questions)

It still does the same thing, ran the scrub from the GUI and from the terminal. GUI blinks and terminal reports started and then stops immediately. UUID: 1fadd8d3-16ae-45cf-b0e6-00fc510e4de2 Scrub started: Wed May 28 12:10:22 2025 Status: aborted Duration: 0:00:00 Total to scrub: 219.07GiB Rate: 0.00B/s Error summary: no errors found

I checked it this morning and there were several messages from the User Scripts, still getting errors for some reason. Id Path Write errors Read errors Flush errors Corruption errors Generation errors -- --------- ------------ ----------- ------------ ----------------- ----------------- 1 /dev/sdb1 0 0 0 310 0

Thank you for the link, I have installed the User scripts, reset the stats and added the script for btfrs hourly monitoring. Since the docker service is technically running at the moment, I've included a screenshot of the volume mappings in case it is helpful. I can't open any of the containers, the web ui's just don't load atm. Since the using the scrub button earlier, the Unable to write to cache drive error in Fix Common Problems has gone and I can access the data share on my main PC also.

Pushing the scrub button in the GUI doesn't seem to do very much, the screen just blinks and the time updates and it says status aborted. I've ran the first command in the link above and it's shown a lot of corruption errors. Would running a scrub from the terminal be more effective? root@node304:~# btrfs dev stats /mnt/cache [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs 0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 60350 [/dev/sdb1].generation_errs 0

UUID: 1fadd8d3-16ae-45cf-b0e6-00fc510e4de2 Scrub started: Tue May 27 18:10:04 2025 Status: aborted Duration: 0:00:00 Total to scrub: 219.07GiB Rate: 0.00B/s Error summary: no errors found

Okay, well I went in an upgraded the Motherboard bios, ran memtest a couple of times and got passes each time. I also disabled the onboard WAN device (only option I could see which I think would control the Bluetooth) in the bios, hopefully that will stop it from spamming the log. Ran another set of diagnostics as well which I've attached. This time, I was able to log into the containers in Docker, how long they will stay available for is another question I suppose. node304-diagnostics-20250527-1734.zip

Hello again, Thanks for the help thus far, new diagnostics here: node304-diagnostics-20250526-2346.zip

I've got a 1TB WD SSD as the cache drive, I was previously using version 7.0.1. I've attached a screenshot the array as well.

I have rebooted the server and Docker started, unfortunately cannot open any of the containers to change the internal paths. I'm also seeing an "Unable to write to cache" message now in Fix Common Problems. I've attached some screenshots which might be helpful which contain some paths in the containers.

Unraid ver: 7.1.2 Hello everyone, I recently upgraded to 7.1.2 and since then I have been experiencing issues with Docker. I was watching something on Jellyfin and the stream crashed, so I logged into Unraid and I found the Docker tab with a message saying "Docker service failed to start" and that there were no containers installed. I read some instructions and watched a few videos on Youtube regarding the issue and increased the size of the Docker image to 50GB and rebooted - the same issue happened again. When the Docker service was running I looked at all of the paths to ensure they were okay and as far as I could see they were. So now I am stuck. I had the server switched off for a few days and I turned it back on today and the Docker service still isn't running. I ran Fix Common Problems and got the "Unable to write to Docker image" message. I would really appreciate some help and advice if possible. Thanks node304-diagnostics-20250526-1732.zip