[Docker Service failed to start help]

no overclocking, but older ram. thanks for all your help. I'm gonna buy replacement ram. 

[Docker Service failed to start help]

Running memtest now at least 200 errors. I guess I need new ram?

[Docker Service failed to start help]

1 minute ago, trurl said:

We'll come back to your shares and docker.

 

First order of business

 

 

just seeing this will do. 

[Docker Service failed to start help]

21 minutes ago, JorgeB said:

Jan  6 05:32:29 Mercury kernel: BTRFS error (device nvme0n1p1): block=544174866432 write time tree block corruption detected

 

Run memtest, btrfs detected corruption before writing metadata to the device, this is usually bad RAM, or other hardware problem.

If a hardware problem how can I pinpoint if it's RAM or the drive? That error on the nvme is the main cache drive does that mean it is the broken bit? 

 

[Docker Service failed to start help]

22 minutes ago, trurl said:

Those diagnostics still show 400G docker.img mounted, which it shouldn't be because Docker isn't enabled.

 

system share still has files on disk1, but it can't be that docker.img, since you don't (and didn't) have docker.img configured to be in the system share like it usually is and instead it is in the root of cache. Not necessarily wrong but there are some advantages to putting it in system share.

 

What do you get from the command line with this?

ls -lah /mnt/cache/system

and this?

ls -lah /mnt/disk1/system

 

 

Sorry if this is a duplicate I had issue posting...This is what I got for running these commands.

 

root@Mercury:~# ls -lah /mnt/cache/system
total 16K
drwxrwxrwx 1 nobody users  48 Jan  7  2022 ./
drwxrwxrwx 1 nobody users 136 Jan  1 04:30 ../
drwxrwxrwx 1 nobody root  142 Apr  4  2021 custom_ovmf/
drwxrwxrwx 1 root   root    0 Apr 17  2022 docker/
drwxrwxrwx 1 root   root    0 Jan  7  2022 libvirt/
root@Mercury:~# ls -lah /mnt/disk1/system
total 0
drwxrwxrwx  3 nobody users  21 Jan  7  2022 ./
drwxrwxrwx 17 nobody users 318 Jan  8 22:45 ../
drwxrwxrwx  2 root   root   25 Jan  7  2022 libvirt/
root@Mercury:~# 
 

 

 

[Docker Service failed to start help]

Hey thanks very much for you r response and help!

 

The mover took a while. I'm unsure why I had a docker image that large. I've done what you've said, made the docker.img setting smaller to 20GB and you can see attached diagnostics. I have not restarted VM manager or docker yet. 

mercury-diagnostics-20230109-0857.zip

[Docker Service failed to start help]

Hi all,

 

My docker service has crashed and won't restart. I get the following error: 

 

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

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712
Couldn't create socket: [111] Connection refused
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 967

 

 

I have tried going into settings -> docker and enable docker no then yes to restart the service and I get the same error.  

 

I haven't changed anything recently with the server so I don't think I changed anything to cause this to happen. 

 

I appreciate any help I have attached diagnostics. 

mercury-diagnostics-20230108-2300.zip