Posts by sonofwatt

    Tried to log into the web gui today and was told my username or password was incorrect. Tried the usual stuff, no luck. I'm certain I didn't change my password since the weekend, but decided to just do a re-set with omv-firstaid and be done with it.
    When I try to execute the control panel admin password change, I get the following error.
    Updating control panel administrator password. Please wait ...
    ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; usermod --password '$1$wITgGd9N$iASwhljseorIBYRc.f5hx/' admin 2>&1' with exit code '1': usermod: cannot lock /etc/passwd; try again later.

    I did find this thread with a similar issue, but the steps listed there don't work for me. https://forum.openmediavault.o…update-OMV-on-raspberry2/

    Also, I'm not sure if this matters, but the system seems sluggish.

    Any ideas?

    Hey guys, How do I uninstall Shellinabox?
    I "uninstalled" it from the plug-in list, even tried a restart of the server, but it's still showing in the left side menu under Services.

    When I click on Shellinabox now, I get this error.


    Error #0:

    OMV\Rpc\Exception: RPC service 'Shellinabox' not found. in /usr/share/php/openmediavault/rpc/
    Stack trace:
    #0 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Shellinabox', 'getSettings', NULL, Array, 1)
    #1 {main}

    Then something in the bios is throwing this, is there a bios setting to enable ahci

    This server the HP DL360 G7 apparently doesn't support AHCI.

    At a guess, it's BIOS related? And there may to 2 BIOS' involved, the host adapter and the motherboard.
    ryecoaaron has way more experience with something like this. I've never seen anything like it.

    (The only thing that comes to mind is, with building a USB thumb-drive and the Debian installer said something like, "error partitioning drive - reboot recommended" or something like that. I rebooted, went through the install routine again and on the second time around all was fine.)

    There definitely is a BIOS on the SAS card, but I ran into the same issue after I'd physically removed the card.

    At this point I've installed OMV to various SD cards and USB thumb-drives easily a dozen times, and haven't seen that error. I guess this older server just isn't easily compatible with OMV or Debian.

    Yes, run swapoff from the command line. And no, just idling along would not be a valid test. Only operations that use up all the memory would trigger a swap, and if there is no swap available the machine would crash.

    I ran swapoff, and did as much as I could to test the system. Was able to run a Windows VM without any problems. I used DiskGenius to erase the Linux Swap folder, then expand the primary partition. The system would boot, but not without a screen of error messages.
    The first screen was filled with this message again and again mdadm: No arrays found in the config file or automatically, then later at the bottom before loading OMV, A start job is running for dev-disk-by\(long list of characters).device.
    I tried creating the OMV disk again from scratch, then using DiskGenius again. Same errors. So I guess the Linux Swap is needed.

    Last night I played around, and physically removed the PCI-E SAS controller from the system and completely removed the sas cable from the backplane/system. I still got the hd0 error!
    There aren't any sata power connectors on the mobo, so it would be a chore to go that route.

    With the user in the other thread using a sata controller, wouldn't that be like my setup with this HBA controller card? (Assuming it is working properly and is in IT mode)
    The card is an LSI 9207, and the server is an HP DL360 G7.

    @gderf Can you think of any problem with using the 32GB card as is? The boot partition is 5.7GB. If I remember, the minimum install volume size for OMV is 4GB? So 1.7GB left over. Will that cause issues for logs, or any temp files that might accumulate?

    Also, wondering how you were able to install to an SSD the same size as your systems amount of RAM? When I try to use a smaller SD or Flash Drive, I get the error Failed to partition the selected disk. This probably happened because the selected disk or free space is too small to me automatically partitioned.
    When I first ran into this error the other week, I did some research and found people talking about the Linux Swap volume needing to be the same size as your system RAM.

    No it's not, but the hd0 error has something to do with the backplane, I'll see if I can find the thread where this came up but HP's can be an issue but not impossible to resolve.

    I'm really confused! I thought the physical backplane was a 'dumb' interface. Just a physical connection to some sort of controller.
    Yes please do, this is so weird.
    I wonder if the SD reader is managed by the same chipset that would be in use by the motherboard's onboard SAS controller.

    Yes, run swapoff from the command line. And no, just idling along would not be a valid test. Only operations that use up all the memory would trigger a swap, and if there is no swap available the machine would crash.

    Can you think of something simple I could do to stress the system?

    But before doing this I would disable swap with the swapoff command and run it a while to be sure you can go without swap.

    I'm guessing I have to run this from the Debian command line. I'll give it a try. Will just having the system idle be enough of a test. I haven't set anything up on OMV yet, other than the basics.

    Sorry I've mis-explained. The backplane is for some SATA 2.5 inch SSD drives. Those 2 caddies are currently removed from the system. The backplane is connected to the SAS card, which is in IT mode already. The server's onboard raid controller is disabled in the BIOS. Also the SD Card reader isn't connected to the backplane, it's a card-slot soldered directly to the motherboard. Does that make sense?
    I will try physically removing the add-on SAS card to see if that helps. I'm not sure if there is a way to further disable the onboard RAID controller. It's currently not connected to anything, disabled in the BIOS, and the cache card is removed.

    You disable and delete the swap partition after the install and optionally grow the primary partition to fill the disk.

    How do you do that?

    Sorry I knew it was one or the other but @gderf is right you wouldn't need a swap.

    Is there another command I can try? Both grub-update and update-grub gave the error. I'd still prefer to use the 256GB card I bought. Don't have much other use for it.

    Best guess it's still attempting to boot from the hw raid hence the error, depending on the machine in the bios you can set the raid option to sata, ide legacy, ahci depends on the bios, but some require the raid to be flashed to IT mode this 'turns into' a sata controller.
    When you say your not using it I take you're still using the 'caddies' if so it's running off a backplane, that all the drives plug into that backplane then has a single connection to the m'board. This is typical of HP and Dell machines

    Sorry I should have said I've disabled the on-board raid controller. AFAIK, there isn't an IT mode available for that controller, the P410i. I bought a PCI-E add-on card that supports IT mode. But it's giving issues acting as the boot device, so that's what lead me down the path of trying to use the motherboard's SD slot.
    That's correct. It's an HP server. I run a SAS cable from the backplane port to the SAS add-on card. And I have an external SAS enclosure I'm going to use for a SnapRAID array that's going to be the main storage pool.

    The weird thing here is that the 32GB SD card works fine, and anything larger that I've tried (64GB or higher) gives the attempt to read or write error. So weird that it's size dependant.

    On my previous install I noticed OMV was storing certain things on the boot partition. I moved Docker images to another physical volume, but assumed there would be other things I couldn't move that would accumulate over time. The system has 24GB of RAM, so a 32GB card was the smallest I could get to work initially. Smaller cards didn't leave enough space for the Linux Swap partition. Apparently that is always the same size as the system RAM.

    Tried typing grub-update at the grub rescue> prompt and got the error Unknown command 'grub-update'.
    Elsewhere I saw that people use the syntax update-grub but that gave the same error.

    Oh that's interesting. This system does have onboard HW RAID, but I'm not using it. Also I thought it was only for the SAS connected drives. Maybe the SD Card is managed as part of the same system?

    For some reason I can't install to 64, 128, or 256GB SD Cards, but when I tried to use a 32GB card it worked fine.
    With the larger cards, the install goes fine, but on boot I get the error:


    Attempting Boot From USB DriveKey (C:)
    error: attempt to read or write outside of disk 'hd0'

    Entering rescue mode...
    grub rescue>

    I tried the guide, but I get an error every time when I get to the "ls /boot" command.
    I also tried with a USB to SD Card adapter and got the same error as above.

    Any ideas? Is there a known limitation with the size of SD card used in OMV or Debian?

    Thanks for the reply @gderf.
    Ahh ok interesting. I saw you ask a similar question in the other thread about docker base path. I'm not sure what it means. How do I check?
    Ideally the base path would be on my array where I have the most free space.

    I wonder, do you also have unionFS installed? I think the error with 'quataon' started after I installed that plugin.

    I changed my 'Docker Base Path' to a shared folder on a UnionFS mount. As soon as I hit save I got an error message and the docker service failed. After a restart the docker service is still down.

    Here's the error:

    Any ideas how to fix this?

    On a side note, is anyone else having a lot of stability/reliability issues with OMV? This is my 4th install of it in as many weeks trying to get it to work without error, and I still have a lingering quota service failure, and unfortunately now Docker is broken.

    Hi guys,
    I keep getting these alerts, 4 so far. I can log-in to the OMV GUI no problem, so not sure what is going on.

    I should note that I have no WAN ports open on my network firewall to this server.

    Any ideas?

    Hi guys,
    I've got a lingering issue with the quotaon.service being in a failed state.

    I've tried to run service quotaon restart but it gave me this error


    Job for quotaon.service failed because the control process exited with error code.

    See "systemctl status quotaon.service" and "journalctl -xe" for details.

    Running systemctl status quotaon.service gives me

    Also, found this thread which seemed to be a similar issue. And followed this suggestion error "Failed start file system quotas" at boot
    But when I tried to create a quota for a user on one of the logical drives I got this error in the web gui.

    Ran sed -i 's/enp1s0/enp2s0/g' /etc/network/interfaces which I think worked.

    Then ran /etc/init.d/networking restart but it gave me the following error.


    [....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code.
    See "systemctl status networking.service" and "journalctl -xe" for details.

    Carried on with omv-firstaid after the error. I selected option 1 (Configure network interface) on the omv-firstaid menu list. Noticed that the interface name had updated. Yes to config IPv4, Yes to DHCPv4, No to IPv6, Yes to WOL.
    Quick restart and the GUI came right up after a few moments!

    Thanks guys!

    Ok, did you put in or remove pcie devices?

    Yes! A pcie video card, and a pcie sound card.
    I did add some new hard drives, but other than that I didn't add or change anything else.

    Ah, that is interesting. I don't understand why that's the behaviour. It seems like it would cause a lot of needless issues. And yes, it's an ASUS consumer mainboard from a number of years ago.

    Under System > Network > Interfaces, I can see enp2s0 listed, but I can't edit it.
    Under Add, I can start the creation process for a new ethernet device, and enp1s0 is listed, but when I click save, I get the following error.

    Thanks for following up. This has been really helpful.
    Yeah I hope that "Existing Path, Most Free Space" works as you've said. Worst case, in an SnapRAID array with "Most Free Space" I should be covered.

    Yeah I was running a FlexRAID array with around 12 x 1TB drives. Bit-rot was an ongoing problem. With backups it wasn't a fatal issue, but it was an ongoing annoyance and lots of work to maintain. I plan on eventually building this array one up to RAID 6. With SnapRAID being able to add disks with data on them, and the ability to expand the array made it the only choice for me.