Posts by tinh_x7


    I'm currently using Docker and Cockpit.

    Anybody receive this error ?

    Hi guys,

    I'm currently using a custom built for OMV5, but lately it has some ethernet driver issue.

    I'm thinking if I can't fix this issue or the system board is dead in the future, then I need a new system.

    Is anybody in here able to install OMV5 in Synology station or another brand that want to share some insights ?


    Apparently the error persist after the server woke up from hibernation.

    I'm planning to put the script to disable tso and gso like this format.

    I'm not sure if this work in OMV5: RE: Customize /etc/network/interfaces the OMV way [>= 1.11]

    Update 1: I put the script in /etc/network/interfaces.d/, and ran this command:

    omv-salt deploy run systemd-networkd .

    However, after the computer restarted, the script didn't execute.

    -rwxr-xr-x 1 root root 1307 Dec 30 19:17

    Why ?


    I'm not sure if this issue is only affect my system.

    But it annoying as crap.

    The computer boot up and showed error for: e1000e 0000:00:19.0 eno1

    I've tried this solution…ic-and-hardware-unit-hang but error persist after it wake from hibernation, then it shut down with in 15 seconds.

    I then restored OMV v5.5.14, and it running fine.

    I don't see that error anymore.

    Next, I updated it to 5.5.19, the system error happening again !

    In addition, I've also disabled the C1E feature in the BIOS too.


    Thanks for sharing the guide.

    I managed to installed Windows 10.

    However, I'm tried to create a bridge adapter, but received an error.

    Note: I'm currently using a bond0 in OMV.

    Hi guys,

    I just replaced a bad hdd with a new hard drive.

    My setup: LUKS Encryption with SnapRAID.

    I unmounted the bad hdd from the encryption but it showing missing.

    It let me did the encryption first time for the new hdd but it failed to create a new file system.

    Now, OMV wouldn't let me do the encryption at all.

    I'm seeing the bad hdd UUID is in the /etc/openmediavault/config.xml.

    What's the best solution ?

    Unable to create encrypted device: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; echo -n 'redacted!' | cryptsetup luksFormat --label=parity2 -c aes-xts-plain64 -q '/dev/dm-4' 2>&1' with exit code '1':