Settings>Docker, select Yes, set the image to 10gb, and point it to "/mnt/disk2/domains/docker.img". When I hit Apply I see "Starting Docker..." in the bottom left which disappears after a few seconds. Nothing else happens.

 

Here's the log...

 

Apr 26 01:07:20 Tower emhttpd: shcmd (697): /usr/local/sbin/mount_image '/mnt/disk2/domains/docker.img' /var/lib/docker 10
Apr 26 01:07:20 Tower kernel: BTRFS info (device loop3): disk space caching is enabled
Apr 26 01:07:20 Tower kernel: BTRFS info (device loop3): has skinny extents
Apr 26 01:07:20 Tower root: Resize '/var/lib/docker' of 'max'
Apr 26 01:07:20 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 21474836480
Apr 26 01:07:20 Tower emhttpd: shcmd (699): /etc/rc.d/rc.docker start
Apr 26 01:07:20 Tower root: starting dockerd ...
Apr 26 01:07:35 Tower emhttpd: shcmd (701): umount /var/lib/docker

 

tower-diagnostics-20210426-0111.zip

Did you already have docker enabled and now you are trying to change its size and/or location?

 yes, the docker enabled before, and couldn't start after  reboot. I try many times to change its size and location but still not on.

Cant remeber the default setting for the docker now😅

And ideas ？ thx

Try disabling the service (Settings - Docker), then delete the image.  Then reboot

 

Then after starting the array, re-enable the service and if it still doesn't restart post a new set of diagnostics.

 

 

Folow the steps,    disable the docker, delete img, then reboot, enable the docker   but  still not working, try disable and re-enable again just the same. 

 

heres the log

 

 

tower-syslog-20210426-1416.zip

1 minute ago, obs6 said:

heres the log

but not

1 hour ago, Squid said:

a new set of diagnostics.

 

my mistake

 

here's the diagnostics 

 

tower-diagnostics-20210426-2227.zip

Not likely the cause of your issue, but why are you trying to put docker.img on the parity array?

 

Normally you want appdata, domains, system shares on cache and set to stay on cache. If these are on the array, disks will stay spunup since there are always open files, and docker/VM performance will be impacted by slower array.

yep, I know these.

 As I see, the cache would move to the parity array disks finally. And the disk1 is ssd disk, I just simply put it on the ssd one, which one has many all time online VMs run on it, so dont care the disk spin up

Apr 26 22:11:53 Tower emhttpd: Pro key detected, GUID: 5..7 FILE: /boot/config/BTRS.key

Possible that running a cracked version of the software may be causing you issues.

you mean the unraid with the cracked key? I'll check this with the re-seller. 

Hope that's the reason  

7 hours ago, obs6 said:

cache would move to the parity array disks finally.

Only if you set the user share to cache-yes. The usual way to handle this is to make the share cache-only or cache-prefer. Then it won't be moved from cache.

 

7 hours ago, obs6 said:

disk1 is ssd

Missed that. SSDs in the array can't be trimmed. Can't really see any good reason for putting it in the array and you don't even have parity so it's not like it is protected there.