Docker keeps going offline

[RLA113]

I have tried to read-up on what might be happening. It appears that maybe my cache is corrupted? But I have a hard time diagnosing that is the problem. The message I get in the docker tab is this:

[[

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

]]

 

When I download the diagnostics, it appears that everything is okay, except that the cache drive is in a read-only mode. Not sure how it got that way though. 

 

Any help would be appreciated. Attached the diagnostics.

 

jarvis-diagnostics-20221130-0656.zip

[Squid]

2 minutes ago, RLA113 said:

cache drive is in a read-only mode.

That's why you're having the issues.  @JorgeB will advise on how to fix the corruption

[JorgeB]

Btrfs is detecting data corruption, start by running memtest.

[RLA113]

Awesome, thank you for the advice, I did have a dimm that failed memtest. Other dimm passed. Have the cache drive in read only mode still. Not sure if the memory corrupted it.

[trurl]

2 minutes ago, RLA113 said:

I did have a dimm that failed memtest

What did you do about it? You must never run any computer unless RAM is working perfectly. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded in RAM.

 

[JorgeB]

6 minutes ago, RLA113 said:

Not sure if the memory corrupted it.

Run a scrub, but most likely there's some data and/or filesystem corruption, I would suggest backing up and reformatting the pool, after the memory issue is solved of course.

[RLA113]

15 minutes ago, trurl said:

What did you do about it? You must never run any computer unless RAM is working perfectly. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded in RAM.

 

Agreed, corrupted RAM should never be used. I took the corrupted dimm out. Running on only a single channel right now, until my order shows up. Then I will remove the single channel and add the two new sticks. Going to see if I can RMA the memory sticks, only got it in September.

[RLA113]

15 minutes ago, JorgeB said:

Run a scrub, but most likely there's some data and/or filesystem corruption, I would suggest backing up and reformatting the pool, after the memory issue is solved of course.

Sounds like a good plan. Backup up what little I have on the drive. I already back up the AppData once a week in case of this failure. Then I will run a scrub. If that does not work, I will reformat. Thank you again for all the help!