jakethecatuk

Hi To maximise space, be great to have official support for block based de-duplication. I recognise that this may break the raid array, but restricting it to blocks on the same volume should make it a workable solution.

Managed to work this one out. In /boot/config/docker.cfg, I added the line DOCKER_OPTS="--bip=172.31.0.1/16" This will force docker to use the IP address and range specified for the network bridge.

Got a problem with Docker configuration that I'm struggling to resolve and it's to do with the default subnet Docker chooses to use. My home LAN is 172.18.0.0 and I have a remote LAN on 172.17.0.0 connected via VPN. When I start my unRaid server and Docker on my home LAN, the Docker0 interface sets itself an IP address of 172.17.0.1. root@Tower:/usr/bin# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:e4:5b:b4:da txqueuelen 0 (Ethernet) eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 172.18.2.10 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::2fd:45ff:fefc:ef99 prefixlen 64 scopeid 0x20<link> ether 00:fd:45:fc:ef:99 txqueuelen 1000 (Ethernet) root@Tower:/usr/bin# ip addr show 11: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 00:fd:45:fc:ef:99 brd ff:ff:ff:ff:ff:ff inet 172.18.2.10/24 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::2fd:45ff:fefc:ef99/64 scope link valid_lft forever preferred_lft forever 23: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:e4:5b:b4:da brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 scope global docker0 valid_lft forever preferred_lft forever This causes problems when I try to connect to my unRaid server from my remote LAN (172.17.0.0) as unRaid sees 172.17.0.0 as local in Docker and does not return any data. I've trawled around on how to resolve this and drawing a blank when it comes to Docker on unRaid. Any suggestions welcome.

Hi Here are the log file entries: - Jan 1 15:21:50 Tower unassigned.devices: Mount SMB share 'mount point' using SMB1 protocol. Jan 1 15:21:50 Tower kernel: Status code returned 0xc000000d NT_STATUS_INVALID_PARAMETER Jan 1 15:21:50 Tower kernel: CIFS VFS: Send error in SessSetup = -22 Jan 1 15:21:50 Tower kernel: CIFS VFS: cifs_mount failed w/return code = -22 Jan 1 15:21:50 Tower unassigned.devices: Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,sec=ntlmv2,vers=1.0,username=*******,password=******* 'mount point' '/mnt/disks/mount_point' Jan 1 15:21:50 Tower unassigned.devices: Mount of 'mount point' failed. Error message: mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) Looks like sec=ntlmv2 isn't supported by the version of CIFS that is installed in unraid.

Hi Sent you a PM with the diagnostic files as requested. Let me know if you need any more info

Will change it back tomorrow and reboot to capture the diagnostics you need and post them.

Hi I could - but not sure what value it would have. As I have rebooted my server after making the change I highlighted above, the log files do not include any error information as the mount now works as expected.

Hi Dlandon Been looking at Unassigned Devices and found an anomaly, undocumented feature, bug, incompatibility issue I'm trying to map to an SMB share running on a Windows 2016 Server and every time I try to connect from Unassigned Devices, I get error(13): - Dec 31 19:00:58 Tower unassigned.devices: Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,vers=3.0,username=*******,password=******* 'mount point' '/mnt/disks/mount_point' Dec 31 19:00:58 Tower unassigned.devices: Mount of 'mount point' failed. Error message: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I know that my SMB shares work as I have other LINUX servers that are able to connect to without any issues. I looked at your code in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php and modified line 569 to include security settings: - 569: return "rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,sec=ntlm,vers=%s,username=%s,password=%s"; This minor change worked for me - not sure whether it's something to include going forward.