Posts by guyp2k

    Given the official reply from ryecoaaron and VB from a plugin perspective I was hopeful that the plugin would be ported over to OMV5. I have been using Cockpit and one issue/challenge I can't address is creating a bridge network from the Cockpit web interface and I read where it is not recommended not to install NetworkManager. I am having an issue where I need the guest to communicate w/ the host that OMV and Cockpit reside. I can communicate w/ all other hosts on the network w/ the exception of the OMV/Cockpit host and I would assume creating a bridge network interface via Cockpit would address the issues, any suggestions?


    Thanks

    I have done both but most are virtual disks because I have a proxmox cluster and you can't migrate a VM to different host if you are using passthrough.

    No. I have an Ubuntu 18 server VM just for dockers.

    I spun up proxmox on a spare box and curious how you present the volumes to docker i.e., plex, did you just add a volume via NFS (source OMV running as a VM in proxmox) in portainer and add the NFS volume to each container as needed, or is there another prefered method?


    Thanks

    Mine is as well but I still run OMV as a VM on proxmox.

    Thinking about going this route as well, just curious how you present the disks to OMV, from proxmox or passthrough? Lastly, do you run Docker from the OMV VM as well?


    Thanks

    Before I start making permission changes thought I would post here. Having an issue when setting the web GUI auto logout and when looking at the logs I see the following:


    /var/log/nginx# tail -1 openmediavault-webgui_error.log
    2019/11/24 09:02:49 [error] 1620#1620: *647 FastCGI sent in stderr: "PHP message: PHP Warning: DOMDocument::load(/etc/openmediavault/config.xml): failed to open stream: Permission denied in /usr/share/php/openmediavault/config/databasebackend.inc on line 112PHP message: PHP Warning: DOMDocument::load(/etc/openmediavault/config.xml): failed to open stream: Permission denied in /usr/share/php/openmediavault/config/databasebackend.inc on line 112" while reading response header from upstream, client: ::ffff:192.168.1.52, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "192.168.1.25:8181", referrer: "http://192.168.1.25:8181/"


    I have done the following:


    chown root:openmediavault-config /etc/openmediavault/config.xml
    chmod 660 /etc/openmediavault/config.xml


    Any suggestions?


    Thanks

    Resolved: I actually had a path in one of my containers pointing to /sharedfolders. Thought I had addressed, but I overlooked that one path.


    I am using the the following path for Docker:


    /srv/dev-disk-by-label-appdata/Docker, Docker Storage under OMV Extras. All the containers I have setup are /srv/dev-disk....


    Looking through fstab, it's /srv/disk..., sorry if I am missing something obvious here.


    Thanks

    Update: Disabled Docker and was able to do what I needed to w/ the disks and shares. Any idea where the conflict is occurring w/ Docker enabled?


    fstab:


    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    # / was on /dev/nvme0n1p2 during installation
    UUID=8ec2e3d1-c0e7-408d-935d-1acfd5fbf32c/ ext4 noatime,nodiratime,discard,errors=remount-ro 0 1
    # /boot/efi was on /dev/nvme0n1p1 during installation
    UUID=B6C2-56B6 /boot/efi vfat umask=0077 0 1
    # swap was on /dev/nvme0n1p3 during installation
    #UUID=256d12ad-ea30-4d48-bcaa-f01067add235 none swap sw 0 0
    /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
    # >>> [openmediavault]
    /dev/disk/by-label/parity/srv/dev-disk-by-label-parity ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data1/srv/dev-disk-by-label-data1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data2/srv/dev-disk-by-label-data2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data3/srv/dev-disk-by-label-data3 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data5/srv/dev-disk-by-label-data5 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/appdata/srv/dev-disk-by-label-appdata ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
    /dev/disk/by-label/data4/srv/dev-disk-by-label-data4 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data7/srv/dev-disk-by-label-data7 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/data6/srv/dev-disk-by-label-data6 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-label/spareSSD/srv/dev-disk-by-label-spareSSD ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
    /srv/dev-disk-by-label-data1:/srv/dev-disk-by-label-data2:/srv/dev-disk-by-label-data3:/srv/dev-disk-by-label-data4:/srv/dev-disk-by-label-data5:/srv/dev-disk-by-label-data6:/srv/dev-disk-by-label-data7/srv/c0ece4ff-b7be-4b9a-963d-4ea4ac6ac95a fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=mfs,minfreespace=10G 0 0
    # <<< [openmediavault]


    Any ideas?

    Thanks for the reply and I missed a step earlier when I created the routing table. last question OMV echoes back not to edit /etc/networks, rather /etc/systemd/network for the last piece to make the routing tables static on a reboot.


    Below are the interfaces:


    10-openmediavault-enp1s0f0.link
    -rw-r--r-- 1 root root 184 Nov 10 19:41 10-openmediavault-enp1s0f0.network
    -rw-r--r-- 1 root root 123 Nov 10 19:41 10-openmediavault-enp3s0f0.link
    -rw-r--r-- 1 root root 160 Nov 10 19:41 10-openmediavault-enp3s0f0.network
    -rw-r--r-- 1 root root 45 Nov 2 23:12 openmediavault-enp1s0f0.link
    -rw-r--r-- 1 root root 191 Nov 2 23:12 openmediavault-enp1s0f0.network
    root@openmediavault:/etc/systemd/network#


    I assume I would need to edit enp3s0f0.network and add the additional:


    iface enp3s0f0 inet static
    address 192.168.4.2
    netmask 255.255.255.0
    post-up ip route add 192.168.4.0/24 dev enp3s0f0 src 192.168.4.2 table rt2
    post-up ip route add default via 192.168.4.1 dev enp3s0f0 table rt2
    post-up ip rule add from 192.168.4.2/32 table rt2
    post-up ip rule add to 192.168.4.2/32 table rt2


    Thanks

    Currently I have 2 physical interfaces configured in OMV:


    1. enp1s0f0 - 192.168.1.25/24 GW: 192.168.1.1
    2. enp3s0f0 - 192.168.4.2/24 GW: 192.168.4.1


    I can ping both IPs and both GWs sourcing from 192.168.1.0/24 network.


    My issue is I created a MACVLAN in Docker for both the .1 and .4 network. The .1 MACVLAN works just fine however when I assign any container to .4 MACVLAN I can't communicate with the container on the .4 MACVLAN.


    The .4 MACVLAN is configured as follows:


    192.168.4.2/24 GW: 192.168.4.1
    Interface: enp3s0f0


    Container is assigned .4 MACVLAN with an IP of 192.168.4.3.


    IP Route:
    default via 192.168.4.1 dev enp3s0f0 proto static
    default via 192.168.1.1 dev enp1s0f0 proto static
    default via 192.168.1.1 dev enp1s0f0 proto dhcp metric 100
    172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
    172.18.0.0/16 dev br-964b0b53880c proto kernel scope link src 172.18.0.1 linkdown
    172.19.0.0/16 dev docker_gwbridge proto kernel scope link src 172.19.0.1
    172.20.0.0/16 dev br-9c082571355b proto kernel scope link src 172.20.0.1 linkdown
    172.21.0.0/16 dev br-f60823117701 proto kernel scope link src 172.21.0.1 linkdown
    172.22.0.0/16 dev br-34de0811e6f4 proto kernel scope link src 172.22.0.1 linkdown
    172.23.0.0/16 dev br-b2bf044c0577 proto kernel scope link src 172.23.0.1 linkdown
    172.24.0.0/16 dev br-78ef2ff541c7 proto kernel scope link src 172.24.0.1 linkdown
    172.25.0.0/16 dev br-37cdf41da664 proto kernel scope link src 172.25.0.1 linkdown
    192.168.1.0/24 dev enp1s0f0 proto kernel scope link src 192.168.1.25
    192.168.1.0/24 dev enp1s0f0 proto kernel scope link src 192.168.1.83 metric 100
    192.168.1.0/24 dev enp1s0f0 proto kernel scope link src 192.168.1.25 metric 100
    192.168.4.0/24 dev enp3s0f0 proto kernel scope link src 192.168.4.2
    192.168.4.0/24 dev mac0 proto kernel scope link src 192.168.4.2
    192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown


    Any idea what I am missing here?


    Thanks

    Currently I have a an OMV5 install with the following at high-level:
    1. SNAPRAID
    2. Multiple shares.
    3. UnionFS
    4. Dokcer on separate SSD.
    5. All drives attached to LSI HBA adapter.



    I have read a few threads and would like to confirm/validate as I swap out CPU and MB.
    1. Unplug data and Docker drives.
    2. New install of OMV5.
    3. Shutdown, plug in drives and reboot.
    4. Add drives back and mount.
    5. Create SNAPRAID and UnionFS.
    Drives will be named the same and added as before.
    6. Install Docker point to same path as before.
    7. Re-create shares.
    8. Reboot.


    Should the above work or should I just start over and migrate my data from other NAS and reconfigure Docker and containers?


    Thanks

    Last question, I am using snapraid and unionfs and have the following:


    9281424326658 4 drwxr-xr-x 9 root root 4096 Nov 3 10:09 7b9a5991-098e-4993-a5e3-b9db0fc5699e
    2752551 4 drwxrwxrwx 2 root root 4096 Oct 31 16:23 dev-disk-by-label-Docker
    2752555 4 drwxrwxrwx 2 root root 4096 Nov 3 07:42 dev-disk-by-label-Test
    2 4 drwxr-xr-x 4 root root 4096 Nov 3 08:53 dev-disk-by-label-appdata
    2 4 drwxr-xr-x 5 root root 4096 Nov 3 00:59 dev-disk-by-label-data1
    2 4 drwxr-xr-x 7 root root 4096 Nov 3 00:59 dev-disk-by-label-data2
    2 4 drwxr-xr-x 5 root root 4096 Nov 3 00:59 dev-disk-by-label-data3
    2 4 drwxr-xr-x 7 root root 4096 Nov 3 00:59 dev-disk-by-label-data4
    2 4 drwxr-xr-x 9 root root 4096 Nov 3 00:59 dev-disk-by-label-data5
    2 4 drwxr-xr-x 8 root root 4096 Nov 3 00:59 dev-disk-by-label-data6
    2 4 drwxr-xr-x 9 root root 4096 Nov 3 10:09 dev-disk-by-label-data7
    2 4 drwxr-xr-x 3 root root 4096 Nov 3 00:59 dev-disk-by-label-parity
    2752514 4 drwxr-xr-x 2 ftp nogroup 4096 Oct 30 21:07 ftp
    2752516 4 drwxr-xr-x 3 root root 4096 Nov 2 14:49 pillar
    2752523 4 drwxr-xr-x 5 root root 4096 Nov 2 14:49 salt


    I assume the path would be /srv/7b9a5991-098e-4993-a5e3-b9db0fc5699e/shareX? Given that is the unionFS...

    Then I have no idea what it could be... In my case, the folders I was adding had nothing to do with Docker or my Containers folder... but when I'd get the error, it always referenced my Containers folder.... this made me think to just disable all of my Docker containers an then try to add the share, and it worked perfectly.. restart Docker containers, problem repeats.


    Once I remapped my Docker container paths, I've not had the problem since.


    Since you're not running Docker, it would appear there is some sort of problem with how the webUI is accessing the shortcuts under /sharedfolders.. I've not saw any other posts on it though, so whatever it is must be a fairly unique set of circumstances, but I'm not really doing anything exotic on my NAS.

    I am having a similar problem, running OMV 5.0.12-1 and Docker. If I disable Docker I can add the share. Did you just remap to the same sharedfolders for your containers? On some of my containers I am binding volumes to /sharedfolders/xxxxx.


    Thanks

    no spaces and no special characters. Formatted as ext4 and label is appdata. The drive is a 500GB SSD I want to use for Docker. OMV sees the drive and I am able to wipe and create a file-system, just can't mount or any other drive for that matter.


    Update;


    Seemed to addressed the issue, I had to edit /etc/fstab and /etc/openmediavault/config.xml. There were non-used drives in config.xml I deleted and same in fstab. Once I cleaned up those 2 files and rebooted, I was able to create the FS, mount, and create shares.


    Thanks

    Same issue:


    Running 5.0.12-1 and I attempted to add an additional drive/SSD. I have
    wiped and created a file system, but when I try and mount the disk I
    receive the following error:



    Failed to execute command 'export
    PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin;
    export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit
    code '1': debian:---------- ID:
    create_filesystem_mountpoint_96b4a306-6e39-45ab-bd0c-7521ef20f45a
    Function: file.accumulated Result: True Comment: Accumulator...



    Any suggestions?



    Thanks

    Running 5.0.12-1 and I attempted to add an additional drive/SSD. I have wiped and created a file system, but when I try and mount the disk I receive the following error:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': debian:---------- ID: create_filesystem_mountpoint_96b4a306-6e39-45ab-bd0c-7521ef20f45a Function: file.accumulated Result: True Comment: Accumulator...


    Any suggestions?


    Thanks

    I tried to create a new share and when I apply I receive the following error:


    Any ideas?


    The configuration has been changed. You must apply the changes in order for them to take eff



    The configuration has been changed. You must apply the changes in order for them to take effect.
    Displaying items 1 - 6 of 6
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run systemd 2>&1' with exit code '1': debian:---------- ID: remove_sharedfolder_mount_unit_files Function: module.run Result: True Comment: file.find: ['/etc/systemd/system/sharedfolders-Backup.mount', '/etc/systemd/system/sharedfolders-Docker.mount', '/etc/systemd/system/sharedfolders-Documents.mount', '/etc/systemd/system/sharedfolders-Media.mount', '/etc/systemd/system/sharedfolders-MusicKODI.mount', '/etc/systemd/system/sharedfolders-Test.mount'] Started: 17:20:57.098325 Duration: 2.323 ms Changes: ---------- file.find: - /etc/systemd/system/sharedfolders-Backup.mount - /etc/systemd/system/sharedfolders-Docker.mount - /etc/systemd/system/sharedfolders-Documents.mount - /etc/systemd/system/sharedfolders-Media.mount - /etc/systemd/system/sharedfolders-MusicKODI.mount - /etc/systemd/system/sharedfolders-Test.mount---------- ID: configure_sharedfolder_Media_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-Media.mount Result: True Comment: File /etc/systemd/system/sharedfolders-Media.mount updated Started: 17:20:57.102042 Duration: 2.147 ms Changes: ---------- diff: New file mode: 0644---------- ID: configure_sharedfolder_MusicKODI_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-MusicKODI.mount Result: True Comment: File /etc/systemd/system/sharedfolders-MusicKODI.mount updated Started: 17:20:57.104273 Duration: 1.543 ms Changes: ---------- diff: New file mode: 0644---------- ID: configure_sharedfolder_Backup_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-Backup.mount Result: True Comment: File /etc/systemd/system/sharedfolders-Backup.mount updated Started: 17:20:57.105888 Duration: 1.538 ms Changes: ---------- diff: New file mode: 0644---------- ID: configure_sharedfolder_Documents_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-Documents.mount Result: True Comment: File /etc/systemd/system/sharedfolders-Documents.mount updated Started: 17:20:57.107495 Duration: 1.513 ms Changes: ---------- diff: New file mode: 0644---------- ID: configure_sharedfolder_Docker_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-Docker.mount Result: True Comment: File /etc/systemd/system/sharedfolders-Docker.mount updated Started: 17:20:57.109087 Duration: 1.494 ms Changes: ---------- diff: New file mode: 0644---------- ID: configure_sharedfolder_Test_mount_unit_file Function: file.managed Name: /etc/systemd/system/sharedfolders-Test.mount Result: True Comment: File /etc/systemd/system/sharedfolders-Test.mount updated Started: 17:20:57.110649 Duration: 1.566 ms Changes: ---------- diff: New file mode: 0644---------- ID: sharedfolder_mount_units_systemctl_daemon_reload Function: module.run Name: service.systemctl_reload Result: True Comment: Started: 17:20:57.112286 Duration: 0.217 ms Changes:---------- ID: enable_sharedfolder_Media_mount_unit Function: service.enabled Name: sharedfolders-Media.mount Result: True Comment: Service sharedfolders-Media.mount is already enabled, and is in the desired state Started: 17:20:57.568850 Duration: 293.6 ms Changes:---------- ID: restart_sharedfolder_Media_mount_unit Function: module.run Result: True Comment: service.restart: True Started: 17:20:57.862701 Duration: 45.104 ms Changes: ---------- service.restart: True---------- ID: enable_sharedfolder_MusicKODI_mount_unit Function: service.enabled Name: sharedfolders-MusicKODI.mount Result: True Comment: Service sharedfolders-MusicKODI.mount is already enabled, and is in the desired state Started: 17:20:57.908099 Duration: 17.947 ms Changes:---------- ID: restart_sharedfolder_MusicKODI_mount_unit Function: module.run Result: True Comment: service.restart: True Started: 17:20:57.926300 Duration: 38.208 ms Changes: ---------- service.restart: True---------- ID: enable_sharedfolder_Backup_mount_unit Function: service.enabled Name: sharedfolders-Backup.mount Result: True Comment: Service sharedfolders-Backup.mount is already enabled, and is in the desired state Started: 17:20:57.964770 Duration: 14.454 ms Changes:---------- ID: restart_sharedfolder_Backup_mount_unit Function: module.run Result: True Comment: service.restart: True Started: 17:20:57.979443 Duration: 34.761 ms Changes: ---------- service.restart: True---------- ID: enable_sharedfolder_Documents_mount_unit Function: service.enabled /salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import Iterable, Mapping/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function)/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function)/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function)