Hello,

Been on 6.12.4 for a little over a week now with no problems, but noticed today my Docker tab said, "Docker Service failed to start".

It doesn't have any errors on the docker tab

Settings > Docker




Attaching diagnostics. Would appreciate any help. 

Thanks in advance!

noumenon-diagnostics-20231207-1814.zip

The docker image is corrupt and will need to be recreated, but first run a correcting scrub on the pool and make sure all errors are corrected, one of the pool devices dropped offline in the past, see here for more info and better pool monitoring.

 

3 hours ago, JorgeB said:

The docker image is corrupt and will need to be recreated, but first run a correcting scrub on the pool and make sure all errors are corrected, one of the pool devices dropped offline in the past, see here for more info and better pool monitoring.

Done and done. Thank you. Also, apologies for creating another post - I thought I had posted to the wrong section and I tried to delete it, but clearly didn't. My bad! 

5 hours ago, JorgeB said:

The docker image is corrupt and will need to be recreated, but first run a correcting scrub on the pool and make sure all errors are corrected, one of the pool devices dropped offline in the past, see here for more info and better pool monitoring.

So, I followed the directions you outlined, and it reported some read write errors with my 1st nvme cache drive. I created a user script as outlined as well, as well as forced a reset of the stats. Then I ran a scrub and it was able to repair the errors :



I also set up a scrub schedule as I was finishing up.

About 1hr later, I got a notification (as set up from the user script) that there were errors on the cache pool again.

I ran the same commands and had this:



I followed the same steps and performed another scrub, but this time it reported no errors were found / none needed correction:



Am I okay? Or do you think there may be another underlying issue?

Thanks for your help once again.

Edited December 8, 20232 yr by rud

10 minutes ago, rud said:

Am I okay?

Should be, just reset the stats again, those are form the scrub corrections.

 

4 minutes ago, JorgeB said:

Should be, just reset the stats again, those are form the scrub corrections.

Okay, just making sure. Thank you so much!

Hello, 
Since a reboot yesterday, which took an extremely long time, the Docker Service no longer starts: "Docker Service failed to start.".

I have already created a new Docker image file, but that didn't help.

I am attaching the diagnostics file: minimax-diagnostics-20231220-1451.zip.

 

I would be very happy about help.

 

kind regards

Thomas

minimax-diagnostics-20231220-1451.zip

Try uninstalling the Connect plugin, reboot and post new diags.

Hello and thank you for your instructions!
I have uninstalled the Connect plugin, restarted the server and uploaded the current diagnostic files.

minimax-diagnostics-20231221-1051.zip

Hi,

Somewhere in the logs I saw an error message regarding /dev/sdc (external USB SSD; FTM56N325H).

I started a long test with "smartctl --test=long /dev/sdc".
The result was: "Extended offline Completed without error".

I suspected an error in the controller or in the USB plug connections.

I shut down the server, changed the USB port of the external USB SSD and restarted the server.

Everything is now running, including DOCKER.

Maybe that was the cause.

 

Greetings
Thomas

I’m also having an issue with docker not starting. Here are my diagnostics. Any help fixing this is greatly appreciated. 

tower-diagnostics-20231231-1607.zip

Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm
Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): using free space tree
Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0
Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): enabling ssd optimizations
Dec 31 13:48:58 Tower kernel: BTRFS error (device sdc1): incorrect extent count for 583105773568; counted 1348, expected 1338

This is causing the cache pool to be read-only, with the result of docker failing to start

 

Since it mentions "corrupt 3", best to initially start with running memtest from the boot menu for at least a couple of passes, since bad memory can and will cause corruption