Unofficial Plugin Repo for 0.5 Sardaukar, 1.0 Kralizec, 2.0 Stoneburner, 3.0 Erasmus, 4.0 Arrakis

  • This is the output:


    local:

    ----------

    data:

    ----------

    debian:

    ----------

    salt_|-populate_pillar_|-omv.populate_pillar_|-runner:

    ----------

    __id__:

    populate_pillar

    __jid__:

    20210919214105993352

    __orchestration__:

    True

    __run_num__:

    3

    __sls__:

    omv.stage.prepare.default

    changes:

    ----------

    return:

    True

    comment:

    Runner function 'omv.populate_pillar' executed.

    duration:

    19527.127

    name:

    omv.populate_pillar

    result:

    True

    start_time:

    23:40:49.275970

    salt_|-run_state_sync_|-run_state_sync_|-state:

    ----------

    __id__:

    run_state_sync

    __run_num__:

    4

    __sls__:

    omv.stage.prepare.default

    changes:

    ----------

    out:

    highstate

    ret:

    ----------

    debian:

    ----------

    module_|-sync_modules_|-sync_modules_|-run:

    ----------

    __id__:

    sync_modules

    __run_num__:

    0

    __sls__:

    omv.sync.default

    changes:

    ----------

    saltutil.sync_modules:

    comment:

    saltutil.sync_modules: []

    duration:

    1223.519

    name:

    - saltutil.sync_modules

    result:

    True

    start_time:

    23:41:09.127940

    module_|-sync_states_|-sync_states_|-run:

    ----------

    __id__:

    sync_states

    __run_num__:

    1

    __sls__:

    omv.sync.default

    changes:

    ----------

    saltutil.sync_states:

    comment:

    saltutil.sync_states: []

    duration:

    1109.916

    name:

    - saltutil.sync_states

    result:

    True

    start_time:

    23:41:10.352053

    comment:

    States ran successfully. Updating debian.

    duration:

    2660.144

    name:

    run_state_sync

    result:

    True

    start_time:

    23:41:08.803926

    salt_|-sync_modules_|-saltutil.sync_modules_|-runner:

    ----------

    __id__:

    sync_modules

    __jid__:

    20210919214027899357

    __orchestration__:

    True

    __run_num__:

    1

    __sls__:

    omv.stage.prepare.default

    changes:

    ----------

    return:

    comment:

    Runner function 'saltutil.sync_modules' executed.

    duration:

    18967.731

    name:

    saltutil.sync_modules

    result:

    True

    start_time:

    23:40:11.102566

    salt_|-sync_runners_|-saltutil.sync_runners_|-runner:

    ----------

    __id__:

    sync_runners

    __jid__:

    20210919214008783415

    __orchestration__:

    True

    __run_num__:

    0

    __sls__:

    omv.stage.prepare.default

    changes:

    ----------

    return:

    comment:

    Runner function 'saltutil.sync_runners' executed.

    duration:

    19194.115

    name:

    saltutil.sync_runners

    result:

    True

    start_time:

    23:39:51.907544

    salt_|-sync_states_|-saltutil.sync_states_|-runner:

    ----------

    __id__:

    sync_states

    __jid__:

    20210919214046974914

    __orchestration__:

    True

    __run_num__:

    2

    __sls__:

    omv.stage.prepare.default

    changes:

    ----------

    return:

    comment:

    Runner function 'saltutil.sync_states' executed.

    duration:

    19203.824

    name:

    saltutil.sync_states

    result:

    True

    start_time:

    23:40:30.071601

    outputter:

    highstate

    retcode:

    0

    • Offizieller Beitrag

    Now,


    sudo salt-call --local --retcode-passthrough --no-color state.orchestrate omv.stage.setup

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thank you and sorry for the late reply, here it is:


    local:

    ----------

    data:

    ----------

    debian:

    ----------

    salt_|-run_state_setup_|-run_state_setup_|-state:

    ----------

    __id__:

    run_state_setup

    __run_num__:

    0

    __sls__:

    omv.stage.setup.default

    changes:

    ----------

    out:

    highstate

    ret:

    ----------

    debian:

    ----------

    cmd_|-set_system_locale_|-update-locale LANG=it_IT.UTF-8 LC_ALL=it_IT.UTF-8_|-run:

    ----------

    __id__:

    set_system_locale

    __run_num__:

    9

    __sls__:

    omv.setup.locale.default

    changes:

    ----------

    pid:

    10979

    retcode:

    0

    stderr:

    stdout:

    comment:

    Command "update-locale LANG=it_IT.UTF-8 LC_ALL=it_IT.UTF-8" run

    duration:

    43.779

    name:

    update-locale LANG=it_IT.UTF-8 LC_ALL=it_IT.UTF-8

    result:

    True

    start_time:

    08:23:47.266267

    cmd_|-udevadm_reload_rules_|-udevadm control --reload-rules_|-run:

    ----------

    __id__:

    udevadm_reload_rules

    __run_num__:

    2

    __sls__:

    omv.setup.fstab.default

    changes:

    ----------

    pid:

    5710

    retcode:

    0

    stderr:

    stdout:

    comment:

    Command "udevadm control --reload-rules" run

    duration:

    25.583

    name:

    udevadm control --reload-rules

    result:

    True

    start_time:

    08:23:18.733245

    cmd_|-udevadm_trigger_|-udevadm trigger_|-run:

    ----------

    __id__:

    udevadm_trigger

    __run_num__:

    3

    __sls__:

    omv.setup.fstab.default

    changes:

    ----------

    pid:

    5711

    retcode:

    0

    stderr:

    stdout:

    comment:

    Command "udevadm trigger" run

    duration:

    232.87

    name:

    udevadm trigger

    result:

    True

    start_time:

    08:23:18.760293

    file_|-configure_root_bashrc_|-/root/.bashrc_|-prepend:

    ----------

    __id__:

    configure_root_bashrc

    __run_num__:

    12

    __sls__:

    omv.setup.shell.10root_bashrc

    changes:

    ----------

    diff:

    ---

    +++

    @@ -1,3 +1,11 @@

    +# Added by openmediavault (https://www.openmediavault.org).

    +if ! shopt -oq posix; then

    + if [ -f /usr/share/bash-completion/bash_completion ]; then

    + . /usr/share/bash-completion/bash_completion

    + elif [ -f /etc/bash_completion ]; then

    + . /etc/bash_completion

    + fi

    +fi

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    comment:

    Prepended 8 lines

    duration:

    12.75

    name:

    /root/.bashrc

    result:

    True

    start_time:

    08:23:50.236362

    file_|-configure_root_inputrc_|-/root/.inputrc_|-managed:

    ----------

    __id__:

    configure_root_inputrc

    __run_num__:

    13

    __sls__:

    omv.setup.shell.20root_inputrc

    changes:

    ----------

    comment:

    File /root/.inputrc is in the correct state

    duration:

    69.075

    name:

    /root/.inputrc

    result:

    True

    start_time:

    08:23:50.249370

    file_|-create_root_bashrc_|-/root/.bashrc_|-managed:

    ----------

    __id__:

    create_root_bashrc

    __run_num__:

    11

    __sls__:

    omv.setup.shell.10root_bashrc

    changes:

    ----------

    comment:

    File /root/.bashrc exists with proper permissions. No changes made.

    duration:

    4.157

    name:

    /root/.bashrc

    result:

    True

    start_time:

    08:23:50.232003

    file_|-enable_discard_in_lvm_conf_|-/etc/lvm/lvm.conf_|-replace:

    ----------

    __id__:

    enable_discard_in_lvm_conf

    __run_num__:

    5

    __sls__:

    omv.setup.fstrim.default

    changes:

    ----------

    comment:

    No changes needed to be made

    duration:

    54.268

    name:

    /etc/lvm/lvm.conf

    result:

    True

    start_time:

    08:23:19.850670

    file_|-fix_etc_path_permissions_|-/etc_|-directory:

    ----------

    __id__:

    fix_etc_path_permissions

    __run_num__:

    1

    __sls__:

    omv.setup.fixmode.default

    changes:

    ----------

    /etc:

    ----------

    mode:

    0755

    mode:

    0755

    comment:

    Directory /etc updated

    duration:

    3.375

    name:

    /etc

    result:

    True

    start_time:

    08:23:18.727417

    file_|-fix_root_path_permissions_|-/_|-directory:

    ----------

    __id__:

    fix_root_path_permissions

    __run_num__:

    0

    __sls__:

    omv.setup.fixmode.default

    changes:

    ----------

    /:

    ----------

    mode:

    0755

    mode:

    0755

    comment:

    Directory / updated

    duration:

    4.83

    name:

    /

    result:

    True

    start_time:

    08:23:18.722213

    file_|-modify_root_profile_|-/root/.profile_|-replace:

    ----------

    __id__:

    modify_root_profile

    __run_num__:

    14

    __sls__:

    omv.setup.shell.30root_profile

    changes:

    ----------

    comment:

    No changes needed to be made

    duration:

    3.606

    name:

    /root/.profile

    result:

    True

    start_time:

    08:23:50.318715

    file_|-symlink_systemd_resolvconf_|-/etc/resolv.conf_|-symlink:

    ----------

    __id__:

    symlink_systemd_resolvconf

    __run_num__:

    10

    __sls__:

    omv.setup.resolvconf.default

    changes:

    ----------

    new:

    /etc/resolv.conf

    comment:

    Created new symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

    duration:

    2920.946

    name:

    /etc/resolv.conf

    result:

    True

    start_time:

    08:23:47.310600

    locale_|-generate_C.UTF-8_locale_|-C.UTF-8_|-present:

    ----------

    __id__:

    generate_C.UTF-8_locale

    __run_num__:

    7

    __sls__:

    omv.setup.locale.default

    changes:

    ----------

    comment:

    Locale C.UTF-8 is already present

    duration:

    14.217

    name:

    C.UTF-8

    result:

    True

    start_time:

    08:23:47.238296

    locale_|-generate_it_IT.UTF-8_locale_|-it_IT.UTF-8_|-present:

    ----------

    __id__:

    generate_it_IT.UTF-8_locale

    __run_num__:

    8

    __sls__:

    omv.setup.locale.default

    changes:

    ----------

    comment:

    Locale it_IT.UTF-8 is already present

    duration:

    12.68

    name:

    it_IT.UTF-8

    result:

    True

    start_time:

    08:23:47.253051

    salt_|-update_initramfs_|-update_initramfs_|-state:

    ----------

    __id__:

    update_initramfs

    __run_num__:

    6

    __sls__:

    omv.setup.initramfs.default

    changes:

    ----------

    out:

    highstate

    ret:

    ----------

    debian:

    ----------

    cmd_|-update_initramfs_|-update-initramfs -u_|-run:

    ----------

    __id__:

    update_initramfs

    __run_num__:

    1

    __sls__:

    omv.deploy.initramfs.default

    changes:

    ----------

    pid:

    5839

    retcode:

    0

    stderr:

    stdout:

    update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.8-amd64

    comment:

    Command "update-initramfs -u" run

    duration:

    27056.741

    name:

    update-initramfs -u

    result:

    True

    start_time:

    08:23:20.172511

    test_|-update_initramfs_nop_|-update_initramfs_nop_|-nop:

    ----------

    __id__:

    update_initramfs_nop

    __run_num__:

    0

    __sls__:

    omv.deploy.initramfs.default

    changes:

    ----------

    comment:

    Success!

    duration:

    1.763

    name:

    update_initramfs_nop

    result:

    True

    start_time:

    08:23:20.169126

    comment:

    States ran successfully. Updating debian.

    duration:

    27326.788

    name:

    update_initramfs

    result:

    True

    start_time:

    08:23:19.907129

    service_|-start_fstrim_timer_|-fstrim.timer_|-running:

    ----------

    __id__:

    start_fstrim_timer

    __run_num__:

    4

    __sls__:

    omv.setup.fstrim.default

    changes:

    ----------

    fstrim.timer:

    True

    comment:

    Service fstrim.timer has been enabled, and is running

    duration:

    852.464

    name:

    fstrim.timer

    result:

    True

    start_time:

    08:23:18.997649

    comment:

    States ran successfully. Updating debian.

    duration:

    32219.125

    name:

    run_state_setup

    result:

    True

    start_time:

    08:23:18.106262

    outputter:

    highstate

    retcode:

    0

    • Offizieller Beitrag

    Not really. Those returned without error. Maybe: sudo apt-get install --reinstall openmediavault

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Here is the output:

    Lettura elenco dei pacchetti... Fatto

    Generazione albero delle dipendenze

    Lettura informazioni sullo stato... Fatto

    0 aggiornati, 0 installati, 1 reinstallati, 0 da rimuovere e 0 non aggiornati.

    1 non completamente installati o rimossi.

    Dopo quest'operazione, verranno occupati 0 B di spazio su disco.

    E: Internal Error, No file name for openmediavault:amd64

    • Offizieller Beitrag

    wget http://packages.openmediavault.org/public/pool/main/o/openmediavault/openmediavault_5.6.16-1_all.deb

    sudo dpkg -i openmediavault_5.6.16-1_all.deb

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • @ryecoaaron Is there a way to install the flash memory plugin only, without using the script that installs omv-extras? I'm trying the docker compose that omv-extras installs (it's causing a conflict with another script I am using).

    Alternatively, can I remove the docker compose that omv-extras installs and leave the rest of the ovm-extras plugin?


    I'm running the OMV 6 Alpha (if that makes any difference).

    Thanks in advance!

    • Offizieller Beitrag

    Why don't you want to install omv-extras? If you don't want docker-compose, don't install docker with omv-extras. docker-compose is not a dependency of omv-extras. If you want to install docker with omv-extras, just delete the docker-compose file after but I don't understand how it could conflict with another script.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • @ ryecoaaron nothing to do... again errors... what damn is it?? It's a lot of time i'm using OMV and i never has a such trouble...

    Anyway i will never end thanking you for the support!!

    Here is the output:


    (Lettura del database... 284582 file e directory attualmente installati.)

    Preparativi per estrarre openmediavault_5.6.16-1_all.deb...

    Estrazione di openmediavault (5.6.16-1) su (5.6.16-1)...

    Configurazione di openmediavault (5.6.16-1)...

    Creating configuration database ...

    Migrating configuration database ...

    Setting up Salt environment ...

    Processing system modifications ...

    dpkg: errore nell'elaborare il pacchetto openmediavault (--install):

    il sottoprocesso installato pacchetto openmediavault script post-installation ha restituito lo stato di errore 1

    Elaborazione dei trigger per rsyslog (8.1901.0-1)...

    Si sono verificati degli errori nell'elaborazione:

    openmediavault

    • Offizieller Beitrag

    what damn is it?? It's a lot of time i'm using OMV and i never has a such trouble...

    This isn't really OMV's fault. Your system is in a weird state. If I had it in front of me and it was in english, maybe I could spend the time to figure it out. Something in the postinst script is causing a problem but it isn't logging enough to tell. What I have been doing is trying to have you run lines from the postinst script one at a time. But there are hundreds.


    When things get in this condition, I usually tell people to reinstall. It takes less time (definitely less of my time).

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Why don't you want to install omv-extras? If you don't want docker-compose, don't install docker with omv-extras. docker-compose is not a dependency of omv-extras. If you want to install docker with omv-extras, just delete the docker-compose file after but I don't understand how it could conflict with another script.

    Thanks!

    I'm using DockSTARTer. For some reason, if OMV-extras is installed, I can't install DockSTARTer and vice versa: if I already have DockSTARTer installed, then I get an error if I try to install OMV-extras. (The couple plugins I use, are now included directly in OMV 6. The only other one I need is the flash memory plugin---that's why I was asking if there was a way to install this all by itself). I have tried this in OMV 5.xx and 6 with the same result.


    You seemed to imply that Docker Compose is only installed by OMV-extras, if I use it to install Docker--but even before installing Docker with OMV-extras, DockSTARTer throws an error when trying to install Docker compose. I'm not exactly sure where the conflict/problem lies. I realize also this problem may lie with DockSTARTer.


    Thanks for any insight you can give...

  • This isn't really OMV's fault. Your system is in a weird state. If I had it in front of me and it was in english, maybe I could spend the time to figure it out. Something in the postinst script is causing a problem but it isn't logging enough to tell. What I have been doing is trying to have you run lines from the postinst script one at a time. But there are hundreds.


    When things get in this condition, I usually tell people to reinstall. It takes less time (definitely less of my time).

    I see, well i will then wait for OMV 6 stable to be released and then i will reinstall everything from scratch, i agree with you definitely :) this system it's running h/24 since ver. 4 of OMV, maybe the time for it to be cleaned as arrived :) do you know when it's planned to be released the ver. 6 ?

    Thank you for the time spended helping me!!

  • Why don't you want to install omv-extras? If you don't want docker-compose, don't install docker with omv-extras. docker-compose is not a dependency of omv-extras. If you want to install docker with omv-extras, just delete the docker-compose file after but I don't understand how it could conflict with another script.

    It's not that I don't want to install omv-extras---it's I get an error trying to install it. This is the error:


    E: Conflicting values set for option Signed-By regarding source https://download.docker.com/linux/debian/ bullseye: /usr/share/keyrings/docker-archive-keyring.gpg !=

    E: The list of sources could not be read.


    I still haven't figured it out--so I am not able to get the flash memory plugin. Obviously, I don't have to use DockSTARTer. But after the last couple weeks of constant trial and error, and multiple re-installations trying to figure all of this stuff out (that's new to me)--that script just makes my life easier to get up and running quickly. Maybe you might have an idea, based on that error message....of what I can change to fix this?

    • Offizieller Beitrag

    It seems like some of the error message is lost. What is the output of: sudo omv-salt deploy run omv-extras

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • It seems like some of the error message is lost. What is the output of: sudo omv-salt deploy run omv-extras

    Thanks for the follow-up! I have redone my system---this time WITHOUT DockSTARTer---so I no longer have access to give you the full error message.
    DockSTARTer was a useful tool, in giving me an introduction, and connecting some dots about how things work. But since it's initial run, and I see the files it creates (docker-compose.yml and .env), I don't need it anymore. So I am am just using the stock OMV install now, and your OMV-extras installs perfectly with that. I am still learning my way around, and hopefully learn to master docker-compose a little better, but it's really not as hard as I thought--the hardest part was figuring out WHERE in the file system some of the files are.

    (This question is unrelated to this thread--but I don't want to make a new thread: Does anyone know if the advice of votdev from 2018 AGAINST using filesystem labels is still relevant?) The hardest part working from the CLI is entering the long disk paths based on UUID, and I was wondering if I can assign labels that I can use as alias for the paths.

    • Offizieller Beitrag

    (This question is unrelated to this thread--but I don't want to make a new thread: Does anyone know if the advice of votdev from 2018 AGAINST using filesystem labels is still relevant?) The hardest part working from the CLI is entering the long disk paths based on UUID, and I was wondering if I can assign labels that I can use as alias for the paths.

    For btrfs file systems labels are use. For others UUID.


    If you don't like UUID, you can use symlinks to link a user friendly name to the actual filesystem. For this you can use the symlink plugin.

Jetzt mitmachen!

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