Posts by timekills

  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote from chente

    This is so in that document because the proposed procedure is to install the docker folder on a separate drive from the operating system. The reasons are explained in the document a little earlier.

    If you want to keep the default path /var/lib/docker you don't need to reinstall docker.

    It all depends on what you want to configure and how you want to do it.

    Yes...that's why I was letting Vitaman know how to set the Docker folder.

    That user asked how to set the Docker folder as directed in OMV Docker guide.

    ( RE: omv-extras 6.3 / openmediavault-compose 6.7 )


    As you recall, we used to do that before installing the OMV-compose plugin to ensure Docker would use the specified folder.

    Now we do it after installing the plugin...but before actually installing Docker.


    Of course, the new instructions show that screenshot and the steps to do this, but I didn't want to just RTFM my response.

    You guys are pretty patient. Appreciate it.

  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote from Vitaman

    Sorry but how do I set the drive where docker is supposed to be loaded to if I can't see it? The wiki guide says it will not go to the correct place if it is not set there.

    Once you install the Docker repo, and then the OMV-Compose plugin you will have to actually install Docker from the Services-> Compose section.


    In there, Under "Settings" you set both the Compose folder and the Docker install folder. Save, then Install Docker.

  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote from ryecoaaron

    Your package cache is old since I just release 6.7.5. Click the apt clean button in omv-extras.

    FWIW, the "issue" with the Save button being grayed-out by default remains even after the apt-clean and GUI refresh. Even tried a restart just to check.

    Not a big deal, but you do have to de-select the yellow button for "Docker repo" and re-select before Save is accessible.

    Perhaps not having the Docker repo check-box pre-selected?


    Or just one line on the instructions page telling people to de-select the button first:

  • omv-extras 6.3 / openmediavault-compose 6.7

    Edit - found solution.*

    First - I appreciate both the thread and the amount of time taken to recreate the plug-ing, the capability, and answer all the panicked users.

    Bottom line up front:

    Problem: the new instructions at https://wiki.omv-extras.org/do…cker_compose#installation state to first install the Docker Repo from the omv-extras before the Compose plugin. Somewhat similar to before.

    --However, you can't click the "Save" button until AFTER you install the OMV-compose.

    Wrong. However - *you can't click the "Save" button until after you deselect the yellow check-box for Docker repo and the re-select the yellow check box.


    Once you install the Docker repo, the OMV-compose URL is accessible.


    --Further however... the OMV-compose relies on Docker installation to work

    ---Further however... the above is an assumption as I get the big red error box upon trying to install the OMV-compose, but the key error line is not that Docker isn't installed it is this:

    Err:1 https://openmediavault-plugin-developers.github.io/packages/debian shaitan/main amd64 openmediavault-compose all 6.7.4

    404 Not Found [IP: 185.199.108.153 443]


    So I think the correct order should be :

    1. OMV-Compose (where presumably I'll be able to choose the Docker install location...?)

    2. Docker repo

    But until the URL https://openmediavault-plugin-…github.io/packages/debian works, not sure we can do anything.

  • create raid 1 on a blank disk, copy from a drive and grow the raid

    Quote from macom

    Where did you get the idea that the speed of reading or writing is better for RAID1 than for a single drive?


    And what do you mean with "the backup should be scheduled"?

    Not to derail this discussion (which of course means this could derail this discussion) ...


    Regarding increased read speed from a RAID 1 array...it depends on the device/software of course, and also on how the data is accessed.

    However mdadm used in OMV can increase read speeds, if/when multiple files are accessed simultaneously, at least according to the RAID1 section of the md manpage:

    Quote
    Note that the read balancing done by the driver does not make the RAID1 performance profile be the same as for RAID0; a single stream of sequential input will not be accelerated (e.g. a single dd), but multiple sequential streams or a random workload will use more than one spindle. In theory, having an N-disk RAID1 will allow N sequential threads to read from all disks.

  • SMART with external USB drives

    There is a way to get quirky (their term, not mine) USB devices to respond to SMART monitoring.

    This most typically affects Seagate external/USB devices as the USB to SATA bidge they employ is a new-ish one that translates as a SCSI device not able to be fully monitored in current kernels.

    The downside is you lose some advanced caching capability...note that I have not seen any real world impact on two (2) x 14TB external drives with this.

    As always...YMMV.


    1: SSH into your OMV device (as root or using sudo later)

    2: type lsblk to confirm the dev/sdx device location

    3: type smartctl --health /dev/sdx using the device you want to get the error code from.

    --You wil see an error similar to /dev/sdd: Unknown USB bridge [0x0951:0x1666 (0x110)]

    4. the important part are the 8 digits with a :(colon) in the middle not including "0x"; i.e. in the above portion the 0951:1666

    5. Edit the /etc/modprobe.d/usb-storage-quirks.conf file to tell Debian/OMV to exclude that device from some checks it performs which end up blocking SMART

    --- easiest way is to type echo "options usb-storage quirks=xxxx:xxxx:u" >> /etc/modprobe.d/usb-storage-quirks.conf

    --Obviously replace the xxxx:xxxx with the code for YOUR device. using the ample above it would be echo "options usb-storage quirks=0951:1666:u" >> /etc/modprobe.d/usb-storage-quirks.conf

    6. Update your root filesystem update-initramfs -u


    You will have to reboot before this takes effect.


    Note: If you want to add multiple devices to usb-storage-quirks.conf, it is done all on the one line, separated by comma. NOT MULTIPLE LINES.

    I.E. options usb-storage quirks=0bc2:3322:u,0951:1666:u


    This also occurs with some newer USB thum drives. You may be able to "solve" it the same way, but I've been less successful so far.


    **Thanks to tkaiser and this thread How to get SMART on external drives

  • Can't execute from shared folders

    This does work.

    Recommend creating a group however, and setting the group owner to that group and giving that group RWX permissions.

    Then you can add users to that group that get those privilges.

    Obviously only really necessary if you have more than one user to the share...but even if there's only one user it doesn't hurt to be prepared to give (or remove) those privileges en masse rather than just to a single user.