Posts by Donald123

    Hello,
    to make it more easier to read the bug report (only the beginning, due to error messages while trying to send the complete error messages):

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run mdadm 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): raspberrypi: ---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 13:16:18.146504 Duration: 0.928 ms Changes: ---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm updated Started: 13:16:18.147710 Duration: 109.384 ms Changes: ---------- diff: --- +++ @@ -1,10 +1,16 @@ -# mdadm Debian configuration -# -# You can run 'dpkg-reconfigure mdadm' to modify the values in this file, if -# you want. You can also change the values here and changes will be preserved. -# Do note that only the values are preserved; the rest of the file is -# rewritten. -# +# This file is auto-generated by openmediavault (https://www.openmediavault.org) +# WARNING: Do not edit this file, your changes will get lost. + +# INITRDSTART: +# list of arrays (or 'all') to start automatically when the initial ramdisk +# loads. This list *must* include the array holding your root filesystem. Use +# 'none' to prevent any array from being started from the initial ramdisk.

    I hope, someone can help...

    Hello,
    to make it more easier to read the bug report (only the beginning, due to error messages while trying to send the complete error messages):

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run mdadm 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): raspberrypi: ---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 13:16:18.146504 Duration: 0.928 ms Changes: ---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm updated Started: 13:16:18.147710 Duration: 109.384 ms Changes: ---------- diff: --- +++ @@ -1,10 +1,16 @@ -# mdadm Debian configuration -# -# You can run 'dpkg-reconfigure mdadm' to modify the values in this file, if -# you want. You can also change the values here and changes will be preserved. -# Do note that only the values are preserved; the rest of the file is -# rewritten. -# +# This file is auto-generated by openmediavault (https://www.openmediavault.org) +# WARNING: Do not edit this file, your changes will get lost. + +# INITRDSTART: +# list of arrays (or 'all') to start automatically when the initial ramdisk +# loads. This list *must* include the array holding your root filesystem. Use +# 'none' to prevent any array from being started from the initial ramdisk. +#INITRDSTART='none' + +# AUTOSTART: +# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically +# during boot? +AUTOSTART=true # AUTOCHECK: # should mdadm run periodic redundancy checks over your arrays? See ---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 13:16:18.257388 Duration: 24.648 ms Changes: ---------- diff: --- +++ @@ -1,22 +1,25 @@ +# This file is auto-generated by openmediavault (https://www.openmediavault.org) +# WARNING: Do not edit this file, your changes will get lost. + # mdadm.conf -# -# !NB! Run update-initramfs -u after updating this file. -# !NB! This will ensure that initramfs has an uptodate copy. # # Please refer to mdadm.conf(5) for information about this file. # -# by default (built-in), scan all partitions (/proc/partitions) and all -# containers for MD superblocks. alternatively, specify devices to scan, using -# wildcards if desired. -#DEVICE partitions containers +# by default, scan all partitions (/proc/partitions) for MD superblocks. +# alternatively, specify devices to scan, using wildcards if desired. +# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. +# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is +# used if no RAID devices are configured. +DEVICE partitions + +# auto-create devices with Debian standard permissions +CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> - # instruct the monitoring daemon where to send mail alerts -MAILADDR root +MAILADDR holger.neustock@kabelmail.de +MAILFROM root # definitions of existing MD arrays - -# This configuration was auto-generated on Fri, 17 Jan 2020 17:47:24 +0000 by mkconf ---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 13:16:18.283826 Duration: 32.739 ms Changes: ---------- pid: 6017 retcode: 0 stderr: stdout: ---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 13:16:18.317126 Duration: 13.427 ms Changes: ---------- pid: 6019 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout: Summary for raspberrypi ------------ Succeeded: 4 (changed=4) Failed: 1 ------------ Total states run: 5 Total run time: 181.126 ms

    I hope, someone can help...

    Hello,
    to make it more easier to read the bug report:

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run mdadm 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): raspberrypi: ---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 13:16:18.146504 Duration: 0.928 ms Changes: ---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm updated Started: 13:16:18.147710 Duration: 109.384 ms Changes: ---------- diff: --- +++ @@ -1,10 +1,16 @@ -# mdadm Debian configuration -# -# You can run 'dpkg-reconfigure mdadm' to modify the values in this file, if -# you want. You can also change the values here and changes will be preserved. -# Do note that only the values are preserved; the rest of the file is -# rewritten. -# +# This file is auto-generated by openmediavault (https://www.openmediavault.org) +# WARNING: Do not edit this file, your changes will get lost. + +# INITRDSTART: +# list of arrays (or 'all') to start automatically when the initial ramdisk +# loads. This list *must* include the array holding your root filesystem. Use +# 'none' to prevent any array from being started from the initial ramdisk. +#INITRDSTART='none' + +# AUTOSTART: +# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically +# during boot? +AUTOSTART=true # AUTOCHECK: # should mdadm run periodic redundancy checks over your arrays? See ---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 13:16:18.257388 Duration: 24.648 ms Changes: ---------- diff: --- +++ @@ -1,22 +1,25 @@ +# This file is auto-generated by openmediavault (https://www.openmediavault.org) +# WARNING: Do not edit this file, your changes will get lost. + # mdadm.conf -# -# !NB! Run update-initramfs -u after updating this file. -# !NB! This will ensure that initramfs has an uptodate copy. # # Please refer to mdadm.conf(5) for information about this file. # -# by default (built-in), scan all partitions (/proc/partitions) and all -# containers for MD superblocks. alternatively, specify devices to scan, using -# wildcards if desired. -#DEVICE partitions containers +# by default, scan all partitions (/proc/partitions) for MD superblocks. +# alternatively, specify devices to scan, using wildcards if desired. +# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. +# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is +# used if no RAID devices are configured. +DEVICE partitions + +# auto-create devices with Debian standard permissions +CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> - # instruct the monitoring daemon where to send mail alerts -MAILADDR root +MAILADDR holger.neustock@kabelmail.de +MAILFROM root # definitions of existing MD arrays - -# This configuration was auto-generated on Fri, 17 Jan 2020 17:47:24 +0000 by mkconf ---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 13:16:18.283826 Duration: 32.739 ms Changes: ---------- pid: 6017 retcode: 0 stderr: stdout: ---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 13:16:18.317126 Duration: 13.427 ms Changes: ---------- pid: 6019 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout: Summary for raspberrypi ------------ Succeeded: 4 (changed=4) Failed: 1 ------------ Total states run: 5 Total run time: 181.126 ms

    I hope, someone can help...

    Hello gderf,
    many, many thanks for your reply. What is the rihgt moment to do a clearing of the cache? The moment after i had just tipped in the correct Email-data? I´m not sure how to handle your (very welcomed) hint.


    Best regards,
    Holger

    Hi,
    my first post! 8o
    it was great to install OMV-RPi4 (Version 5.2.3.-2). Everything works fine.
    My only problem so fare: I can´t store my email-configuration. Everytime I want to store my configuration, I get the error, which i have append.


    Anyone with the same problem?


    Regards
    Holger