Posts by Genna

    thanks gderf

    So, maybe the best way, actually, to have OMV 5.x is to install OMV 5 on new partition/drive from iso/usb stick, as a new drive and then mount volumes.

    I use on most of my systems, raid card like lsi or HP. In fact, installing a new OS is not a problem for shared volumes.

    thanks.

    i will use your method on a test system.

    Hi,


    i 'm wondering where i could find the method to migrate/upgrade OMV 4 to 0MV 5 ? if it exists.


    I remember that i asked same question about 3.x to 4.x upgrade, but really, in this forum, even in pinned topic, i didn't found my subject.

    in 4.x, i had to reinstall from scrath all my OMV systems.


    in omv-extras plugin, upgrade does not the job i want. all my 6 systems are up-to-date, in this openmediavault 4.1.35 version. they work fine.


    Before migrating, i would like to test one of them to 5, without re-installing all.


    i read this read-me-upgrading-to-a-new-major-version-of-openmediavault and this documentation


    Do i need to upgrade Debian 1st, 9.x to 10 ?


    i apologize, if it is about my english understanding.


    thanks again.


    :)

    hi,


    yesterday evening i was trying to install a new OMV4 on a motherboard, x58, 8GB ram, 1 only drive = SSD 120GB. No hw card, no more disk (for the moment)
    after a lot of different tries, i always get "mdadm message".


    with or without OMV usb stick present on boot.


    so i decide to change bios settings, no boot on USB.
    But using the button to select which boot drive. So, in this ways, system sees only my SSD. (for the moment). You can set SSD/HDD boot Before USB.


    Just before installing OMV i do this:


    I also put my SSD into a Win10 PC, it was the 5th disk into it. Then with run alt-Win, cmd, Diskpart, i ran a couple of commands (List disk, Select disk 5, clean - be careful, it is fast). To have No partition present on SSD. (equal gparted). SSD is now Not initialized, what i wanted.


    unplug it.


    plug in future OMV system.


    plug usb stick (omv4)


    as there is an only bootable drive was present (the usb stick, not the ssd, because, it has been erased before with previous action), OMV install began.


    And during OMV installation, i could see, this: for the 1st time, SDA1 was selected and prefered as SDB1, as never as my few previous install since yesterday, even if OMV USB stick was present.


    So, when OMV install usb stick is present, and you decide to install to a drive, be sure that your new drive was clean, no partition, no previous partition information. AND in your BIOS, do not select USB drive before HDD/SDD (just for the install of OMV).


    This is how i get a new and fresh install on OMV with 1 only SSD, and from its OMV install USB key (no need to change anything in grub or mdadm.conf). without mdadm issue.


    Thanks for your precious help.

    i tried different things (omv-firstaid, dhcp on or dhcp off, with manual ip editing), same.


    as it was my first omv5, and very recent, i decided to reinstall OMV 4 from scratch, i did not see any dns issue. Maybe i made some stuff wrong.


    back to omv4, with openmediavault_4.1.22-amd64.iso on 16GB usb stick. all my omv system use finally same version.


    for next try, what do you propose to me if i get this error ?
    for instance, like this way ? => Losing DNS settings whenever, I install a portainer and docker.


    thanks

    Hi,
    This is what i did to fix the "OMV" issue:

    • in bios, i set to disabled pci-express slot where was connected my raid card.
    • reboot.
    • login
    • editing mdadm.conf with nano /etc/mdadm/mdadm.conf
    • adding ARRAY <ignore> devices=/dev/sda
    • save
    • reboot
    • enabled pci-express slot

    same error.


    Then, I checked on different OMV 4.x machines of mine, and there is in mdadm.conf at the end of file, a section with:


    Code
    # definitions of existing MD arrays
    ARRAY <ignore> devices=*

    this machine runs OMV4 and have 1 SSD and 1 Raid HW volume (with card).
    /dev/sda1 => raid HW volume
    /dev/sdb1 => ssd OS.


    but on the new machine, issue.
    During my different checks, i start my machine, with disabled pci-express slot, and in OMV webgui, i could see raid HW volume. I was surprised.
    And i understood what was wrong:


    it was not disabling pci-express slot, but disabling Bios on pci-express slot. So, with disabled bios pci-e slot, my OMV works fine, my Raid volume is mounted, and i opened mdadm.conf file,
    there is nothing after this line # definitions of existing MD arrays


    So, there were a lot of messages mdadm during boot, because of my wrong settings in bios. Not OMV cause.


    thanks :thumbup:

    hi,
    new install of OMV 4 on SSD, from bootable usb sitck, on motherboard 775 socket, e8400, 8GB ddr2.
    after rebooting, all was fine. Setup in OMV webgui, network, ip address, ... all was fine.
    shutdown
    install LSi card, 8 sata ports. Plug 8 hdd. setup in lsi bios virtual drive, fine.
    boot on ssd... and


    mdadm : no array found... messages, a lot. without stopping, until new small OS cli.


    a few commands exist in this small reduced os.


    i think, OMV tries to boot on my new LSI volume which has never been formatted, because never succeed to run omv gui.


    /dev/sda1 is certainly lsi volume. Where is my SSD ? how can i know uuid of my ssd, without disconnecting lsi card ?


    maybe i have to install a small omv3 on a new ssd, just to have omv gui, and then having time to initialize lsi volume as ext4 raid 6.


    what i don't know is:


    how to get debian prompt with unplug anything ?
    what is the command line, in small os (i don't remember its name) to access to mdadm.conf on ssd ?


    if you have some single steps.


    i can try to install on another new ssd, omv5 :) or older omv3.
    in fact all my omv (i have some running systems) are made from OMV3, and were upgraded to omv4, or, the hw raid array were already created and initialized)


    it is this reason, i am pretty sure that there is a mistake on omv installer (or debian installer), for new user, who want to run 1st omv install, and then plug new raid volume.
    take time, please, to answer or help me, my new big system is initializing raid 6... for a few days :)


    i am sure the solution is not far...

    ok, thanks @votdev
    do i need to do something with journald ?
    thanks


    Bash
    # journalctl --disk-usage
    Archived and active journals take up 4.9M in the file system.

    Hi everyone,


    i would like to delete logs on my OMV 4.1.28-1, in Diagnostics/System Logs section.


    clear button is available on almost all of items present in list, except "boot".


    how to clean this one :?: ? i have a lot of pages. :/


    thanks :)

    Hello,


    if possible, i would like a button to empty the trash directly, in SMB/CiFS section or Filesystem.
    Actually, the only way from OMV Web UI is open SMB section, then Shares, then Edit shares then scrolling Edit Share Window then clicking on the loved button Empty Now ^^ -Edit Share Window is too small.


    Thanks.

    Hi,


    after some OMV 4.x upgrades, and some fresh installs on different PCs, i can see on my network through win10 filebrowser my last "domain name" or "really old nas name".


    only SMB used. global option ntlm auth = yes


    for example,


    i set "workgroup" as domain name in "web ui/system/network section", and i can see "nas-genna.home" and also "NAS-Genna" in my filebrowser. Why ?


    new example:


    in OMV3, i created a new system named "NAS-OMV3", OMV3 on SSD. After reinstall OMV4 on new SSD (previous partitions deleted), and domain name = Workgroup, nas name = "NAS-OMV4". I can see in my file browser, "nas-omv3.home" and also "NAS-OMV4".


    How purge them ?


    what is the explanation ? i do not see where i missed a setting


    thanks again


    #~ ## ~#
    edit:
    in OMV webui, Services // SMB/CiFS // Settings // Home Directories // enable & browseable are Off

    my system is OMV 4.1.22, new install. and works, except this error message in mail.


    chown --help works !
    chown -R postfix /var/spool/postfix works, after deleting spaces and rewriting all the command (maybe some bad characters from paste)


    i will see :)
    thanks

    Did you change the owner from root to the system name? This thread probably has your fix - https://forum.openmediavault.o…penmediavault-flushmailq/

    I did not change anything. Thanks for the link, i have already read it before posting my message, but as my OMV 4.1.22 is completely new on a new SSD, i was not sure about the reason


    'chown' command is unkown... lol why unknown on a fresh and new install of OMV 4.1.22 ??


    i 'm going to install chown ... oups. No, chown is already installed, chown --help works but this chown -R postfix /var/spool/postfix returns error

    what is the output of: ls -al /var/spool/

    Hi,


    this is the 4 outputs of ls -al /var/spool/


    1st with email with error:

    Code
    drwxr-xr-x 7 genna1 genna1 4096 avril 20 13:49 .
    drwxr-xr-x 12 genna1 genna1 4096 avril 20 13:49 ..
    drwxr-xr-x 2 genna1 genna1 4096 avril 20 13:55 anacron
    drwxr-xr-x 3 genna1 genna1 4096 avril 20 13:49 cron
    lrwxrwxrwx 1 genna1 genna1 7 avril 20 13:49 mail -> ../mail
    drwxr-xr-x 20 genna1 genna1 4096 avril 24 00:36 postfix
    drwx------ 2 genna1 genna1 4096 janv. 18 2017 rsyslog
    drwxrwxrwt 2 genna1 genna1 4096 mars 5 2018 samba


    2nd system, without error:

    Code
    drwxr-xr-x 7 genna2 genna2 4096 avril 10 2018 .
    drwxr-xr-x 12 genna2 genna2 4096 sept. 27 2017 ..
    drwxr-xr-x 2 genna2 genna2 4096 sept. 27 2017 anacron
    drwxr-xr-x 3 genna2 genna2 4096 sept. 27 2017 cron
    lrwxrwxrwx 1 genna2 genna2 7 sept. 27 2017 mail -> ../mail
    drwxr-xr-x 20 genna2 genna2 4096 avril 23 19:51 postfix
    drwx------ 2 genna2 genna2 4096 déc. 19 2015 rsyslog
    drwxrwxrwt 2 genna2 genna2 4096 juil. 14 2017 samba

    3d system, without error:


    Code
    drwxr-xr-x 7 genna3 genna3 4096 avril 10 2018 .
    drwxr-xr-x 12 genna3 genna3 4096 nov. 18 2017 ..
    drwxr-xr-x 2 genna3 genna3 4096 nov. 18 2017 anacron
    drwxr-xr-x 3 genna3 genna3 4096 nov. 18 2017 cron
    lrwxrwxrwx 1 genna3 genna3 7 nov. 18 2017 mail -> ../mail
    drwxr-xr-x 20 genna3 genna3 4096 avril 18 19:38 postfix
    drwx------ 2 genna3 genna3 4096 déc. 19 2015 rsyslog
    drwxrwxrwt 2 genna3 genna3 4096 juil. 14 2017 samba

    4th system, without error:

    Code
    drwxr-xr-x 7 genna4 genna4 4096 mai 3 2018 .
    drwxr-xr-x 11 genna4 genna4 4096 mai 3 2018 ..
    drwxr-xr-x 2 genna4 genna4 4096 mars 9 2018 anacron
    drwxr-xr-x 3 genna4 genna4 4096 mars 9 2018 cron
    lrwxrwxrwx 1 genna4 genna4 7 mars 9 2018 mail -> ../mail
    drwxr-xr-x 20 genna4 genna4 4096 avril 20 11:52 postfix
    drwx------ 2 genna4 genna4 4096 déc. 19 2015 rsyslog
    drwxrwxrwt 2 genna4 genna4 4096 nov. 12 2017 samba


    As you can see, all my 4 systems seem similar, except username (root) or dates.


    thanks

    hello,


    i activate notifications, on my 4 systems, recently upgraded or reinstalled.
    The last one, which has been upgraded 3.0.99 > 4.1.22-1 sends to me an email with this error:



    Code
    /etc/cron.daily/openmediavault-flush-mailq:
    postsuper: fatal: scan_dir_push: open directory hold: No such file or directory
    run-parts: /etc/cron.daily/openmediavault-flush-mailq exited with return code 1

    what do i have to do or set ?


    thanks.

    You only needed to uninstall the hpraid plugin since it doesn't exist on OMV 4.x.

    There is an uninstall button in the Plugin tab. Select the plugin(s) and click it is all that is required.

    Clear your browser cache. Problem #1 - https://forum.openmediavault.o…tions-to-common-problems/

    While the OMV 2.x -> 3.x upgrade was a challenge because it added the change from sysvinit to systemd, the OMV 3.x -> 4.x upgrade is much better in most cases.

    Hi,


    my last OMV 3.0.99 system has been upgraded and updated without big issues or error messages.


    1st, yes, after upgrade or update, cleaning cache or changing internet browser was a good idea. For instance, OMV-Extra was displayed as OMV 3.xx version, just after a reboot, but in the same browser.


    2nd, after point 1, in fact, no more rpc error message.


    3d, upgrade than update, some reboots to be sure. All was good.


    My 4 systems are now based on OMV 4.1.22-1 and work great.


    PS: Always, same translation error into login page, size words too long for this small popup window. English choosen instead.


    Big Thanks to @ryecoaaron for his patience with me :)

    thanks again and always, Aaron, as your answers are limpid.
    About hpraid yes, uninstalled like you said to me few weeks or months ago.
    I really don't know what was wrong.
    But now, i know how to and what to do if it crash, I will upgrade my last one with upgrade command.
    Thanks a lot, Aaron , again

    On 4 systems using omv,


    omv 3.0.99 -> 4.1 => 1 update/without issue, except errors in web interface, during a update check in update management section, fixed with a single reboot.


    1 update with issues, fixed with changing sources.list (i copy the us repositories instead of fr, seen in openmediavault documentation)


    1 update crashed omv. Web interface displayed All updates as it was a new 3.0. As i use a logical volume managed with an raid card, i get out my ssd, plugged it into my pc, deleted partition, and plugged it back into my nas, and re install from scratch, with bootable USB stick and omv 4.x


    1 kept in 3.0.99, and i think, reinstall omv4 on a clean ssd.


    Why?


    I only used omv extras, backup (what for?), and hpraid plugin.


    Before upgrade, i tried to uninstall all these 3 plug-ins. Not sure that omv propose an easy way to do that. I always had some messages rpc... because plug-ins were uninstalled but in menu, lines were displayed yet.


    That s all.


    So, in my 4 cases, same installations, different situations.


    As I said previously, my raid arrays are not managed by omv, I prefer installing new omv4 on clean drive than upgrading, because Debian dist upgrade, omv engine upgrade, update,... a lot of potential issues. And i didn't understand error messages without asking here. My english is not good too.


    Thanks for your help