OMV 3.0 after OMV 2.0

  • omv-mkconf monit
    apt-get -f install

    Ran the codes. Here are the results.


    Errors were encountered while processing:
    openmediavault
    Creating index of upgradeable packages ...
    Creating index of openmediavault plugins ...
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    Should I run that same code for openmediavault?




    sounds like a slow stick.

    BTW, my stick is a USB 2.0. I had read somewhere (might have been on FreeNAS when I was looking at that) that USB 3.0 was not advised, so I deliberately acquired a 2.0 stick.

  • After omv 3.0.47 upgrade, errors preventing me from moving forward. I went to omv-firstaid to configure the network interface and got this error message:


    ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:


    Error: Expected at least 6 tokens for --menu, have 4.
    Use --help to list options.


    Between this error and the previous one I listed, I don't know what to do at this point.

    • Offizieller Beitrag

    Between this error and the previous one I listed, I don't know what to do at this point.

    I don't either. I am really tired of failed upgrades. I think you should install virtualbox on your desktop/laptop and practice installing OMV 3.x on a virtual machine. Then install on real hardware.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I don't either. I am really tired of failed upgrades. I think you should install virtualbox on your desktop/laptop and practice installing OMV 3.x on a virtual machine. Then install on real hardware.

    Wow. Wasn't expecting that :( . Is there a way to do a fresh install of 3.0.47 without going through the upgrade process?

    • Offizieller Beitrag

    Is there a way to do a fresh install of 3.0.47 without going through the upgrade process?

    Use the 3.0.36 iso from here. Then update to 3.0.47 from the updates tab.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Use the 3.0.36 iso from here. Then update to 3.0.47 from the updates tab.

    OK. Installed 3.0.36 and it went through the normal installation process, including the host and domain setup. But ifconfig is only showing the lo information, and there is nothing on the eth0. When I run omv-firstaid for network configuration it displays "eth0 Ethernet Connection I217-LM". I take the defaults on the rest of the questions, and the display then says:
    "Configuring network interface. Please wait ...
    ERROR: address: The value ' ' is not a string."


    Any ideas?

    • Offizieller Beitrag

    I don't know why I was expecting things to just work...


    omv-firstaid probably needs to be updated but you need network for that. So try:


    dhclient -v eth0


    If that doesn't give you an IP, try (obviously it may need to be adjusted for your network):


    ifconfig eth0 192.168.1.23
    route add default 192.168.1.1
    echo "nameserver 8.8.8.8" > /etc/resolv.conf

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    omv-update
    wget http://omv-extras.org/omvextras3.deb
    dpkg -i omvextras3.deb
    omv-aptclean
    apt-get install openmediavault-flashmemory


    then enable flashmemory in web interface. Don't worry about the changes in the flashmemory notes.
    reboot

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • omv-update

    Woo Hoo!!!! omv-update went through without a hitch!
    (also glad that this time I used a USB 3.0 stick :) )


    Now onto the omv-extras.


    But one quick question: on the omvextras.org site, the guide says the filename is "openmediavault-omvextrasorg_latest_all3.deb" but your instructions here say just omvextras3.deb. I will go by your instructions, but was curious what the difference is.

    • Offizieller Beitrag

    That is the experience I wanted to hear about.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Hmmm ... had to run this again to get access to ethernet.

    I thought you might. See if eth0 shows up in the Network -> Interfaces list. If not, add it, If it does, edit it and save.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    You have a shared folder created for it or it is being used by a plugin.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Worked perfectly! Rebooted, ran ifconfig and eth0 is now showing. Now I'll setup my HDDs. Stay tuned

    Good to hear. I may not be on much the rest of the day. It is beer:30 :D

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • You have a shared folder created for it or it is being used by a plugin.

    Hmmm ... I reinstalled the drives after I went through all the setup and installing the plugins we needed. The drives are currently formatted as ext4 and I want to get them to btrfs. Could it be that the weird UUIDs as NTFS that were showing up under Stone Burner were on that drive? Or that all the bizarre issues I was having and things I was trying, ended up putting something on that drive?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!