Raid directory not available at boot for minidlna and Docker

mepi0011 · 13. Juli 2022

During the boot process, docker and minidlna are starts before the directory is available.

I have a Btrfs raid system mounted in srv/dev-disk-by-label-data. In this directory are subdirectories for my pictures and videos.

Have already tried various solutions from the internet to adjust the systemd files so that docker and minidlna are started later. Unfortunately, no success so far.

When the system has booted, I currently always have to manually restart minidlna and docker (e.g. systemctl restart minidlna).

My override.conf in /etc/system/system/minidlna.service.d currently looks like this (not working):

Code

Requires=mdmonitor.service local-fs.target dev-md0.device srv-dev\x2ddisk\x2dby\x2dlabel\x2ddata.mount
After=mdmonitor.service local-fs.target dev-md0.device srv-dev\x2ddisk\x2dby\x2dlabel\x2ddata.mount
RequiresMountsFor=/srv/dev-disk-by-label-data

Ideas what I can do to solve my problem?

geaves · 13. Juli 2022

Docker always starts after the system is up and running, always has done, for minidnla add a cron job set at reboot for it to restart

ananas · 13. Juli 2022

How often do you restart/reboot your system ?

Is it worth that effort ?

raulfg3 · 13. Juli 2022

same problem here, and same BTRFS filesystem for data ( Video), the problem is that boot disk is fastest that BTRFS Data disk, so allways dockers start before data disk are ready.

I have lot of interest of know how to solve.

PD; I have several OMV machines and this rare behaviour only hapens on system that have BTRFS data disk, not in system with ext4 data disk.

mepi0011 · 13. Juli 2022

Zitat von raulfg3

BTRFS filesystem for data ( Video), the problem is that boot disk is fastest that BTRFS Data disk, so allways dockers start before data disk are ready.

My research so far has also led me to this conclusion and I am now trying to find a solution that docker and minidlna wait until the BtrFS raid is available.

mepi0011 · 13. Juli 2022

Zitat von raulfg3

I have lot of interest of know how to solve.

I made some tests and I think following works:

Run sudo systemctl edit minidlna as admin and add following line

in to the configuration file RequiresMountsFor=/srv/dev-disk-by-label-data/<path_to_your_data>.

Save the file, close the editor and reboot the system.

For me it works but I get alway following e-mail notifications from OMV.

Code

The system monitoring needs your attention.

Host:        
Date:        Wed, 13 Jul 2022 19:52:42
Service:     filesystem_srv_dev-disk-by-label-data
Event:       Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-label-data' state

This triggered the monitoring system to: restart

—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

or

Code

The system monitoring needs your attention.

Host:        
Date:        Wed, 13 Jul 2022 19:53:13
Service:     mountpoint_srv_dev-disk-by-label-data
Event:       Status failed
Description: status failed (1) -- /srv/dev-disk-by-label-data is not a mountpoint

This triggered the monitoring system to: alert

—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Alles anzeigen

Soma · 13. Juli 2022

Zitat von raulfg3

same problem here, and same BTRFS filesystem for data ( Video), the problem is that boot disk is fastest that BTRFS Data disk, so allways dockers start before data disk are ready.

I have lot of interest of know how to solve.

PD; I have several OMV machines and this rare behaviour only hapens on system that have BTRFS data disk, not in system with ext4 data disk.

Alles anzeigen

Sorry but I never had a failed reboot with the same config:

RAID1 BTRFS data serving docker Nextcloud .

Not only the NC server but I also have another OMV serving the media BTRFS drive (16Tb on qbittorrent) and never fails reboots.

If you need some cat, I can provide you.

Just tell me what you need, 😉

macom · 16. Juli 2022

Zitat von mepi0011

During the boot process, docker and minidlna are starts before the directory is available.

If you installed docker from omv-exxtras this should be prevented for file systems that were present when docker was installed (for docker, not for minidlna).

Check if this file exists and if it contains the filesystem in question

/etc/systemd/system/docker.service.d/waitAllMounts.conf

If not, press the install docker button again in omv-extras and check again. It should be there.

raulfg3 · 16. Juli 2022

my failing system:

actually:

after push install docker button again.:

content of file is:

Code

[Unit]
After=local-fs.target srv-dev\x2ddisk\x2dby\x2duuid\x2daebef5cc\x2d71dd\x2d4a5b\x2d8372\x2da878a15b972a.mount

now is time to test if problem on PLEX dissapear.

raulfg3 · 16. Juli 2022

Thanks a lot works fine, and yes mount is my data disks.

That is the answer that i wait a lot, no need to edit files by hand.

and the sollution is as simple as reinstall docker ( pust install button again in webGUI).

Thanks one more time.

Raid directory not available at boot for minidlna and Docker

Jetzt mitmachen!

Tags