Hi,

 

I just upgraded to 7.0.1 and got this error. I updated to 7.0.0 a couple of weeks a go without any issue. I've tried downgrading to 7.0.0 again but docker still didn't want to start so upgraded to 7.0.1 again to fix forward. Not sure how to troubleshoot this, any help is appreciated.

 

Feb 25 18:24:02 Nassie avahi-daemon[2113]: Got SIGHUP, reloading.
Feb 25 18:24:02 Nassie unassigned.devices: Updating share settings...
Feb 25 18:24:02 Nassie unassigned.devices: Share settings updated.
Feb 25 18:24:03 Nassie emhttpd: shcmd (337): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 100
Feb 25 18:24:03 Nassie kernel: loop2: detected capacity change from 0 to 209715200
Feb 25 18:24:03 Nassie kernel: BTRFS: device fsid 78bb5bf8-dda0-4f88-bd7d-1bb567fafd86 devid 1 transid 973979 /dev/loop2 scanned by udevd (15759)
Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): first mount of filesystem 78bb5bf8-dda0-4f88-bd7d-1bb567fafd86
Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): using free space tree
Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): level verify failed on logical 14558167040 mirror 1 wanted 2 found 0
Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): level verify failed on logical 14558167040 mirror 2 wanted 2 found 0
Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): failed to load root extent
Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): open_ctree failed: -5
Feb 25 18:24:03 Nassie root: mount: /var/lib/docker: can't read superblock on /dev/loop2.
Feb 25 18:24:03 Nassie root:        dmesg(1) may have more information after failed mount system call.
Feb 25 18:24:03 Nassie root: mount error

nassie-diagnostics-20250225-1837.zip

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

 

Your system share has files on the array.

Hi Trurl,

 

Thank you for your reply, I really appreciate it.

 

I have some Ollama and other AI containers that take a lot of space. Is there a better way to do it? 

 

Should I make the system share as dedicated as I did with appdata?

Your domains share also has files on the array.

 

Nothing can move open files. Disable Docker and VM Manager in Settings.

 

Then, run mover, wait for it to finish, post new diagnostics

Disabled those settings and ran mover. Docker still won't start.

 

Thank you so much for helping out.

 

nassie-diagnostics-20250225-2031.zip

Edited February 26, 20251 yr by NorseRider
added stuff for clearlity

Not sure if there are still files on the array or not, maybe only folders as files show cache only.

This is my settings for system share, guessing i miss configured something there?]

 

system and domains shares still have files on the array.

 

Mover won't replace files, so if there are duplicates you will have to clean those up yourself.

 

You will need to recreate docker.img and reinstall from Previous Apps.

 

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

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

 

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

 

 

Thank you so much for your reply.

 

I will recreate and reinstall.

 

What are the best settings for primary and secondary storage for system and domain? Should those shares be cache only?

 

Thank you.

30 minutes ago, NorseRider said:

Should those shares be cache only?

Assuming they won't run out of space that way. I have mine on another pool that isn't used for caching. Used space on that pool doesn't change much.

Recreated the docker.img file on my apps pool instead. Previous apps made it a breeze to reinstall my docker apps.

 

Thank you so much for your help Trurl, really appreciate it.