My take on OMV6

  • Just testing OMV 6.0.5-2 on a separate testing machine:

    Yes, I know its early stages.


    smb, ftp, ssh and Rsync work fine. Yay!

    External NTFS formatted USB drive works at acceptable speed 8)


    The quirks I have found so far:


    1.) Dashboard Configuration it not saved. Yellow bar confirmation is missing.


    2.) No formatting of disks via GUI. Can only wipe. Must use command line fdisk.


    3.) When installing a drive with files, it is not possible to select the existing shares

    via the gui, unless you know the directory names used.

    Found "Browse directories". Silly me.


    4.) Can not install any packages via GUI. Getting error message

    "Could not resolve 'packages.openmediavault.org')


    So far so good. Thanks Volker for the hard work.


    PS:. Long time user of OMV starting a long time ago with FreeNAS

  • Dashboard Configuration it not saved. Yellow bar confirmation is missing.

    Dashboard setting are stored via cookies.


    No formatting of disks via GUI. Can only wipe. Must use command line fdisk.

    On a NAS it is not necessary to create partitions; or at least this is not the concept of OMV. The disk is partitined with one big GPT partition when creating a file system.


    Can not install any packages via GUI. Getting error message

    Your DNS is not configured correct.

  • Dashboard setting are stored via cookies.


    On a NAS it is not necessary to create partitions; or at least this is not the concept of OMV. The disk is partitined with one big GPT partition when creating a file system.


    Your DNS is not configured correct.

    Correct. I have all cookies permenently switched off and this will remain so.
    Was thus surprised by this inconsistency. Maybe a "Select all" button would be helpful.


    Agree. Missed Create/Mount.


    Yep. Missed the DNS setting under "Advanced".



    Thanks for the quick response to my errors.

  • Backupmaster

    Changed the title of the thread from “May take on OMV6” to “My take on OMV6”.
  • I like OMV 6 so far. :)


    After getting some upgrade quirks fixed I found that everything except denyhosts which I have had running for years survived and that may have become broken recently on OMV 5 due to some python version deprecation. I easily switched to fail2ban to solve that one.


    One problem did carry over from OMV 5. In Diagnostics Performance Statistics Memory Usage the graphs are still absent and only frowns are shown. On the Dashboard, the Memory widget does display a pie graph, so OMV can read the memory usage.


    One thing I would like to see is the ability to easily remove old unused kernels in the new Kernel section.


    Thanks again for all the great work on this release :!:

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 6.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • One problem did carry over from OMV 5. In Diagnostics Performance Statistics Memory Usage the graphs are still absent and only frowns are shown. On the Dashboard, the Memory widget does display a pie graph, so OMV can read the memory usage.

    Do you have monitoring enabled?

  • Do you have monitoring enabled?

    Yes, it's always been enabled and all the other graphs are there properly.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 6.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Dashboard setting are stored via cookies.

    I think that's a poor choice. I use 3-4 devices to access OMV and setting up the dashboard for each of them (and setting them up again when for some reason I need to erase the cookies) is gonna be a pain

    HP Proliant Microserver Gen8, E3-1265Lv2, 16 GB ECC RAM, 3x WD RED 3TB + 1x WD RED 4TB + Crucial MX300 525 GB SSD.

    Powered by Proxmox VE

  • I think that's a poor choice. I use 3-4 devices to access OMV and setting up the dashboard for each of them (and setting them up again when for some reason I need to erase the cookies) is gonna be a pain

    They are client side settings. Where would you store them?

    omv 6.0.8-1 Shaitan | 64 bit | 5.15 proxmox kernel | omvextrasorg 6.0.5 | kvm plugin 6.0.3
    omv-extras.org plugins source code and issue tracker - github


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

  • is there a reason they have to be client side settings?


    also a few other things that bother me in OMV for a while and I was hoping them to be addressed in 6.x:

    - having to apply each and every setting is quite annoying. i understand it for some crucial settings but i feel most screens could do without it, simply applying them when pressing OK

    - managing shares is overly complicated, with creating the shares itself, then sharing them via the respective services entirely elsewhere in the menu. i think all settings related to the shares should be under Storage / Shared folders (e.g. FTP, SMB, NFS, etc.) and the Service menu should be used only to manage the settings related to the particular service

    HP Proliant Microserver Gen8, E3-1265Lv2, 16 GB ECC RAM, 3x WD RED 3TB + 1x WD RED 4TB + Crucial MX300 525 GB SSD.

    Powered by Proxmox VE

Participate now!

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