OMV Config vs FSTAB, FSTAB looses every single time even with external help.

  • Hi,
    I have re-installed OMV on the latest Debian.
    When I say i re-installed omv, i mean I created a new virtual disk and installed Debain and OMV. The 4 Data disks (Raid 5) were not touched so the data stays. (Had to re-install because after a dist upgrade on XENSERVER, it broke...)

    It has detected my RAID no problem and as attached it.


    root@OMV:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : active raid5 xvdb[0] xvde[2] xvdf[3] xvdc[1]
    5860538880 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

    unused devices: <none>

    When I try to mount the volume that was previously created in a previous install, it throws this error.

    I run


    omv-mkconf fstab

    but it doesn't help me in any way.
    Here is some background info...

    So this is what I try now...


    cat /etc/openmediavault/config.xml | awk '/<fstab>/,/<\/fstab>/'

    and get this...

    So i give /etc/fstab a helping hand... Add the entries by hand...

    Now the mount works...

    But as soon as I create an folder, NFS share and save my config again, look at error message i get and the output of the fstab.

    Any clue on what may be going on?
    Why does creating an nfs share erase the entries in the fstab? They remain in the config file though.

  • You are running OMV on Jessie (Debian 8). This is not supported nor works properly.

    Very good point! (I know this because I followed this guide... [Guide] Howto install OpenMediaVault on Debian 8.x (Jessie) TESTING - EXPERIMENTAL )
    On the other hand, isn't it a good case to debug for the official supported version on Jessie? If I wanted real support, I would of get Nexenta with a support contract, or i would of atleast installed a supported OS / Software combination. :P
    If debugging this issue is a defiant "faux pas", then we can discard this tread... ||

  • The support issue isn't really that big of a deal. The fact that many things just don't work is a much larger issue. OMV 2.x is nowhere near ready for jessie. So, debugging is not really needed since changes haven't been made to work on Jessie. Is there a reason you need Jessie?

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2 plugins source code and issue tracker - github

    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!