Acheron4171 Posted January 20, 2023 Share Posted January 20, 2023 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 Quote Link to comment
Solution JorgeB Posted January 20, 2023 Solution Share Posted January 20, 2023 Btrfs is detecting data corruption on all 3 pool members, start by running memtest. Quote Link to comment
Acheron4171 Posted January 20, 2023 Author Share Posted January 20, 2023 Looks like I have a bad RAM stick. After I replace the stick, what then? Quote Link to comment
JorgeB Posted January 21, 2023 Share Posted January 21, 2023 After the issue is fixed run a scrub on the pool and post new diags. Quote Link to comment
Acheron4171 Posted January 21, 2023 Author Share Posted January 21, 2023 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. Quote Link to comment
JorgeB Posted January 22, 2023 Share Posted January 22, 2023 18 hours ago, Acheron4171 said: I don't know if that overclocked the RAM as well. Could that have led to the RAM failure? It could, it could even mean that the RAM is OK just not stable with an overclock, servers and overclock don't go together. Quote Link to comment
Acheron4171 Posted January 25, 2023 Author Share Posted January 25, 2023 (edited) 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. Edited January 26, 2023 by Acheron4171 Add more info. Quote Link to comment
Acheron4171 Posted January 26, 2023 Author Share Posted January 26, 2023 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 Quote Link to comment
JorgeB Posted January 26, 2023 Share Posted January 26, 2023 If the issues as solved pool should be redone, backup what you can and reformat. Quote Link to comment
Acheron4171 Posted January 27, 2023 Author Share Posted January 27, 2023 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. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.