Error after depolying omv-env variable unset OMV_BTRFS_ERROR_CHECK_ENABLED under 7.0.3

1. offizieller Beitrag

    I unset the omv-env variable OMV_BTRFS_ERROR_CHECK_ENABLED back to default (was set to "no" before).

    Than doing:

    Code
    sudo monit restart omv-engined


    Code
    sudo omv-salt stage run prepare


    Code
    sudo omv-salt stage run deploy


    After deplay i get errors i never had before. No idea what to do. I'm not familiar with this salt stuff

    Output errors see attached file.


    Best regards

    prtigger

    Hi votdev


    Yes, plugin "openmediavault-md 7.0-6" is installed.

    If got an old Supermicro Atom Server with 3 * Samsung 870 QVO 4T SATA SSDs configured

    as SoftRAID, Level 5, with BTRFS Single filesystem on it.

    Systemdisk is a 64GB Supermicro SATA DOM with Flashmemory enabled.

    Server has only 4GB RAM.

    I used this setup since 6.9.x and had done a clean reinstall off the system with 7.0-RC1.

    I disabled BTRFS check and scrub with the reinstall and want to bring back the filesystem check today.

    With unsetting the variable to default....

    Had done all updates at the server console with omv-upgrade command from 7.0 RC1 till now

    That's the whole story.


    Best regards

    prtigger

    Hello votdev


    It´s not working for me.... The adviced commands produce no output and i still got errors after deploy (See attachment).

    I don´t know what i´m doing, i got the three deployment commands from the forum here. Never had any problem

    to set my custom variables during installation procedure. I always setup the basic system from ISO an installed the plugins

    i need... After restart, i do the individual configuration of the btrfs and scrub variables to my decision and after that, i install

    SMB, NFS, DLNA services.

    Do i have to do a clean reinstall with 7.0-32 ISO? I don´t know what´s going wrong in background. System is running

    normal... I recogniced this problem because i want to switch btrfs check back on.

  • prtigger1

    Hat das Label OMV 7.x hinzugefügt.

    Good morning votdev


    I don´t know if i can support you with any additional informations about config or any config files

    to bring 'light into my darkness'. I've no idea what i may made wrong with the installation,

    because i've done the same procedure with 7.0, i´ve done with 6.9.


    Best regards,

    have a great day,

    prtigger

    Oh, strange, too... Just bootup my server and get (via PuTTY):


    root@192.168.150.42's password:

    Linux pr-srv-01 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64


    The programs included with the Debian GNU/Linux system are free software;

    the exact distribution terms for each program are described in the

    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

    permitted by applicable law.

    Last login: Sun Mar 17 14:46:27 2024

    root@pr-srv-01:~# omv-confdbadm read --prettify conf.system.notification.notification

    [

    {

    "enable": true,

    "id": "monitprocevents",

    "uuid": "c1cd54af-660d-4311-8e21-2a19420355bb"

    },

    {

    "enable": false,

    "id": "monitloadavg",

    "uuid": "8deb96bd-10d6-4eb8-9e3d-0938f2bcbb30"

    },

    {

    "enable": true,

    "id": "monitmemoryusage",

    "uuid": "03dc067d-1310-45b5-899f-b471a0ae9233"

    },

    {

    "enable": false,

    "id": "monitcpuusage",

    "uuid": "fbf7973e-57a6-4c4a-8b7d-353653b596a5"

    },

    {

    "enable": true,

    "id": "monitfilesystems",

    "uuid": "d1ce47d1-d8d5-4f43-9f5c-36a30d818734"

    },

    {

    "enable": true,

    "id": "smartmontools",

    "uuid": "bd784490-a15c-47a9-9930-9f5897804654"

    }

    ]

    root@pr-srv-01:~#


    I swear, no output when i tried it last time and paste screen into the Output.txt file!!

    • Offizieller Beitrag

    The md related notification config is still not there. Run the following command again


    Bash
    omv-confdbadm read --defaults "conf.system.notification.notification" | jq ".id = \"mdadm\"" | omv-confdbadm update "conf.system.notification.notification" -

    No output after that:


    root@pr-srv-01:~# omv-confdbadm read --defaults "conf.system.notification.notification" | jq ".id = \"mdadm\"" | omv-confdbadm update "conf.system.notification.notification" -

    root@pr-srv-01:~#

    This output:


    root@pr-srv-01:~# omv-confdbadm read --prettify conf.system.notification.notification

    [

    {

    "enable": true,

    "id": "monitprocevents",

    "uuid": "c1cd54af-660d-4311-8e21-2a19420355bb"

    },

    {

    "enable": false,

    "id": "monitloadavg",

    "uuid": "8deb96bd-10d6-4eb8-9e3d-0938f2bcbb30"

    },

    {

    "enable": true,

    "id": "monitmemoryusage",

    "uuid": "03dc067d-1310-45b5-899f-b471a0ae9233"

    },

    {

    "enable": false,

    "id": "monitcpuusage",

    "uuid": "fbf7973e-57a6-4c4a-8b7d-353653b596a5"

    },

    {

    "enable": true,

    "id": "monitfilesystems",

    "uuid": "d1ce47d1-d8d5-4f43-9f5c-36a30d818734"

    },

    {

    "enable": true,

    "id": "smartmontools",

    "uuid": "bd784490-a15c-47a9-9930-9f5897804654"

    },

    {

    "enable": true,

    "id": "mdadm",

    "uuid": "750d6330-a218-47e6-b12e-52e726bac257"

    }

    ]

    root@pr-srv-01:~#


    mdadm is present now...

    What to do next (reboot or what else?)

    Try the 3 deployment commands...

    Still some Errors at the end (Full output, see attachment):


    Summary for debian

    ------------

    Succeeded: 2 (changed=2)

    Failed: 0

    ------------

    Total states run: 2

    Total run time: 207.095 s

    [ERROR ] Command 'blkid' failed with return code: 2

    [ERROR ] retcode: 2

    [ERROR ] Command 'blkid' failed with return code: 2

    [ERROR ] output:

    root@pr-srv-01:~#


    No idea for this....

    Just for information 'blkid' output from commandline:


    root@pr-srv-01:~# blkid

    /dev/sdd: UUID="9e7f70ab-36ef-1bca-7417-da7ac939dc8c" UUID_SUB="13b4b378-2598-6a61-a949-96b161e2f2a1" LABEL="PR-SRV-01:0" TYPE="linux_raid_member"

    /dev/sdb: UUID="9e7f70ab-36ef-1bca-7417-da7ac939dc8c" UUID_SUB="281ab7ed-a426-a721-9a39-b9b59e30f593" LABEL="PR-SRV-01:0" TYPE="linux_raid_member"

    /dev/md0: UUID="3baec89d-45b8-4b3c-bbf6-f0d2783c861d" UUID_SUB="4e80d5ff-df7d-497a-b935-fb47cb249e8e" BLOCK_SIZE="4096" TYPE="btrfs"

    /dev/sdc: UUID="9e7f70ab-36ef-1bca-7417-da7ac939dc8c" UUID_SUB="fff23200-99ff-1e77-999b-4cc04151c7a1" LABEL="PR-SRV-01:0" TYPE="linux_raid_member"

    /dev/sda5: UUID="8c24178a-6342-498a-8fca-fa201c798d37" TYPE="swap" PARTUUID="2872489a-05"

    /dev/sda1: UUID="2f66f0be-84ac-424c-8b61-f68565b97287" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2872489a-01"

    root@pr-srv-01:~#


    I don't know if this is interesting for you...

    • Offizieller Beitrag
    Zitat von prtigger1

    Thanks for your response...

    But have you got any idea for the 'blkid' errors? Never had seen something like that before at this place, after these commands....

    Best regards

    prtigger

    This is what the blkid man page says


    Zitat

    If the specified token was not found, or no (specified) devices could be identified, an exit code of 2 is returned.

    Since the OMV Python code does not call blkid, it is probably called within Salt. However, since it does not produce an error, it is also possible that a call that produces a return code 2 is made on purpose.

    I understand your post...

    I don't want to bother you with my questions... I'm not changing anything with the filesystems and get an error after deployment

    that i don´t get before with same configuration. So there may something changed in background.... Ok it´s not an error, it´s a warning

    that a token is missing by blkid call...

    I just try to understand the behaviour....

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden