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 Service failed to start, Rebooting Temporarily Fixes it

Featured Replies

Hi All,

 

For some reason, Docker keeps crashing. After reviewing the system logs, the main thing that stands out is:

 

Oct 6 03:41:04 HS kernel: BTRFS error (device sde1): block=1077952512 write time tree block corruption detected Oct 6 03:41:04 HS kernel: BTRFS: error (device sde1) in btrfs_commit_transaction:2466: errno=-5 IO failure (Error while writing out transaction) Oct 6 03:41:04 HS kernel: BTRFS: error (device sde1: state EA) in cleanup_transaction:1964: errno=-5 IO failure Oct 6 03:41:05 HS kernel: loop: Write error at byte offset 992399360, length 4096.

 

I'm assuming the device sde1 is my main cache drive, since the path is /dev/sde in system devices, so could it be a faulty drive?

 

I attached my diagnostics. I'll keep digging around and post a solution if I find one.

 

Thanks!

 

**Edit**

I cleared my logs and stopped / restarted docker. For some reason the docker.img is in use and terminates the start.

Oct 6 08:53:32 HS emhttpd: shcmd (328): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 100

Oct 6 08:53:32 HS root: '/mnt/user/system/docker/docker.img' is in-use, cannot mount

Oct 6 08:53:32 HS emhttpd: shcmd (328): exit status: 1

hs-diagnostics-20231006-0845.zip

Edited by preventive-dungeon1911

Solved by JorgeB

  • Community Expert
  • Solution

The pool filesystem went read-only, and this error:

 write time tree block corruption detected

can indicate a RAM issue, so good idea to run memtest.

 

There are also macvlan call traces, change the docker network to ipvlan.

  • Author

Set the network to ipvlan and memtest is running. Memtest is on its 3rd pass with 0 errors.

  • Author

So I ran memtest for a day or so and nothing failed. However, after changing the docker network to ipvlan and removing a potentially faulty array hard drive, everything is good again.

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.