Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

"DOCKER failed to start"

Featured Replies

 

Hi,

I’m completely lost. My server was working perfectly for months, nothing changed, and suddenly Docker stopped working.

(Some apps are still working in the background, like qBittorrent, which is still adding files even though Docker is stopped. That’s strange.)

When I restart the server, Docker works for a while but then stops again.

I’ve already tried:

Deleting the Docker image and reinstalling the apps.

Changing the cache file system.

Moving Docker from an image to a directory.


None of this worked.

I don’t know what else to try, other than throwing the server out the window and starting from scratch...

Please, please, please save my server! Hehe.

 


 

tower-diagnostics-20250108-1657.zip

Edited by Skakrew
Grammar

Solved by JorgeB

  • Community Expert

Problems with the flash drive. Do you have a current flash backup?

  • Author

Hi

Yes i have the automatic backup, and at the moment the server seems working... but i expect docker to fail in some hour...

 

Edited by Skakrew

  • Community Expert
  • Solution

Replace the flash drive and retest, that can cause issues with docker, but if the issues with docker continue, post new diags.

  • Author
4 hours ago, JorgeB said:

Replace the flash drive and retest, that can cause issues with docker, but if the issues with docker continue, post new diags.

Ok i try today thx

  • Author
22 hours ago, trurl said:

Problems with the flash drive. Do you have a current flash backup?

Solved thx a lot

Hello all,

Here I am again. I woke up this morning, and my server was running, although inaccessible from the web.  I opened up a local connection and found that the docker failed to start. I assume after the backup last night. I did some searches, and I am running 6.12.1,4, so it isn't the 7.0 issue. (I think). Next, I tried to scrub my cache drive, and during the scrub, I noticed some temp issues (an ongoing problem with one of my cache pools; I am moving to a new build). The docker has never failed before. I placed a fan to assist in temp control and continued the scrub. (Set to repair corrupted blocks) I pulled a diagnostic while the scrub was running, and the cache drive reported that it was 55 degrees. @14% The scrub has corrected 64151 blocks ( I hope this is good.) I am going to attach three diagnostics, 20250112-1305, while the scrub is running.  Diagnostic 20250112-1329 was immediately after the scrub was completed and Diagnostic 20250112-1415 is after reboot.

 

I assume that I will need to recreate my docker image file and then reinstall the dockers, but I thought I'd get the opinion of those much smarter than I first.

 

Thanks in advance.

Chas

 

tower-diagnostics-20250112-1305.zip tower-diagnostics-20250112-1329.zip tower-diagnostics-20250112-1415.zip

  • Community Expert
14 hours ago, kysdaddy said:

The scrub has corrected 64151 blocks ( I hope this is good.) I

Post the full scrub results, after a correcting scrub.

  • 3 weeks later...

Jorge,

Thank you. This has been a bit of a ride; I apologize. I got tied up keeping systems running and didn't have time to get back to the forum. 

The semi-good news is that I think I muddled through. I ran two cache pools both redundant 1 one tb and 1 240 gb.  As a complete idiot I had all of my appdata, system, isos etc on the small pool.

That pool was overheating and failing. 

Today I moved all of the information off of that pool and onto the one tb pool. I have backed up app data, rebooted the system and everything worked as expected.

That being said, I still have errors that I do not comprehend in the system log.

these keep repeating.


Jan 29 11:43:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2882, gen 0
Jan 29 11:43:43 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 44193 off 159744 csum 0x48842079 expected csum 0x1726b2ec mirror 1
Jan 29 11:43:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2883, gen 0

 

I am attaching a diag  that I ran right after reboot and I'll go ahead and run the scrub again and post those results as well

 

UUID: cc3cc728-5d29-430f-9c0c-dcbf3ee13d23 Scrub started: Wed Jan 29 11:46:06 2025 Status: finished Duration: 0:00:00 Total to scrub: 304.00KiB Rate: 0.00B/s Error summary: no errors found

 

I assume that I did something stupid, while moving the files or setting up the share. current setup: primary storage 1tb cache, secondary array, mover cache 1tb to Array,

I feel like this is wrong.

 

Chas

 

tower-diagnostics-20250129-1136.zip.crdownload

Jorge, 

I followed the instructions, which seems to have worked. 

Thank you sir!

 

 

 

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.