(SOLVED) Unable to Connect to Dockers

[Drogon]

I'm trying to get my cache pool removed and, in preparation of this, I was moving everything off of my cache drive. Apparently this is a no-no and I only saw the error alert after it was too late and some of my appdata files had been moved. I moved them back to my cache but now I can't connect to any of the dockers. What's the fix for this?

Edited June 23 by Drogon

[JorgeB]

Please post the diagnostics.
 

[Drogon]

Diagnostics attached. I've tried force updating and removing/reinstalling the dockers that don't work but that hasn't helped.

truesource-diagnostics-20240621-0918.zip

[JorgeB]

Btrfs is detecting data corruption in the pool, so first thing to do is to run a correcting scrub, post the results from that.

[Drogon]

I tried that yesterday on my docker settings but I found another scrub in the cache settings, which is probably the one you're referring to? Here are the results:

DOCKER

UUID: 94b3c8f9-211d-4688-bde6-d0e34d3e0704

Scrub started: Thu Jun 20 17:51:40 2024

Status: finished Duration: 0:00:04

Total to scrub: 12.43GiB

Rate: 3.14GiB/s

Error summary: no errors found

 

CACHE

UUID: 111b1f78-5398-4386-889e-e15cd660b0d3

Scrub started: Fri Jun 21 11:11:05 2024

Status: finished

Duration: 0:11:55

Total to scrub: 370.45GiB

Rate: 530.54MiB/s

Error summary: no errors found

Edited June 21 by Drogon

[JorgeB]

Since no errors were found, clear the stats and keep monitoring, in case new ones come up, and if they do, there's still a problem, most often RAM related.

 

Regarding the docker issue, try recreating the docker image:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

[Drogon]

Just tried that and no luck. I scrubbed the cache again and restarted. Still no luck accessing the dockers. I've attached the updated diagnostics file which hopefully contains something useful.

truesource-diagnostics-20240621-2132.zip

[JorgeB]

I don't see anything relevant in the logs, can you describe exactly the issue? Docker service appear to be running correctly.

[Drogon]

This is what I see when I try to access the affected dockers:

 

[JorgeB]

And it only happens with some? a few, most?

[Drogon]

5/10. If I had to guess it happens with the dockers that had data moved off of the cache drive before I noticed.

[JorgeB]

If you re-create one of those container from scratch, without using the existing appdata, doers it work correctly?

[Drogon]

Yep. I removed the appdata folder for one of the dockers, reinstalled, and I'm now able to access the docker. Is there a way to backup my data and somehow bring it over to the new docker or am I going to have to set up everything from scratch?

 

Something probably of note: In my appdata folder, there were changes to the owner and permission fields with the new image. Owner changed from root to nobody and permission went from drwx------ to drwxrwxr-x.

 

EDIT: Most of the dockers that aren't working match the old root / drwx------ and changing this (then restarting the docker) does allow access to the docker so I'm all set. Except for my Plex docker... which is already set to nobody / drwxrwxr-x. Not sure what to do about this one?

 

EDIT: Something in the folder must have had different owner/permissions because I went ahead and "changed" it to nobody / drwxrwxr-x and after restarting it's working. Thanks for all of your help!

 

While I've got you here... why don't I have the drop down options on my cache to convert it back to single mode? This is what started all of my problems:

EDIT: For anyone that comes across this, I couldn't convert to single mode because I had already removed a disk from the pool. I added the disk back, balanced again, and then I was able to convert to single mode.

Edited June 23 by Drogon