Posts by danzirulez

    Oh, long time no see... Did not have much time and constantly trying to get myself familiar with OMV version 5.xx.

    So far I am finding it more and more tricky, but I hope it's only due to lack of time to get more experienced.

    Got version 5.x on a rPt model 4B 4 Gig RAM.

    • No Proxmox kernel on this one (at least could not find any)
    • Due to this I might be completely out of luck for a simple ZFS mirror
    • USB drives can't do any other raid - unless you use a USB enclosure
    • Portainer - I am way too dumb for this. I could install some very good containers in OMV 4 with Techo Dad's videos, but can't figure out on the new system

    Hey, many thanks for that.

    I think I was trigger happy and just wanted to install it like some others did. Quick and dirty.

    Only got to know about this option about networking from your post just now. I admint I have not done proper pre-install research though.

    But it's an easy fix and hey, I might just re-image and re-try it the proper way :) good thing is, it's not my production OMV :-)

    Hey, just installed OMV 5 on a Pi 4b with 4 gig ram.

    Used the lite image of rasbian for it and the install script.

    No luck for my wifi either. I am not too concerned with file transfers, but all my lan ports are used by other devices, so would prefer to have the wifi option just for play-around purposes.

    Added my wifi details to wpa_supplicant.conf but can't even get the interface up. Has there been any easy fixes?


    Actually here are the steps so far...

    so far:

    1. edited /etc/wpa_supplicant/wpa_supplicant.conf file - added a network section with SSID and psk.
    2. ran this
      sudo wpa_supplicant -Dnl80211 -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
    3. actually changed it to
      sudo wpa_supplicant -Dnl80211 -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -B
      this way it runs in the background
    4. Can now set Localisation to my country in raspi-config

    Scan works too,

    sudo iwlist wlan0 scan

    shows the available networks, and using raspi-config trying to connect.

    Can also enter SSID and password, it will then show in ifconfig and iwconfig output, but no IP address. :-(

    Ok, so it IS connected, but what's missing is the IP, so what could go wrong...:

    sudo dhclient -4 wlan0

    et voilá.

    I now have an IP address for wlan0 and can access OMV5 on the wireless ip address from a browser. :-)


    found this link too. Perhaps this works too, have not tried it myself

    just a test vm, on an ESXi host.

    This is from dmesg:


    I tried this several times now and it fails every time.

    • install OMV 5.x
    • update via Web Gui
    • SSH in and install extras
    • Install proxmox kernel
    • reboot
    • install zfs plugin
    • wipe disks
    • create mirror

    Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin
    :/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; ls -la /dev/disk/by-id | grep 'sdb$'' with exit code '1': in /usr/share/php/openmediavault/system/ trace:#0 /usr/share/omvzfs/Utils.php(438): OMV\System\Process->execute(Array, 1)
    #1 /usr/share/omvzfs/Utils.php(133): OMVModuleZFSUtil::exec('ls -la /dev/dis...', Array, 1)
    #2 /usr/share/openmediavault/engined/rpc/ OMVModuleZFSUtil::getDiskId('/dev/sdb')
    #3 [internal function]: OMVRpcServiceZFS->addPool(Array, Array)
    #4 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
    #5 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('addPool', Array, Array)
    #6 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('ZFS', 'addPool', Array, Array, 1)
    #7 {main}

    I am sure I am missing something very obvious...

    thanks in advance

    Hi Adoby,

    Thank you for the tip. I actually realised that since I planned to install OMV in a VM that would sit on SSD vmware store, the USB issue is out of the equation. So in that regard - wouldn't it be better to use the docker_user's home folder? Although this would require that the OMV system disk is also backed up I guess...

    I found the option just now: it defaults to /var/lib/docker if unset).


    • XigmaNAS config files for Transmission and PLEX are also on a data drive, I guess I am just inexperienced with OMV yet.
    • Creating a folder under sharedfolders for docker doesn't mean I HAVE to share that 'further' via SMB to clients - so there
    • One question though: wouldn't I be better off putting the /srv/disk-by-id...etc path in the docker config? That will be an always valid location even if shared folder configs aren't working well for some reason...

    Part I.

    Ok, decided to start kind of a blog.

    Long story short, I started using FreeNAS back at around version 0.7.x and fell in love with the USB drive-installable system, with ZFS. Had it running on an ATOM mobo with a fairly slow cpu. 3x1.5 Tb drives in a RaidZ1 setup. I stayed with the same OS through the Nas4Free years and even today when it is called XigmaNAS - same system, although the underlying hardware was switched first to a Dell PowerEdge T20 with the same 3 drives, + 1 without redundancy, then to the current PowerEdge T130.

    Today's setup
    is an ESXi host on the bare metal, XigmaNAS is on a root-on-zfs mirrored VM, an LSI 9211-8i card passes through a 2x2Tb ZFS mirror, and a 3 Tb not-so-important data drive to the XigmaNAS VM.

    The ESXi host has one single 500Gb SSD storage for holding the VMs. (so the aforementioned root-on-zfs mirror probably only makes sense for the XigmaNAS upgrades, where you have the chance to revert to the previous install should something go awry).

    The host give home to occasional Debian, Ubuntu, Windows, FreeBSD and other VMs I use for work and home test lab.

    Pros & Cons


    • As much as I got familiar enough with FreeBSD, I feel that linux has a much larger user base and probably a more active development
    • With Docker Support I found so many containers to my liking, it is vastly new, broader and wider world to me than what XigmaNAS offers today. (don't mean this as a negative comment really, after all, I used it for like 8 years :thumbsup: )

    Not really cons rather than my worries and learning curve milestones I guess:

    • Doesn't seem that the Proxmox kernel was something bad, but I hope ZFS gets added to the 'regular' repo, I am a bit shy to tinker with the kernel, but hope someone here reassures me not to be. Or else, maybe I don't really need ZFS?
    • Some of the Docker concepts are very new, and configuration can be a bit confusing here and there... lots to learn, but hey, I am lazy. This will get even more tricky with Portainer in OMV 5... I tried, but got lost...
    • A bit worried about installing OMV on USB - again, plugin is there, but then where do I put the docker config files? Bit confused, hope that by X-Max I will become an OMV enthusiast :rolleyes:

    Requirements for the new system:

    • ESXi on the metal can stay put. Works as expected and hosts a lot of other VMs already
    • I want to have redundancy both for OpenMediaVault and the other VMs (basically use some kind of mirror for the ESXi storage I guess, but I have not done this before...)
    • Passthrough mode for the LSI HBA dedicated to OMV - data disks will be handled by OMV
    • Redundancy for all data that I have - be it SnapRaid, or stick to ZFS and another mirror, yet to decide
    • Docker config - looking out for best practices where to put the /config files for the containers, etc
    • Probably replacing PLEX with EMBY... I experience a lot of slow network response and long buffering times when continuing an episode or a movie... with EMBY it was pretty much instantaneous from my old test box, which is a ridiculous-in-comparison N40L HP Microserver, that is 8 years old now.
    • Same goes with transmission - lacks some features, eg. delete after x days or hours of seeding, especially since on my test box with PLEX I now have a 2nd copy of everything, one is in the complete folder, one is in PLEX's media - although probably just a config issue.
    • Docker containers, Docker containers, and even more Docker containers :) Well, only the ones that I got to like really.

      • Heimdall
      • Sonarr
      • Radarr
      • Jackett
      • EMBY or Plex
      • Transmission or another torrent client
      • Pihole
      • PXE and DHCP and SFTP for booting VMs from some images...
      • Some home automation
    • Anything that comes to my mind during or after the install. or you'd recommend to have :)

    Sorry for the long post, but Techno Dad Life's videos MADE me do it!! 8)

    Some caveats I'd note.

    What is the filesystem and how will you access it? I'd say mounting a drive with data on another operating system should be fairly safe, but just make sure the new OS supports whatever fs you already have on the disk with your data.

    And a backup never hurts.

    don’t use that path for services. Use the original path at /srv


    Am I getting this right, that actually all docker 'mapped' folders should point via /srv, so that even if the sharing setup changes, a docker 'app' would find its ways to its designated folders?

    I meant that the 'appdata' folder that Techno Dad Life refers to - is no longer on the sharedfolders path. In another guide here on the forum I read that it was better to create a 'dockerperson' user specifically for the docker containers anyway...

    So I am using that now, and all the configs for the containers go under this users' home folder.

    Just wanted to clarify these two things.

    Thank you

    Hi All,

    Watched Techno Dad Life's super easy video tutorial about duckdns on OMV, but just was thinking if I ever needed a docker for this, or can I just use a cron job to run every hour for a quick update...

    Isn't that more lightweight? Or am I missing out on some super features without the docker container for duckdns? ?(


    Hi All,

    I have installed

    • transmission
    • sonarr
    • radarr
    • plex
    • jackett
    • heimdall

    all in docker, and sonarr gets hold of the new episodes for the series... however, now I seem to have all downloaded media twice - once in the download folder of transmission and once in the plex media folder.

    I believe this is down to config issue, but cannot figure out what the solution is. ;(

    Transmission docker's /download variable points to a sharedfolder's root, so it creates two subfolders here for itself, 'comlpete' and 'incomplete'.

    Plex docker's variable for /media is the same sharedfolder's root location - under which I have 'movies' and 'series'.

    Although sonarr does put the episodes correctly under series/<show title>/<season number>/episodes, I do have the same files under transmission's complete folder too... ?(

    Would I be better off with another torrent client? 8|


    Hello All,

    Quite new to OMV, but I like it a lot. Generally different concept from what I have been using so just trying to get the concept.

    SharedFolder would be a conceptual pointer to a folder, but when creating and giving it a name, OMV would go ahead and actually add the folder itself to the selected device.

    So if I want to share the whole disk, I would delete the name and use / in the path.
    Caveat here: the actual device would probably be non-writeable, since the top level folder of the device is owned by root

    And then Samba would take this one step further and re-use the pointer and take it from there... right?

    hm, that would be interesting... no, no boot order issue, since the drive is alone, and it does get to grub - at least to some extent.

    I do have another WD USB driver, an older passport one. I did boot off OSX from that ages ago, maybe will give that one a try.

    Also, there's a SATA-to-DUALUSB connector that I have for notebook HDDs, and that worked too, so the WD enclosure could indeed be the culprit.

    Thanks for helping me investigate guys, much appreciated!

    I used balena etcher to write out the iso installer on a flash drive.

    I can use this to boot the installer and install OMV to the WD Element USB connected HDD. This disk is connected to the on-board USB plug.

    During the install /dev/sda is the WD element and /dev/sdb is the thumb drive.

    All installs fine, grub goes through fine too.

    Then when I reboot - I just get that error message, normal.mod not found and grub's prompt, that's it.

    No blue screen, no countdown.

    At the moment I have an internal sata disk instead. It is connected to the optical disk sata port and this way it boots fine.

    sda8:00 149.1G0 disk
    |-sda1 8:10 133.2G0 part /
    |-sda2 8:20 1K0 part
    `-sda5 8:5015.9G0 part [SWAP]

    There's no countdown... as soon as the post passes the pxe and press F10 and F12 menu, I am presented with the few lines of text and grub as it is on 1.jpg.

    ls command was typed in by me, but that's it, grub rescue> prompt and nothing else.

    I am re-trying now with another solution - just hooked a disk on the optical drive sata port and that seems to resolve the issue, wanted to learn my way around grub a little bit, now that (yet again) it tricked me.

    This is weird.

    I can mount the filesystem on my mac and I can see the contents of /boot/grub

    Yet when I try to ls the folder in the grub menu, the folder is empty...

    I was under the impression that I could still boot the system and then repair grub when I only have this one disk attached to the system?



    • 1.jpg

      (505.51 kB, downloaded 138 times, last: )
    • 3.jpg

      (524.6 kB, downloaded 138 times, last: )
    • 2.jpg

      (677.34 kB, downloaded 138 times, last: )
    • Screen Shot 2019-10-08 at 14.58.28.png

      (37.28 kB, downloaded 129 times, last: )