Posts by NothingNowhere

    sudo mv /var/lib/dpkg/info/openmediavault.triggers /var/lib/dpkg/info/openmediavault.triggers_backup

    Great, this worked for me with OMV 5 on my Odroid HC2. Thank you.

    I didn't need to reboot, I did sudo service openmediavault-engined restart then a force reload in my browser (ctrl-shift-R in chrome)

    Just sharing this for future reference, hopefully to save hair pulling for somebody along the line!

    I built an OMV box using a large case and a known good motherboard, CPU and memory. I was combining 10 HDDs from 2 old boxes but all drives were known good.

    I got a used Dell H310 SAS card from a reputable eBayer to host eight of the HDD's, connected the other 2 to the motherboard SATA and put the OMV operating system on a small SSD.

    I soon was getting lots of problems which I couldn't make sense of - sometimes the system booted fine, often it got to the GRUB menu but then had lots of mdadm no arrays found errors and dropped out to BusyBox. I tried various fixes relating to GRUB in case that was corrupted, but no change.

    Sometimes the system didn't find the OS drive at all. I tried changing power and data cables, but no change.

    I thought there might be an intermittent fault with the SAS card, causing some weird conflict with motherboard BIOS, and this led me on a fruitless internet goose chase.

    Finally it occurred to me that the SSD might be faulty. So I bought Crucial's smallest SSD, cloned the OS to that with Clonezilla and hey presto, everything working as it should.

    What I don't quite understand is why the system, once booted, would run for many hours without fault - suggests that SSD only had an intermittent problem at power-up I guess.

    Having had weird mobo issues for months and recently resolved them, first try:

    1. Remove all cables, cards, memory, CPU. Remove motherboard from case.

    2. Look over mobo very closely for any blown/bulging components or damage to copper traces.

    3. If OK, clean board with cotton buds and isopropyl alcohol. (mine was not just a bit dusty, it turned out!)

    4. Check closely for anything in the PCI / memory slots that might cause shorts/bad contacts. Hold board upside down, shake it about.

    5. Check case for the same before rebuilding.

    In my case, I think something very small was causing an intermittent short that threw all sorts of odd errors for months - POST problems, and once booted lots of "xz-compressed data is corrupted system halted" errors.

    I got new RAM, that didn't help. Reflashed BIOS, no help. Eventually it didn't POST at all, so I was about to order a new board but then did the above and so far, no problems at all.

    Hope this helps. If not, is very useful for sifting through mobos and components by specs.

    I am merging 2 Snapraid arrays into 1. From 4 data and 1 parity to 8 data and 2 parity.

    I added 3 of the disks from the old second array without error (using the Snapraid plugin in the OMV webui) but one disk threw this error and could not be added:

    The configuration object '' is not unique. An object with the property 'mntentref' and value '5ec4c9fa-ab9a-4cfc-bc39-32c87808027f' already exists.

    Can anyone point me to how to correct this?

    Thanks gderf,

    So far so good, I enabled that mountpoint column (very useful, never realised it was there) and those drives are using disk-by-label.

    Once I was sure this was working as intended I rebooted and recreated my union/fuse mountpoints with the OMV ui for disks 5-8

    I will be creating shares using the union mountpoint rather than the disks so I think I'm OK.

    OK, answering my own question... I'd be grateful if someone with more linux wisdom could check this over though!

    I went into /srv and did

    sudo mkdir /dev-disk-by-label-disk6

    sudo mkdir /dev-disk-by-label-disk7


    sudo mount /dev/sdc1 /srv/dev-disk-by-label-disk6

    sudo mount /dev/sdd1 /srv/dev-disk-by-label-disk7


    sudo nano /etc/fstab to edit the fstab and replace






    Rebooted, all seemed fine.

    Finally, I went into /srv again and checked the old mountpoints were empty:



    They were so I deleted them.

    Hello all,

    I am combining two old OMV systems into a new box. For simplicity I've labelled the main drives (using e2label) as disk[1-8]

    Under /srv/ I have 2 drives that haven't mounted with labels. This is output of lsblk:

    How can I change sdc1 and sdd1 to mount at dev-disk-by-label-disk[6-7] like the rest?

    Thanks for reading.

    Hello all,

    I have a problem with a Samsung D3 external HDD, which is USB 3.0

    With my Windows laptop it works fine on USB 3.

    With my OMV box (a PC case with this mobo ) it works fine on USB 2 but I connect it to USB 3 it is not recognised and I get the following errors in syslog:

    However, if I connect a different USB 3 drive (a slightly newer Seagate Expansion) BUT using the same PSU, USB cable and port, it works fine.

    Any thoughts welcome!

    Yes, I see it's possibly doable on Armbian, I might experiment one day.…all-to-emmc-nand-sata-usb

    Cards are Kingston or SanDisk from Amazon as the seller, i.e. not fakes.

    I'll run them through badblocks maybe, it's not the cost of new cards it's just frustrating when I think I've got everything ticking over nicely, something odd like this comes along.

    Anyway, thanks as ever for your help.

    Hello, I have OMV 5 on my Odroid C2, which was working fine, now can't login to the webui. It seems omv-engine service isn't running.

    This is a recent installation using the instructions for Armbian installs. Not an upgrade from OMV 4.

    SSH, FTP, Samba etc. all working fine still.

    This seems to be a common problem but with various causes. I've tried a few suggestions from older threads, to no avail.

    Here are some more outputs from common suggestions.

    Webgui login error:

    Failed to connect to socket: No such file or directory

    journalctl -xe

    sudo omv-engined -d -f gives:

    Illegal instruction

    sudo dpkg --verify

    Just flashmemory and extras plugins installed:

    sudo dpkg -l |grep openme

    Lots of disk space left

    df -h

    Everything is up to date using apt.

    Any thoughts anyone?

    Hello, I have SSH working fine for months on various OMV machines.

    I wanted to add a second public key to a user for use with rsync. I got the same error on two machines, one an AMD64 box and one a RaspberryPi 3 - both running OMV5.

    On trying to apply the changes I get a long error - can anyone help me decipher this?:

    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 ssh 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/decorators/ DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) debian: ---------- ID: remove_ssh_authorized_keys Function: Name: /var/lib/openmediavault/ssh/authorized_keys Result: True Comment: Files cleaned from directory /var/lib/openmediavault/ssh/authorized_keys Started: 00:25:27.755780 Duration: 1.512 ms Changes: ---------- /var/lib/openmediavault/ssh/authorized_keys/myusername: ---------- removed: Removed due to clean removed: - /var/lib/openmediavault/ssh/authorized_keys/myusername ---------- ID: create_ssh_authorized_key_file_myusername Function: file.managed Name: /var/lib/openmediavault/ssh/authorized_keys/myusername Result: True Comment: File /var/lib/openmediavault/ssh/authorized_keys/myusername updated Started: 00:25:27.757405 Duration: 2.346 ms Changes: ---------- diff: New file user: myusername ---------- ID: create_tmp_pubkey_file_myusername_1 Function: file.managed Name: /tmp/tmpzbwfhxdr Result: True Comment: File /tmp/tmpzbwfhxdr updated Started: 00:25:27.759858 Duration: 25.691 ms Changes: ---------- diff: --- +++ @@ -0,0 +1,9 @@ +---- BEGIN SSH2 PUBLIC KEY ---- +Comment: "rsa-key-20190118" +AAAAB3NzaC1yc2EAAAABJQAAAQEA2V57GdjZF3ypQuOKQ9zObejNXKQYkIfVu2eQ +SxItL1o/5qHK2EAIVdHMUp8pBoOZAc7wBa7gDvhhPGhClBsaC73rWq+p2ntbUFVj +DVmamtGaOyTiS79mtQ/AzIZJO16k9QvfeelAKaj6XkAO5ZFh7VYtYDQDWu5wvyWy +TS67X9dILiSm9U2IbbZQZxvmfAKznVLGU21e7FDjUpIvvabFmWKxUjddlUXXXUCv +ZMibDtXtU1FsEbCuFGYjvo3d4uqwcZK1izSSSAGf0+f6YgxVm2vdKWpaA8BJVMfY +I8ykYNLMPkLddAs8SNtT91Xo108Z7tAhIGA3dJJ+GbTuoH+pGQ== +---- END SSH2 PUBLIC KEY ---- ---------- ID: append_ssh_authorized_key_myusername_1 Function: Name: ssh-keygen -i -f '/tmp/tmpzbwfhxdr' >> '/var/lib/openmediavault/ssh/authorized_keys/myusername' Result: True Comment: Command "ssh-keygen -i -f '/tmp/tmpzbwfhxdr' >> '/var/lib/openmediavault/ssh/authorized_keys/myusername'" run Started: 00:25:27.786159 Duration: 22.557 ms Changes: ---------- pid: 3281 retcode: 0 stderr: stdout: ---------- ID: remove_tmp_pubkey_file_myusername_1 Function: file.absent Name: /tmp/tmpzbwfhxdr Result: True Comment: Removed file /tmp/tmpzbwfhxdr Started: 00:25:27.809399 Duration: 1.746 ms Changes: ---------- removed: /tmp/tmpzbwfhxdr ---------- ID: create_tmp_pubkey_file_myusername_2 Function: file.managed Name: /tmp/tmpp2_vmk6h Result: True Comment: File /tmp/tmpp2_vmk6h updated Started: 00:25:27.811506 Duration: 8.279 ms Changes: ---------- diff: --- +++ @@ -0,0 +1,6 @@ +---- BEGIN SSH2 PUBLIC KEY ---- +Comment: "rs-key" +AAAAB3NzaC1yc2EAAAADAQABAAAAYQDOUxjgVJOyRf/9WeEBfPL567d9wy0HFYfe +VILVQo69Mk/MW3s9HUzUPgyp/LlTNTzgaKxouTpt56SpMWhc3bGASZ8PTSMAljg4 +50YVeKESGFbuAa+VCyvElpInwcT02ec= +---- END SSH2 PUBLIC KEY ---- ---------- ID: append_ssh_authorized_key_myusername_2 Function: Name: ssh-keygen -i -f '/tmp/tmpp2_vmk6h' >> '/var/lib/openmediavault/ssh/authorized_keys/myusername' Result: False Comment: Command "ssh-keygen -i -f '/tmp/tmpp2_vmk6h' >> '/var/lib/openmediavault/ssh/authorized_keys/myusername'" run Started: 00:25:27.820174 Duration: 12.931 ms Changes: ---------- pid: 3283 retcode: 255 stderr: decode blob failed: Invalid key length stdout: ---------- ID: remove_tmp_pubkey_file_myusername_2 Function: file.absent Name: /tmp/tmpp2_vmk6h Result: True Comment: Removed file /tmp/tmpp2_vmk6h Started: 00:25:27.833308 Duration: 0.507 ms Changes: ---------- removed: /tmp/tmpp2_vmk6h ---------- ID: configure_ssh_sshd_config Function: file.managed Name: /etc/ssh/sshd_config Result: True Comment: File /etc/ssh/sshd_config is in the correct state Started: 00:25:27.833923 Duration: 35.578 ms Changes: ---------- ID: start_ssh_service Function: service.running Name: ssh Result: True Comment: The service ssh is already running Started: 00:25:27.878126 Duration: 58.484 ms Changes: Summary for debian ------------ Succeeded: 9 (changed=8) Failed: 1 ------------ Total states run: 10 Total run time: 169.631 ms

    Hello all, just sharing for info.

    I suspected my cheap internal SATA card was causing intermittent POST problems with my old PC box running OMV5 so I looked around for better options and went for this:…AS-SATA-HBA-RAID-319.html

    along with a couple of these:…rget-Cable/dp/B07C15LPWW/

    My PC box has lots of space for drives, using a few 1 to 3 TB drives for a Snapraid array (currently 5 data and 1 parity, another parity on order). Motherboard is old-ish

    Anyway, no firmware tinkering required, it recognised all drives fine, OMV5 was fine with it, Snapraid didn't blink. The cable management is neater too, if you look at the link for the cables above you'll see how it's neater than SATA cables.

    Hello all, not OMV-specific but hope someone can help. The main annoyance with this is that Chrome won't save my OMV webgui login info due to self-signed cert problems.

    I have a local machine and made a SSL cert within the OMV gui. Set it up to be used as the SSL/TLS login cert in gui.

    Chrome 81.0.4044.129 on Windows 10 warns about it, as expected. I imported the cert as per instructions in…r-self-signed-certificate (and elsewhere). But warnings persist, despite restarting Chrome, and "This certificate is OK." in the certification path tab.

    I note that Chrome can balk at certs if subject alternative name is not given, but this seems OK in my cert. I tried it in Edge, which also dislikes my cert. Under the subject alternative name, Edge says "not critical" so I was wondering if that was a problem.

    Possibly related to this point -…ternative-name-in-my-cert

    Any thoughts welcome!