Error with docker on new Openmediavault 6 install

[loladin 2]

Ive been using openmediavault and emby for years without any issues. A power serge wiped out my OS drive in my local server so i had to reinstall OMV6 on a new ssd. Installed and got docker/portainer up and running and installed a container from https://hub.docker.com/r/linuxserver/emby like i always have. The container starts no issue. The issue is i cant get into the webUI or anything. ill attach the latest log and my compose. This is a free install of everything - im leaning towards permissions but im not entirely sure where to go.

compose.txt embyserver-63829736276.txt

[Luke 42078]

Hi, did you see this?

2023-09-08 02:17:56.143 Error Main: Error in appHost.Init
	*** Error Report ***
	Version: 4.7.14.0
	Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe -restartexitcode 3
	Operating system: Linux version 6.1.0-0.deb11.11-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35
	Framework: .NET 6.0.20
	OS/Process: x64/x64
	Runtime: app/emby/System.Private.CoreLib.dll
	Processor count: 8
	Data path: /config
	Application path: /app/emby
	SQLitePCL.pretty.SQLiteException: IOError: disk I/O error - PRAGMA journal_mode

Is there a problem with the disk drive?

Look at the beginning of the log - the server is unable to get info from it's own files, then later sqlite reports a disk i/o error, so that's two pieces of software having trouble with the directory.

[loladin 2]

im not sure. i have 0 issues accessing the files or folders on the disk drive through samba share or locally on the machine itself. also other containers are having no issues accessing any of my media files - although those dont seem to use PUID or PGID in the compose setups.

Is this saying its having issues with the OS drive? the config setup is on my media pool of drives and not on the OS drive itself. 

Edited September 8, 2023 by loladin

[Luke 42078]

There are issues with the storage that is exposed to the server. Whether that's related to the volume configuration in Docker or the underlying physical drive, there's no way for the server to know that. 

How did you configure your docker run command?

[loladin 2]

Ran docker compose through portainer. The storage for the media is on 4 hdd on a single pool through mergerfs. 

 

*Edit: Thanks this got me on the right track. the previous setup had the config older directly to the HDD that its saved on - not through the mergerfs pool like the media. I think emby cannot see through the mergerfs or has permission issues. Changed just the config line to directly to the HDD and it loads up. thanks!

Edited September 8, 2023 by loladin

[Luke 42078]

Thanks for following up !