Monit alert on restart - Unable to read filesystem for btrfs raid1

  • Hello colleagues,

    I am having problems with my omv5.4.2-1 since the last update. When the system starts, I receive monit alerts about the availability of two services:

    Code
     The system monitoring needs your attention.
    
    Host:        \NAS.local
    Date:        Mon, 04 May 2020 08:16:57
    Service:     proftpd
    Event:       Does not exist
    Description: process is not running
    
    This triggered the monitoring system to: restart

    In a minute or so I re-receive alerts that the file system is already available:


    Code
    The system monitoring needs your attention.
    
    Host:        \NAS.local
    Date:        Mon, 04 May 2020 08:17:58
    Service:     mountpoint_srv_dev-disk-by-label-poolFS
    Event:       Status succeeded
    Description: status succeeded (0) -- /srv/dev-disk-by-label-poolFS is a mountpoint
    
    This triggered the monitoring system to: alert
    Code
    The system monitoring needs your attention.
    
    Host:        \NAS.local
    Date:        Mon, 04 May 2020 08:17:28
    Service:     filesystem_srv_dev-disk-by-label-poolFS
    Event:       Exists
    Description: succeeded getting filesystem statistics for '/srv/dev-disk-by-label-poolFS'
    
    This triggered the monitoring system to: alert
    Code
     The system monitoring needs your attention.
    
    Host:        \NAS.local
    Date:        Mon, 04 May 2020 08:16:57
    Service:     proftpd
    Event:       Does not exist
    Description: process is not running
    
    This triggered the monitoring system to: restart

    I understand that it is for the time that elapses since the mount is launched until the filesystem is ready.


    The one that worries me is the filesystem because it causes my docker containers to be corrupted because when they start up they do not have access to the volumes located in the poolFS that I have with btrfs and raid1.


    I'm pretty lost with this, can anyone help me?


    I add some information that I have collected:


    Code
    blkid
    /dev/sda: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="de0668a0-116a-420e-ba18-120e256be965" TYPE="btrfs"
    /dev/sdc: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="514ce6bf-77c8-466c-803e-a00406203080" TYPE="btrfs"
    /dev/sdb1: UUID="440A-716A" TYPE="vfat" PARTUUID="8416d791-32ac-4e22-97ac-87c9359f1d24"
    /dev/sdb2: UUID="720c65b3-b6ad-4fd8-a29d-7a71ea7bf347" TYPE="ext4" PARTUUID="c4da7b72-06da-4f84-b08f-682cf65648fd"
    /dev/sdb3: UUID="804397ea-1c5c-48ea-bf6d-8cf1a4e62040" TYPE="swap" PARTUUID="22a373c9-efa1-4f47-9ad7-c47987444487"
    /dev/sdd: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="19f398c6-8a42-4d2c-83be-55f7b74bc192" TYPE="btrfs"


    thanks in advance and sorry for my english

  • Hello colleagues,


    I have reinstalled version 5.3.9 and the problem persists. I have been able to observe that mounting the btrfs pool takes a few seconds and I think this is the problem. Is it possible to make any changes to the mounting time so that the monitor returns these errors?

    • Official Post

    You can add or change an environmental variable to /etc/default/openmediavault


    OMV_MONIT_DELAY_SECONDS

    to delay the start of monit.

    After you added the variable run

    omv-salt stage run prepare

    omv-salt deploy run monit

    to make the change effective.

  • Hi macom,

    Thanks for amswering, monit has stopped giving the error but I still have the problem with the docker containers. the docker service continues to start before the filesystem is available and I really don't know how I can fix it.


    Thank you

Participate now!

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