Posts by Mr. Lumbergh

    If only it were that simple. Same error code is generated with the decimal in the right place.

    Code
    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; docker network create -d macvlan --subnet=255.255.255.0 --gateway=192.168.1.1 -o parent=enxb827eb07eac4 WORKGROUP' with exit code '1': in /usr/share/php/openmediavault/system/process.inc:182
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/docker.inc(1082): OMV\System\Process->execute()
    #1 [internal function]: OMVRpcServiceDocker->createNetwork(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('createNetwork', Array, Array)
    #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'createNetwork', Array, Array, 1)
    #5 {main}

    I've finally gotten around to trying this but I'm not getting any love. I reinstalled OMV to give myself a clean slate, but when I get to the stage of creating a new network after pulling the image, I get the following error:

    Code
    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; docker network create -d macvlan --subnet=255.255.255.0 --gateway=192.1681.1 -o parent=enxb827eb07eac4 WORKGROUP' with exit code '1': in /usr/share/php/openmediavault/system/process.inc:182
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/docker.inc(1082): OMV\System\Process->execute()
    #1 [internal function]: OMVRpcServiceDocker->createNetwork(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('createNetwork', Array, Array)
    #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'createNetwork', Array, Array, 1)
    #5 {main}

    I also get this when trying to set a static ip for OMV itself. I'm grateful for any guidance you can give.
    EDIT: I ran ifconfig from the command line in an SSH session and noticed that eth0 had a subnet of 255.255.255.0, but docker had 255.255.0.0. I tried running network creation again but it returned the same error.

    Hello, pardon if this is in the wrong place.
    I have an install of OMV on a Pi 3+ that's been in place for a couple of months. I came across a guide for installing Pi-hole on OMV, which seemed like a great solution since OMV is on all the time. It's an older method that suggested setting the active port for PH to 8080, which I did. Initially, there were no problems. I could log into OMV by going to a browser and typing in its IP for my network: 192.168.1.103; getting into the PH interface just required that I add :8080/admin to the end of that.
    I'm trying to log in now to update the blacklist as some ads are starting to creep back in, and it refuses let me connect on Mac, Raspbian, or PCLOS. Since this has become a problem, I'd also like to reconfigure according to this howto: https://www.mediafire.com/file…c3/HOWTO-PiHole.pdf/file.


    Thanks in advance.

    What does this mean? 'Trying to get Etcher working'?
    Etcher works flawlessly, if problems occur this is an indication that the SD card is faulty. How did you achieve a 'clean boot'? By disabling verify in Etcher?

    Long story, but neither the Linux AppImage nor source that is offered at Github would run on my desktop; I'm not sure if it was a dependency issue or a setting somewhere that prevented this, I haven't been able to suss that out yet. Gave up after a while and went to get the OSX build, but the one currently at Github also wouldn't run on my MacBook, it kept getting blocked as unrecognized. The latest OSX build from the Balena project pages finally ran correctly. After that, getting the card itself detected for some reason also became an issue, as if neither OS recognized it. I reformatted the card but wound up having to go back to the desktop and manually delete the partition I had just created using Gparted, end the session and eject the card, open it again to create the new Fat32 partition in a new session because it triggered an error if I tired performing both actions together and wouldn't cleanly create the Fat partition. After all this though Etcher did get the job done, but I burned a lot of time with all the troubleshooting and workarounds to get there. I didn't disable verify, I figure there's a reason for having this when you're trying to write an operating system to disk, but you're right, I need to keep an eye on this card; it shouldn't have been that much of a pain. Is there a easy way of backing up in OMV that doesn't simply image the card? If there is any corruption, I don't want it to copy also.

    RAID1 can't help here. RAID is about data availability and not data protection. You need backup. And USB RAID especially connected to something unreliable as a RPi is only a great way to fool yourself.

    Interesting, why? My understanding of RAID1 is that the function is the opposite, a fully-redundant mirroring of drives so that if one fails the other can be used to restore onto the replacement and no data is lost.

    Why do you want to use Raid1?
    If you need high reliability, you better use something else than a Raspi and USB drives, that I why I ask.
    Apart from that:
    Software. Otherwise if your enclosure fails, your data is lost. Single point of failure.

    Paranoia, mostly. I've lost things I considered priceless before because of HDD failures.

    I've installed OMV on a Raspberry Pi to use as a network fileshare/media server between another Pi, a MacBook, a Linux laptop, and a desktop booting a couple of 'Nixes and Wintendo 7.
    Attached I have a pair of HGST 1TB drives in a Nexstar GX NST-272S3 dual enclosure I picked up with the intention of using it in RAID1 to serve as a redundant backup of the photos, music, etc. scattered across all my devices as well as share and stream among them and I also will be installing Unison soon to keep everything synced.
    Anywho, on the enclosure I can use DIP switches to set it as JBOD, RAID0, or RAID1, but I see in the WEBGUI that OMV is capable of handling the RAID. Is it best to keep it set to JBOD and let OMV handle the RAID, or use the hardware settings to set the RAID and let OMV just see it as a single drive, and why? I just created the filesystem using the hardware RAID1 setting, but it doesn't have anything on it yet and so would be trivial for me to set in JBOD and configure it in OMV.

    admin and openmediavault is for the webui (go to the IP address in a browser from a machine on your network)


    To log in at the console... username is root.. and I *believe* the password is openmediavault.. however different images seem to have different root passwords... so you need to check the info where you downloaded the image.. it should state what the root passwords is.


    admin cannot log in at the console (or ssh for that matter)


    Ahh, thank you. The WEBGUI, as in, not the command line. I'll catch up eventually.
    I'm dialed in now from my other Pi with Raspbian and OSMC loaded up and things are working fine in Chromium, but now I'm having an issue seeing the attached dual-drive enclosure with the mode manually set to RAID 1. I'm trying to get back in via SSH now because it isn't initialized yet and I don't see an option to do so in the webgui, but can't get to the command line to force mount and format; SSH requests are denied even though I initialized SSH just now via the GUI.

    Pardon if this is a repeat thread, I didn't see anything with a quick search.
    I just installed OMV 4 on an extra Pi 3+ I had. I used Etcher to load the image to a SanDisk 32GB micro SD card, and watched it boot verbose. There were a couple errors that came up but it seemed to be things such as "Microtek Bluetooth Adapter" and the like that I'm not using.
    After a verbose reboot with fewer errors, it popped up with the ASCII-character logo, a few more status lines on WPA Supplicant and the like, I was presented with an info and copyright line, and that was all in line with headless Linux distros I've played with on first boot so I assumed it was standard for this system. It then said to manage the system on the web control panel and displayed the MAC and IP address on the network, admin is account name, openmediavault is the password.
    I tried logging in via SSH from my desktop with Putty. It would connect, accept admin as the user name, but would tag "openmediavault" as invalid and ask again. Thinking it might be an SSH configuration issue I went ahead and plugged in a USB keyboard. No love there either.
    What might I be doing wrong here?


    Thanks.