[Unraid 6.11.5 Docker Service failed to start.]

I wasn't able to save much of anything.

Thanks for your help though.

 

Reformat complete.

Docker containers reinstalled using pre-existing templates.

Reconfiguring containers and rebuilding VMs.

[Unraid 6.11.5 Docker Service failed to start.]

Alright. I have disabled overclock.

I have completely replaced the RAM.

 

I try to scrub the cache pool but it immediately aborts.

Fix Common Problems gives me the attached error.

 

New diagnostics also attached.

aperturescience-diagnostics-20230125-2018.zip

[Unraid 6.11.5 Docker Service failed to start.]

Ah. I have since separated them, but my server used to host my gaming/work rig.

 

Specs formerly dedicated to my gaming/work VM:
24 threads at 4Ghz (with the overclock)

64 GB of RAM

2TB SSD passed-through

3080 ti

 

It ran my VR rig and everything.

[Unraid 6.11.5 Docker Service failed to start.]

Will do. My new RAM arrives Wednesday.

Out of curiosity, I had the CPU overclocked by 8%. I don't know if that overclocked the RAM as well. Could that have led to the RAM failure?

I had pretty high-end RAM (G.Skill Ripjaws V Series) and it was only about a year old.

[Unraid 6.11.5 Docker Service failed to start.]

Looks like I have a bad RAM stick.

After I replace the stick, what then?

[Unraid 6.11.5 Docker Service failed to start.]

I was running Unraid 6.11.1 and my Docker Service wouldn't start, with the quoted error.

I upgraded to 6.11.5 and it started (some containers but not most).

I disabled and re-enabled the Docker service and now the service refuses to start again (with the same quoted error).

Quote

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712
Couldn't create socket: [2] No such file or directory
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898

I have tried recreating the docker image file, to no effect.

Please help.

You'll find my diagnostics attached.

aperturescience-diagnostics-20230120-0809.zip

[Array Will Not Auto-Start]

On 6/24/2022 at 1:21 AM, JorgeB said:

Parity is invalid, autostart will start to work once it's synced.

This was the issue.

It is now resolved.

 

Thank you for your help.

[Array Will Not Auto-Start]

Looks like I'm going to be waiting for awhile for the parity rebuild.

I'll let you know the results, once that's done.

[Array Will Not Auto-Start]

Here is the requested diagnostics archive.

aperturescience-diagnostics-20220623-2236.zip

[Array Will Not Auto-Start]

I have recently migrated all of my drives/dockers/VMs from Unraid 6.9.X (I don't remember what the last number was) to 6.10.3

Now, the array will not auto-start.

I have enabled auto-start in the disk settings but it won't auto-start.

 

Please help and please let me know if I can provide any info that can help.

 

Regards,

Ash