Posts by johnnyb

Quote from geaves

That should not be necessary, I have this currently on OMV4 and the option nofail is not included in the mergerfs mount point and it should not be necessary what trapexit it pointing out is that if the individual drives already have nofail, which in OMV they do, then mergerfs will mount. If a drive does not have that or fails then the megerfs will not mount.

I have the same microserver with mergerfs and snapraid and it runs flawlessly, I have also tried and tested OMV5 in a VM with mergerfs and snapraid setting it up exactly as it is on my OMV4 and I've not needed to add that option, it does what says on the tin.

My snapraid/mergerfs/luks setup was similarly flawless on OMV4, it's only been since the move to OMV5 these boot issues have started. I suspect it was the nofail flag all along (and not the encrypted drives) that caused initial issues.

The last boot fail came after I did a hard reset due to the system stalling on a large file size copy between two drives- the source drive subsequently dropped from OMV.

No issues since nofail flag. Can't explain it, but moving on to learning how to balance my media folder between old and new drives.

For others out there and my own memory when I need to do this again- the solution was adding nofail to the mergerfs fstab entry.

Got it from here- https://www.reddit.com/r/OpenM…1/mergerfs_drive_failure/

So looks like a fstab issue- the mergerfs filesystem is failing the boot.

The drives it points to were encrypted through CLI though unlocked through OMV GUI, perhaps that’s the issue. I’ll wipe everything and start again.

Further relevant info- I manually partitioned the USB in the Debian install as it was below threshold capacity for auto partition.

10GB /, 4GB swap.

I have a Proliant N54L with BIOS hack unlocking 5th drive. Was running OMV4 over Debian on a partitioned SSD without issues. 5x HDD with luksencryption (unlocking with a file).

Tried to upgrade to OMV5 but that failed so went with a fresh install, same setup but installing over Debian to a 16Gb USB (tried OMV ISO but presume the flash drive is too small for direct install).

All good, set everything up, installed Extras and Docker etc, but on first reboot after being able to load GUI I can’t boot. Have tried fresh install again, same result. Tried with updated kernel, still the same.

The error is-

You are in emergency mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” or “exit” to boot into default mode.

The red errors in journalctl -xb are-

Base address is zero, assuming no IPMI interface

ERST: Failed to get Error Log Address Range

APEI: Can not request [mem 0xdfab6a3] for APEI BERT registers

usbhid 1-3.1:1:1: couldn’t find an input interrupt endpoint

sd 6:0:0:0 [sda] No caching mode page found

Sd 6:0:0:0 [sda] Assuming drive cache: write through

Opemmediavault.local blkmapd[290]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

Opemmediavault.local kernel: kvm: disabled by bios

Opemmediavault.local systemmd[1]: Timed out waiting for device /dev etc (all the HDD drives)

Opemmediavault.local nfsdcltrack[475]: Failed to init database: -13

And the last message is -

The process /bin/plymouth could not be executed and failed. The error number returned by this process is ERRNO.

Help? Thanks.

Same- very useful.

Unfortunately took me a while to find out why my Plex wasn't working, let alone finding this thread for a solution, so ended up rebuilding my Plex library about 5 times.

Manual match fixing is not fun 5 times.

Another update from me- ended up abandoning encrypted system drive and everything seems to be working OK with a dedicated docker user/group.

Even having an encrypted partition only for the config files meant settings weren't saved on reboots- it was just too complicated.

Update from me- think I sorted it.

Not surprisingly it was probably my error all along in the end. With PUID/PGID I had created new users for the specific containers (plex, sonarr etc) under the group 'media', in an attempt to separate out users.

I changed this to my default user and group and have rebooted after loading each container- docker survives.

Thanks again ryecoaaron.

Quote from ryecoaaron

That was just a guess. You could try other targets like multi-user.target

Thanks for spending time on this ryecoaaron- appreciate it.

