I recently move my unraid to new hardware, however I've been having difficulties. Docker containers would take at least an hour to start all 20 ish, and then they started to randomly stop and remove themselves. I've deleted the docker.img to try and start again in-case it happened to be corrupted and nothing has really changed, docker is still very slow and having weird issues, when editing the container it would error on trying to stop it and then delete it when it tried to start it. I have just tried changing the docker setup to (directory/overlay2) and now it won't even start, diagnostics are attached

diagnostics-20250709-1049.zip

Edited July 9, 2025Jul 9 by ThunderLord96

I'm trying the docker.img of xfs type, and it seems to have the same slowness issue I saw in the other type.

There are constant USB issues logged, may not like the UASP driver, but note that USB is not recommended for array or pool devices. Post the output of lsusb -vt

This is the output of that. I thought it might have something to do with the hdd bay I got, it does support S.M.A.R.T. at least, the computer I'm using now doesn't exactly have SATA ports so that's why I thought I would get one...

I'm not currently at home, but when I get back I'll try reseating all of the hdds in the bay and the cables connecting them, then boot them back up hoping for a change. If there isn't anything I can do remotely

Edited July 9, 2025Jul 9 by ThunderLord96
Context

If it helps at all, the new hardware is a mini pc (GMKtec Mini PC Workstation, Intel Core i9 13900HK(14C/20T), with 2x500GB m.2 drives) and the Hard Drive Bay (Mediasonic USB 3.2 Type C 8 Bay 3.5-inch Hard Drive Enclosure, currently 6 HDDs, 5x16tb and 1x4tb filling slots 2-7)

Edited July 9, 2025Jul 9 by ThunderLord96
Hard Drives

Click on the flash drive, scroll down to the Syslinux configuration section, make sure Menu View is enabled, top-right, and add after /bzroot to the default boot option, the one in green:

usb_storage.quirks=174c:1356:u

It should be added to the same line as /bzroot, just leave a space between that and the kernel option, like the example below but with the IDs above, then reboot and retest.

I have added as shown and am now rebooting, thanks so much for the help so far JorgeB :)

I have managed to change to directory/overlay2 and docker+unraid is running much faster now! I'm no longer getting any errors either when editing containers and r/w times seem way better as the parity is building much faster. Thank you so much! I certainly wouldn't have found out how to fix that. I will continue to monitor the logs for a bit to see if the problems re-emerge

For anyone using this as reference, I strongly recommend you to make your own DIY NAS, the hdd enclosure was giving me disconnection issue and now half of it has simply stopped working. I'm returning it and the mini computer today and have already ordered a Tower Case that has x10 Slots for HDD dedicated with plenty of space to stack in the front. If I ever need to add anymore I can simply get a PCIEx1 to SATA ports which I already have one card for. All you really need to make your own is a motherboard with good I/O, a CPU with Cooler, Memory, and a way to cool the HDDs such as an enclosed case with fans. If buying intel make sure not to get a F cpu as that means it doesn't have any integrated graphics and you will have to supplement a gpu if needed for any reason. This is my current part list for my DIY NAS excluding the drives I already have (you can find cheap refurbished ones online), please note this is not the best build and the cpu is most likely overkill, however I like having plenty of compute power and plan to run single core intensive services such as a Minecraft server. And the good news is that buying this is actually cheaper than what I was trying to use and has better performance! So please, when someone tells you that USB Enclosures are difficult to use and are more likely to have problems, try to listen to them

Edited July 10, 2025Jul 10 by ThunderLord96
Clarify