Posts by mcflym

    Nope. Not saying I won't but I really don't want to. Using a password file to lock/unlock isn't possible with OMV 6.x for one. Getting the zfs plugin to a better place and improving the kvm plugin are my priorities right now.


    There is nothing stopping you from using LUKS. Since normal filesystems live on top of it, OMV really doesn't care about it.


    Can't wait for the luks plugin. :) I just need to add a key file via gui, cause i'm using an usb stick to decrypt after boot.


    I'm scared of fiddeling with cli to encrypt my drives and maybe not getting access to them.

    There was an answer at the project-homepage


    Quote

    I'd need debug output to 100% sure but this is most probably caused by running out of system memory by running argon2 kdf in parallel (since systemd-cryptsetup processes are being killed by SIGKILL). It should be evident from syslog.

    There's patch for it in systemd v244+ already (and it requires upstream cryptsetup v2.2.0 or later). See https://github.com/systemd/sys…dfbff1c95ce3210d06f256e58.

    So it's related to the cryptsetup and systemd version (I'm using 2.2 and 241) and the memory-size I allocated to openmediavault. I have 8 GB of RAM, so I increase in the first step the allocated RAM to get the errors away and in future there will be a fix hopefully. :)

    I tried to boot with two usb-sticks and use one stick for four drives... Same issue.


    I think there is a "limit" of decrypting at bootup in luks?!


    Is there anyone who is decrypting more than 7 drives at bootup?


    Hi,


    I'm using luks for drive encryption. I decrypt the drives at bootup via usb-stick, /etc/crypttab:


    Code
    sda-crypt UUID=fbc503de-a359-41e8-9f74-bd009a4ff5b6 /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdb-crypt UUID=eea24687-f2f4-4738-b47d-a2b8840a815e /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdc-crypt UUID=1d51afa7-6ee0-4a0d-b568-7f4b9e0f7ada /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdd-crypt UUID=01139fc6-56bc-42b2-b863-199695d68d1e /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sde-crypt UUID=5826dfc3-bfe4-4f62-a266-f169870dec75 /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdf-crypt UUID=3757d17b-a7e0-4bba-828d-53f87becafa5 /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdi-crypt UUID=07d49183-b216-44fb-b016-88951c4a6036 /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512
    sdj-crypt UUID=1b9f32c0-10f1-4cf3-84b1-b065d86aabfd /dev/disk/by-id/usb luks,tries=3,keyfile-size=8192,keyfile-offset=512

    as you can see, the number of drives are 8 and this doesn't work. If I reduce this number to 7 or lower, the bootup works as expected.


    Here are some log infos.

    Code
    root@omv:~# systemctl --state=failed
      UNIT                                    LOAD   ACTIVE SUB    DESCRIPTION
    ● systemd-cryptsetup@sda\x2dcrypt.service loaded failed failed Cryptography Setup for sda-crypt
    ● systemd-cryptsetup@sdf\x2dcrypt.service loaded failed failed Cryptography Setup for sdf-crypt


    The drives are different at every boot:

    Code
    root@omv:~# systemctl --state=failed
      UNIT                                    LOAD   ACTIVE SUB    DESCRIPTION
    ● systemd-cryptsetup@sda\x2dcrypt.service loaded failed failed Cryptography Setup for sda-crypt
    ● systemd-cryptsetup@sdb\x2dcrypt.service loaded failed failed Cryptography Setup for sdb-crypt
    ● systemd-cryptsetup@sdd\x2dcrypt.service loaded failed failed Cryptography Setup for sdd-crypt
    ● systemd-cryptsetup@sde\x2dcrypt.service loaded failed failed Cryptography Setup for sde-crypt
    ● systemd-cryptsetup@sdf\x2dcrypt.service loaded failed failed Cryptography Setup for sdf-crypt

    bootup:


    What's going on here?


    Are there some timing issues?

    Hi,


    I'm resolving the following message after upgrade (coming from 5.5.2-1) if I'm accepting the new configuration:



    I'm using omv-extras with unionfilesystems (mergerfs).


    Installation is within an proxmox-VM.


    Kernel-Version is 5.8


    Any ideas?


    Thank you!

    Hi,


    I'm getting 100 percent CPU Load when I'm starting the smb service...



    Whats wrong there?


    CPU: C3858 ATOM

    RAM: 4 GB DDR4


    top is showing me:


    Code
    top - 12:32:38 up 2 min,  0 users,  load average: 1.52, 0.82, 0.33
    Tasks: 139 total,   2 running, 135 sleeping,   0 stopped,   2 zombie
    %Cpu(s): 33.3 us, 61.1 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  5.6 si,  0.0 st
    MiB Mem :   3940.6 total,   3500.9 free,    198.6 used,    241.1 buff/cache
    MiB Swap:   1022.0 total,   1022.0 free,      0.0 used.   3513.2 avail Mem
    
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
      657 root      20   0   49804  20580  17916 S  18.8   0.5   0:18.86 smbd
        1 root      20   0  104236  10628   7984 S   0.0   0.3   0:02.11 systemd
        2 root      20   0       0      0      0 S   0.0   0.0   0:00.00 kthreadd


    Code
    root@omv-fw:~# smbstatus
    
    Samba version 4.9.5-Debian
    PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing
    ----------------------------------------------------------------------------------------------------------------------------------------
    
    Service      pid     Machine       Connected at                     Encryption   Signing
    ---------------------------------------------------------------------------------------------
    
    No locked files


    Thanks!

    Hallo,


    ich habe rsync bei mir eingerichtet und möchte ihn per Job laufen lassen und zwar jede Nacht um 3 Uhr.


    Momentan sieht meine Konfiguration hierfür folgendermaßen aus:



    Jetzt macht er natürlich jede 3 Stunde seinen Lauf. Das möchte ich aber so nicht, sondern er soll eben nur einmal am Tag um 3 Uhr seinen Lauf machen. Wie muss das hier eingestellt werden? Jeden Nten Tag auf 1 setzen? Geht das dann auch wirklich um 3 Uhr los? Weil momentan hat er quasi ab Aktivierung diese jede Nte Stunde gezogen. D.h. Die Jobs laufen z.b. um 06:09 Uhr oder um 09:09 Uhr... Ich möchte das aber exakt auf die Stunde.


    Vielen Dank!

    /etc/apt/sources.list.d/openmediavault-kernel-backports.list: Datei oder Verzeichnis nicht gefunden


    hmm? :/


    there is only:


    Code
    root@omv:/etc/apt/sources.list.d# ls
    omv-extras-org.list  openmediavault.list  openmediavault-local.list
    Code
    root@omv:~# apt-cache policy btrfs-tools
    btrfs-tools:
      Installiert:           3.17-1.1
      Installationskandidat: 3.17-1.1
      Versionstabelle:
     *** 3.17-1.1 0
            500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
            100 /var/lib/dpkg/status

    Hi ryecoaaron,


    thanks for your instant reply!


    If i try to run

    Code
    apt-get install btrfs-tools=4.7.3-1~bpo8+1

    it doesn't work. "E: Version »4.7.3-1~bpo8+1« für »btrfs-tools« konnte nicht gefunden werden."


    and if I try

    Code
    apt-get install btrfs-tools

    it says that the newest version is installed.


    Any ideas? I am on kernel version 4.9.0-0.bpo.3-amd64

    Hi there...


    yes I know there are two threads with this topic... but i don't get it...


    What I have to do to upgrade to the newest btrfs version? Currently installed is 3.17...


    Thanks!