I reinstalled with GUI after going through the motions manually removing and cleaning up (sorry didn't record the errors).

Docker survives reboots when I have no containers loaded. As soon as I run an image, it doesn't survive a reboot.

Quote from ryecoaaron

No but it would look something like:
sudo nano /etc/systemd/system/docker.service.d/override.conf
add these lines:
[Unit]
After=local-fs.target

No luck unfortunately, same errors.

Trying to uninstall the plugin via GUI again just seems to break things.

Quote from ryecoaaron

Sounds like docker is starting before you unlock the filesystem. Try adding a systemd override file that makes the docker service wait for the local filesystem.

Thanks for the post ryecoaaron, have you got a link to help me through creating such a file?

Also- is there any significance to these error messages-

Your kernel does not support swap memory limit
Your kernel does not support cgroup rt period
Your kernel does not support cgroup rt runtime

bumping- any ideas?

Three fresh installs, running into the same errors each time.

Docker plugin never survives a reboot.

Update- got impatient so though I'd just reinstall.

Bad idea- incomplete uninstall via OMV, locked apt-get, manual reboots and apt remove are also unsuccessful.

Something bad seems to have happened- this is the error on reinstall-

Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
* docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2018-06-09 23:50:59 AWST; 11ms ago
     Docs: https://docs.docker.com
  Process: 3563 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 3563 (code=exited, status=1/FAILURE)
      CPU: 51ms


Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Main process exited,…URE
Jun 09 23:50:59 n54ldebian9 systemd[1]: Failed to start Docker Application C…ne.
Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Unit entered failed …te.
Jun 09 23:50:59 n54ldebian9 systemd[1]: docker.service: Failed with result '…e'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openmediavault-docker-gui:
 openmediavault-docker-gui depends on docker-ce; however:
  Package docker-ce is not configured yet.


dpkg: error processing package openmediavault-docker-gui (--configure):
 dependency problems - leaving unconfigured


Errors were encountered while processing:
 docker-ce
 openmediavault-docker-gui

I had docker working perfectly with plex etc- no dramas.

I've got luks encryption so followed some guides using dropbear to remote unlock- that is working now too.

But now docker isn't working- I can't quite work out the connection between the two- this is the error

Error #0:
OMVModuleDockerException: Error: "Operation timed out after 30001 milliseconds with 0 bytes received" - Code: 28 in /usr/share/omvdocker/Utils.php:73
Stack trace:
#0 /usr/share/omvdocker/Utils.php(196): OMVModuleDockerUtil::doApiCall('http://localhos...')
#1 /usr/share/openmediavault/engined/rpc/docker.inc(211): OMVModuleDockerUtil::getImageList(42005, true)
#2 [internal function]: OMVRpcServiceDocker->getImages(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getImages', Array, Array)
#5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'getImages', Array, Array, 1)
#6 {main}

Along with a 'Bad Gateway' error. I had set a static IP in initramfs.conf- I deleted that and put a manual IP in my router (so I could still SSH in to unlock on a static IP), no difference.

Help please- thanks.

I'll just go ahead and update this to resolved then shall I.

And hey, I've just notice your signature.

Having troubles installing USB Backup 4.05 from plugins.

Fresh install OMV4 over Debian9.

I can only screenshot the bottom of the error because it keeps scrolling down to the bottom- won't let me scroll up to see what's happening above it.

Any help appreciated.

Having the same issue- even with the default 4G.

Fresh install of OMV4 over Debian9, have a SnapRAID pool created.

Pics attached. Error message attached.

OMV\Json\SchemaValidationException: min-free-space: The value '4G' doesn't match the pattern '/^[0-9]+[KMG]$/'. in /usr/share/php/openmediavault/json/schema.inc:481
Stack trace:
#0 /usr/share/php/openmediavault/json/schema.inc(370): OMV\Json\Schema->checkPattern('4G', Array, 'min-free-space')
#1 /usr/share/php/openmediavault/json/schema.inc(297): OMV\Json\Schema->validateString('4G', Array, 'min-free-space')
#2 /usr/share/php/openmediavault/json/schema.inc(627): OMV\Json\Schema->validateType('4G', Array, 'min-free-space')
#3 /usr/share/php/openmediavault/json/schema.inc(395): OMV\Json\Schema->checkProperties(Object(stdClass), Array, '')
#4 /usr/share/php/openmediavault/json/schema.inc(285): OMV\Json\Schema->validateObject(Object(stdClass), Array, '')
#5 /usr/share/php/openmediavault/json/schema.inc(257): OMV\Json\Schema->validateType(Object(stdClass), Array, '')
#6 /usr/share/php/openmediavault/rpc/paramsvalidator.inc(59): OMV\Json\Schema->validate(Object(stdClass))
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(178): OMV\Rpc\ParamsValidator->validate('{"name":"mediap...')
#8 /usr/share/openmediavault/engined/rpc/unionfilesystems.inc(182): OMV\Rpc\ServiceAbstract->validateMethodParams(Array, 'rpc.unionfilesy...')
#9 [internal function]: OMV\Engined\Rpc\UnionFilesystems->set(Array, Array)
#10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#11 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('set', Array, Array)
#12 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('UnionFilesystem...', 'set', Array, Array, 1)
#13 {main}

Quote from gderf

Does the sonarr user have rw access to the all the directories holding your shows?

Yeah the Sonarr user has RW to the tvshows folder, and the config folder where the posters are kept is owned by Sonarr.

Just noticed another random series that initially added correctly is now going into a refresh loop and eventually freezes Sonarr requiring a restart via command line.

Just wondering if there is any solution to this issue. I did a fresh OMV install including Sonarr- which was previously working perfectly. The new install is not able to add a number of existing series that were previously managed by Sonarr- the most obvious problem is posters not downloading and the same error (MediaCoverMapper) and an endless update loop which eventually crashes Sonarr.

Interestingly when I try to add the series fresh from TVDB the poster is still not showing for these specific series.

I'm wondering if this is a Sonarr -> TVDB interface issue rather than Sonarr on OMV, but just wondering if there was any other troubleshooting ideas.