Posts by m4tt0

Thanks, guys. I understand. I did not have Snapraid on my radar at all, until someone at kodinerds mentioned it favorably. I got the idea immediately, which is why I tried it. I may revisit it, but probably just in years from now: I have 8 hot-swap bays and four left to fill-up with (more) 6TB HDDs. I use my NAS as home server and as build machine from time to time. My sensitive information barely changes over time. I do regular backups. In server terms my needs are VERY basic. I run RAID5 to reduce potential hassle if a drive fails (happened once before), nothing more, nothing less. RAID5 will do for me at this stage.

But again, many thanks for your support and your explanations. I'm sure future readers will appreciate them as much as I did. Would still be walking in the dark without you guys. Much, much appreciated!

Brave @geaves...

I've got a 250GB NVMe SSD, just to run Debian Netinst + OMV, which is already overkill. My storage comprises 3 x 6TB WD Red drives, soon 4 as I'll be running out of space in a couple of months, but not a lot. I do have HDD slots as well as old, small hard drives left. But I feel uneasy about installing a HDD just for Docker config files. And I feel uneasy trusting Snapraid / UnionFS, when I ran into these really, really weird problems within the very first days of trying. Initializing Raid5 as I write. Old school is ok for me. I'm pretty old already...

Yeah, read it. No way I would have suspected UnionFS to be the problem. I'm still just testing my NAS so can afford to start from scratch. I think I'll go the old-school way, get rid of Snapraid / UnionFS and revert to good old SW-Raid5...

Cheers, mate. This drove me crazy the last two days.

Just cross-posted. OK, my Debian/OMV installation sits on an NVMe SSD. I should be able to store the Docker configs there as well. Just need to back them up separately. Gee, did not see that one coming. Again, many thanks!

@geaves: Followed your hint and rechecked the Snapraid and unionfs setup. Realized I had UnionFS on eMFS. Switched to MFS, rebooted, and now the Emby container runs. This does not make any sense to me and I'd be more than happy to learn why that is. So, Emby runs now, but please do let me know. In any case, many thanks for your help!

@geaves: Thanks for looking into this.

I'm running it on a newly built DIY NAS:
- MB: Gigabyte C246-WU4
- Intel Core i3-8100
- 2x16 GB Crucial DDR4, ECC RAM
- 2U SilverStone SST-RM208 rackmount case, backplane with 2x miniSAS connectors connected to the onboard SATA slots

And I use Snapraid with UnionFS.

I'm new to OMV and docker, but have successfully installed both, OMV starting from a Debian netinst installation, then Docker and also some Docker images, which run perfectly fine.
Then, I've been trying to install the latest emby/embyserver docker image on the system. I've followed the instructions, as well as the video tutorial by TechnoDadLife, but the container ends up in an endless restart loop.

Here the log file: https://pastebin.com/tj7qD0Ms

I've suspected permission issues and tried different UID, GID and GIDLIST versions, from users to root, without success. Do you have any idea how to fix it? Or is the image broken?