Monitoring restart - Unable to read filesystem

    Good morning everyone!


    Since a few days at system startup I get this emails:


    After about 1 minute I get these two other emails:


    The mountpoint is always the same and it's used by a PLEX docker.

    This forces me to reboot the docker every day to get it started and be able to use it away from home.


    Is anyone able to give me a solution to solve the problem permanently?


    Thank you very much to those who will help me.


    Have a good Sunday! :*
    Davide

    Quote from shecky66

    The mountpoint is always the same and it's used by a PLEX docker

    Maybe docker is starting sooner than the mount point is available.

    You can try to make a delay on docker service to start after it.


    Post
    RE: Syncthing Container stopped working: need help with diagnosis
    to delay the start of docker by 30s

    systemctl edit docker.service

    and paste this
    (Code, 3 lines)

    save and close the editor

    Might be worth a try.
    macom


    Looking at your outputs, it took 2:30 minutes for the system to see the mount point as OK, so make a delay of 3 minutes (180 seconds) on docker.


    Also, if your install is somewhat old, maybe the docker doesn't have the "wait all mounts" conf.


    Post the output of:

    ls -al /etc/systemd/system/docker.service.d/



    And please, don't mask UUIDs of the drives.

    Noone will hack you with disks IDs.

    Hi Soma and thanks for your reply.


    The output of ls -al /etc/systemd/system/docker.service.d/ is this:

    Code
    totale 12
drwxrwxrwx  2 root root 4096 15 set  2024 .
drwxr-xr-x 25 root root 4096  6 apr 13.21 ..
-rw-r--r--  1 root root  253 15 set  2024 waitAllMounts.conf
    Quote

    And please, don't mask UUIDs of the drives.

    Noone will hack you with disks IDs.

    Sorry, you're right but I'm a little obsessed with security... :P :P :P

    Hi Soma .


    waitAllMounts.conf exist.


    I followed @macom's directions that you linked and modified the docker.service file by setting a delay of 3 minutes (180 seconds).


    Code
    [Service]
ExecStartPre=/bin/sleep 180
StartLimitIntervalSec=300s


    I rebooted but the problem remains.


    Any other suggestions?

    Sorry, no.


    Just confirm that the drive is mentioned on the waitAllMounts.conf:

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


    You can try to redeploy the monit service or reinstall docker to see if it clears

    omv-salt deploy run monit


    OMV GUI -> Services -> Compose -> Settings -> Reinstall Docker


    Be aware that if you have any special edits on the daemon.json file (using nvidia GPU, for eg) , if you reinstall docker, make sure that it will stay the same.

    My daemon.json is this:

    Code
    {
  "data-root": "/var/lib/docker"
}


    By performing reinstallation of the monitoring service or docker, I should not lose any current configuration, right?

    Because I have 5 active containers and I don't want to have to reconfigure all of them....


    Thanks again.

    Quote from shecky66

    performing reinstallation of the monitoring service or docker, I should not lose any current configuration, right?

    It will use the same config.

    Quote from shecky66

    Before reinstalling Docker it is advisable to stop all containers, right?

    Not needed but its up to you.


    If you have the YMLs of the containers and the volumes are on seperate drives, you can always redeploy them

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login