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.

7.0 Update- Docker Service Won't Start..

Featured Replies

Hi all, just updated to 7.0 .. My frist issue was that the Cache pool configuration was now invalid. I fixed that by deleting and recreating the pool, but now my Docker Service won't start. Not even sure where to start on this one. Help! What is dmsg(1)? says it might have more informatin.

 

Jan 11 10:32:32 UR-HomeServer ool www[21128]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
Jan 11 10:32:32 UR-HomeServer emhttpd: Starting services...
Jan 11 10:32:33 UR-HomeServer emhttpd: shcmd (139): /etc/rc.d/rc.samba reload
Jan 11 10:32:33 UR-HomeServer emhttpd: shcmd (143): /etc/rc.d/rc.avahidaemon reload
Jan 11 10:32:33 UR-HomeServer avahi-daemon[1737]: Got SIGHUP, reloading.
Jan 11 10:32:36 UR-HomeServer ool www[21482]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
Jan 11 10:32:36 UR-HomeServer emhttpd: Starting services...
Jan 11 10:32:36 UR-HomeServer emhttpd: shcmd (150): /etc/rc.d/rc.samba reload
Jan 11 10:32:36 UR-HomeServer emhttpd: shcmd (154): /etc/rc.d/rc.avahidaemon reload
Jan 11 10:32:36 UR-HomeServer avahi-daemon[1737]: Got SIGHUP, reloading.
Jan 11 10:32:37 UR-HomeServer emhttpd: shcmd (162): /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 32
Jan 11 10:32:37 UR-HomeServer kernel: loop3: detected capacity change from 0 to 67108864
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS: device fsid 7491084b-4d8a-40d1-a497-b147cdf3d06c devid 1 transid 184842 /dev/loop3 scanned by mount (21651)
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS info (device loop3): first mount of filesystem 7491084b-4d8a-40d1-a497-b147cdf3d06c
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS info (device loop3): using free space tree
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS error (device loop3): bad tree block start, mirror 1 want 22109929472 have 3181288440457736952
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS error (device loop3): bad tree block start, mirror 2 want 22109929472 have 15680564271484292426
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS error (device loop3): failed to read chunk root
Jan 11 10:32:37 UR-HomeServer root: mount: /var/lib/docker: can't read superblock on /dev/loop3.
Jan 11 10:32:37 UR-HomeServer root:        dmesg(1) may have more information after failed mount system call.
Jan 11 10:32:37 UR-HomeServer kernel: BTRFS error (device loop3): open_ctree failed
Jan 11 10:32:37 UR-HomeServer root: mount error
Jan 11 10:32:37 UR-HomeServer emhttpd: shcmd (162): exit status: 1

 

Solved by trurl

  • Community Expert

Pool has issues, one of the devices dropped offline in the past:

 

Jan 11 10:25:42 UR-HomeServer kernel: BTRFS info (device sde1): bdev /dev/sde1 errs: wr 89861006, rd 174026, flush 329362, corrupt 42, gen 0

 

Run a correcting scrub and post the results

 

But in any case, you will need to recreate the docker image after.

  • Author

Scrub results:

UUID:             1783b43b-6693-45f5-9201-334d8e942e86
Scrub started:    Sat Jan 11 11:02:59 2025
Status:           finished
Duration:         0:15:37
Total to scrub:   719.94GiB
Rate:             786.79MiB/s
Error summary:    verify=41088 csum=3489528
  Corrected:      3530616
  Uncorrectable:  0
  Unverified:     0

 

Do I just run this procedure to replace the image file?  

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

  • Community Expert
  • Solution

Yes, and then continue with the next part in the docs about reinstalling your containers from Previous Apps.

I have the same issue, everything worked fine previously. 

  • Community Expert
18 minutes ago, eduardthethird said:

I have the same issue, everything worked fine previously. 

Diagnostics?

  • Community Expert
7 hours ago, eduardthethird said:

annoying to re-install all dockers again

Did you use Previous Apps on the Apps page?

Yes, I did, but I've been running this Unraid server for many years and there are loads that I do not use anymore in the list. It is also difficult as I have used multiple versions of certain databases and must figure out what I decided to use for each application. Luckily this option is available, but I've never experienced issues like this for many years, I always upgrade to whatever is the latest version of Unraid, first time having this bad luck.

My system went unresponsive overnight and I had to do a hard reboot. Docker is running, but all the previously installed containers are gone again, and no apps are running.

image.thumb.png.fcc33a2448a2928ce02d45bec19940fe.png

I'm going to reinstall apps again, and monitor it. 

Added diagnostics as requested.

neem-diagnostics-20250113-0920.zip

Edited by eduardthethird

  • Community Expert

Why do you think you need 300G docker.img?

 

Your system share has files on the array.

  • Community Expert

How many parity sync errors do you have so far? Why do you have any?


The good news is that it is still up and running after the second reinstallation!

I've set it to cache first and array second but I changed it now to SSD only. Probably my mistake, thanks for checking!

It is still running:

Total size:6 TB

Elapsed time:23 hours, 40 minutes

Current position:4.70 TB (78.3 %)

Estimated speed:1.5 MB/sec

Estimated finish:10 days, 1 hour, 30 minutes

Sync errors corrected:78687


I ran out of docker space at one time as I run loads of containers, including Ollama local models, databases, caches etc:
image.thumb.png.c20efafed45aa25a9d30189f2f3b6319.png

Edited by eduardthethird

For anyone else having this problem, for me the issue was that after the upgrade I had to re-create the pool due to the invalid expansion error.  When I did this, I left the name as the default "cache", but the old pool name was something different.  This resulted in the path to the docker.img being invalid.  I renamed the pool and all was good again.

  • 1 month later...

My Docker will not run and I see an error from Fix Common Problems that my Cache is Read Only. I checked the permissions, and everything seems ot be set to Read/Write.

Not sure what to do next.

The "Recreate Docker Image File" instructions will not work because it can't access the Cache to delete the file.

Attached is my DIagnostic file.

 

homenet-unraid-diagnostics-20250305-1423.zip

  • Community Expert

There were some write errors to both pool devices in the past, and now there's some critical filesystem corruption:

 

Mar  5 14:20:33 Homenet-Unraid kernel: BTRFS critical (device sdb1): corrupt leaf: block=2036130365440 slot=47 extent bytenr=2445737984 len=4096 invalid data ref root value 8695201835243274245
Mar  5 14:20:33 Homenet-Unraid kernel: BTRFS error (device sdb1): read time tree block corruption detected on logical 2036130365440 mirror 1
Mar  5 14:20:33 Homenet-Unraid kernel: BTRFS critical (device sdb1): corrupt leaf: block=2036130365440 slot=47 extent bytenr=2445737984 len=4096 invalid data ref root value 8695201835243274245
Mar  5 14:20:33 Homenet-Unraid kernel: BTRFS error (device sdb1): read time tree block corruption detected on logical 2036130365440 mirror 2

 

I recommend backing up and re-formatting it.

Thanks for the information. I can't seem to be able to back up what is on the drive. Any insight on how to best accomplish this?

I finally got it working. Thanks everyone.

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.