Posts by openletter

    No. I pull a drive out of a different computer, plug it into an eSATA dock. From there, it wold be nice to even have something similar to USB Backup to automagically save the image, or however it would work.

    dd on the command line isn’t that hard. Are you making backups on a Windoze or a Mac? Why does it need to be GUI?

    A NAS on the command line isn't that hard. :P


    I just don't want to deal with ssh into the box every time. easier to just click and go, plus without worrying I'm disk destroying something.

    I've been searching solutions regarding the nut UPS plugin for OMV, but the search function requires 4 or more characters, so there is no way to use ups or nut as search terms.


    I also can't find a way to search tags or view all tags.


    If there is an option in the forum configuration to change this, that would be great.

    I have a Linux Mint computer that only transfers ~400 mbps both up and down, while Windows 7 computers transfer at >990 mbps.


    Is there something different about a Linux computer that I should change to get full transfer speeds? I actually get ~440 mpbs download from the Internet, so my Internet is faster than local file transfer, <sigh>.

    Okay, I figured out a fix.


    I noticed one of the ttyS* ports was member of group nut:


    # ls -alF /dev/ttyS*
    crw-rw---- 1 root nut 4, 64 Apr 8 15:38 ttyS0
    crw-rw---- 1 root dialout 4, 65 Apr 8 15:38 ttyS1
    crw-rw---- 1 root dialout 4, 66 Apr 8 15:38 ttyS2
    crw-rw---- 1 root dialout 4, 67 Apr 8 15:38 ttyS3


    I chowned ttyS2 to root:nut, and now everything works.


    The first time I loaded the configuration I copy pasted my old one, which was ttyS0, then later figured out it was ttyS2. I wonder if nut changed the group of ttyS0 on the first configuration load, but not later configurations?

    The interface seems largely unchanged since OMV 2.x.


    The configuration is from the 'Driver configuration directives' field in the interface.


    The rest of the options shouldn't have any bearing on the posted directives, which I have used for a very, very long time. The last time I redid my NUT config was in 2015, and haven't touched it since.


    My BIOS has only two options for the serial port: enable/disable and IRQ address.


    From command line:
    # dmesg | grep tty
    [ 0.000000] console [tty0] enabled
    [ 1.011463] 00:05: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A


    The following configuration is saved for the UPS (same as I used on 2.x and earlier):



    When I attempt to enable the UPS plugin and Apply the configuration, I get the following error dialog:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'nut-driver' 2>&1' with exit code '1': Job for nut-driver.service failed because the control process exited with error code.See "systemctl status nut-driver.service" and "journalctl -xe" for details.


    When I select 'View details' from GUI:


    systemctl status nut-driver.service:


    journalctl -xe produces a huge output. I *think* this is the relevant bits:



    What am I missing in my configuration?