Hi folks,

First of all a short resumé of what has been done, what has happened:

Phase 1

- a while ago, somewhere between 1 and 2 months ago, I started out with my first Unraid system (trial)

- I first ran it on a Intel NUC that had a Addonics 4 disk housing connected using simple usb. Everything ran quite ok, a lot of getting used to but nothing special there.

- I wanted to try and start Docker, but that was not possible, message: Docker Service failed to start

At that time I thought it was maybe due to the NUC, not being capable or? But in fact I did not know.

Phase 2

With the summer sale, I wanted to buy a couple of Unraid licenses, but that turned out to be more difficult than I had imagined..
I'm still trying to purchase an upgrade to upgrade my starter to unleashed or lifetime.. but up to now it did not work..

 

I had also decided to move the Unraid install (usb boot disk + 4x 16 TB hard drive, no cache yet) to a 2019 or 2020 Medion PC. 

- upgraded the Medion PC with 64 GB of ram

- inserted a PCIe X1 esata card and connected the Addonics 4 disk housing using esata

- had quite some trouble getting Unraid up and running but in the end using Tools > New Config and then checking keep all (Array slots and Pools slots) it worked out and I got Unraid up and running.

 

Time for Docker once again..

- Docker Service failed to start

I also got a couple of disk errors and looking at the logs, I assume these are due to esata, so I reverted the Addonics 4 disk housing back to usb instead of esata. Again did the new config trick and Unraid and its shares are up and running with no problem.

 

Did some searching and read that Docker needs it's own share "appdata" so I created that, but still Docker fails to start.

Then I tried to also delete the Docker vDisk location /mnt/user/system/docker/docker.img but this did not help either.

 

Here's a short System Information:

Model:	Custom
M/B:	MEDION B550A4-EM Version 1.0 s/n MH9301G93003222
BIOS:	American Megatrends Inc. Version 550A4W0X.101 Dated 07/09/2019
CPU:	AMD Ryzen 5 2600 Six-Core @ 3400 MHz
HVM:	Enabled
IOMMU:	Enabled
Cache:	L1 - Cache: 576 KiB, L2 - Cache: 3 MiB, L3 - Cache: 16 MiB
Memory:	64 GiB DDR4 (max. installable capacity 128 GiB)
Network:	bond0: fault-tolerance (active-backup), mtu 1500
Kernel:	Linux 6.1.99-Unraid x86_64
OpenSSL:	1.1.1v

 

Any help to get Docker started and going, or any pointer most welcome!!

 

I think / hope I solved my own issue:

While I was examining Docker related settings (I know little or nothing about them..) I noticed that > Settings > Docker showed the Docker data-root as btrfs vDisk.

Since all my drives are xfs, I changed the setting of data-root accordingly from btrfs to xfs and Tada!! Docker started to work!

27 minutes ago, panini said:

Since all my drives are xfs, I changed the setting of data-root accordingly from btrfs to xfs and Tada!! Docker started to work!

That wouldn't have been your problem.  Glad it's working, but as a vdisk (btrfs or xfs) sitting on an xfs drive it doesn't matter.  Diagnostics from when it wasn't working would have said why, but its irrelevant now

On 9/1/2024 at 5:44 PM, Squid said:

That wouldn't have been your problem.  Glad it's working, but as a vdisk (btrfs or xfs) sitting on an xfs drive it doesn't matter.  Diagnostics from when it wasn't working would have said why, but its irrelevant now

Thanks for replying, will read up and see if I can trace something to learn what was wrong.