relink2013
commented
2 weeks ago Fellow Unraid user here. I've been learning my way around this recently too, so maybe i can help.
your docker log is showing an error on a volume formatted as EXT2-fs, i'm not sure what that is, virtual DSM has its boot image which is EXT4 and then your actual volume that DSM uses is btrfs... so that's odd.
Did you just go with the containers default of using a single virtual disk image?
If so that means it's now trying to run the entire Synology OS "DSM" from your Unraid array, Which it's not designed to do. you'll actually get performance slower than a single HDD because it's calculating parity non stop, while only reading and writing on a single HDD.
I'd try moving it back to your cache and seeing if it works again. Either way id highly suggest using multiple disk images. Set the first one as cache only, subsequent ones as array only. store your data on the other volumes, leaving volume 1 to handle the OS, etc...
phillipunzen
Operating system
Unraid (Latest Version)
Description
Hello! I installed my Virtual Diskstation on my Unraid server as a Docker. To test it, I had the data in the cache (NVME) and now I wanted to push the data to the array (HDD). I created a share that only writes to the array. And when I start the container, I get the error messages from the screenshot. Permissions are correct so far. What can I do to make the container start correctly?
Docker compose
Unraid Configuration
Docker log
Screenshots (optional)
No response