hendry Posted February 21, 2022 Share #101 Posted February 21, 2022 (edited) 9 hours ago, uxora-com said: The answer is on my last post about that: yes, i can ping the ip address of container from my laptop. i run docker exec -it containername /bin/bash, running ipconfig i see eth0 is getting same ip that i put on the docker run parameter. but i cannot go into synology web ui.. dockerbridge: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 20.20.20.1 netmask 255.255.255.0 broadcast 20.20.20.255 ether 66:4f:06:f4:03:26 txqueuelen 1000 (Ethernet) RX packets 126 bytes 24414 (23.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 960 (960.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.3 netmask 255.255.255.0 broadcast 192.168.10.255 ether 02:42:c0:a8:0a:03 txqueuelen 0 (Ethernet) RX packets 322 bytes 96417 (94.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 380 (380.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0 is getting correct ip from my router subnet. 192.168.10.3 can be access but it's not xpenology, it's debian.. what is missing ? Edited February 21, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
hendry Posted February 21, 2022 Share #102 Posted February 21, 2022 On 2/20/2022 at 3:28 AM, uxora-com said: No, I never get this issue ... maybe this is something to do with trying to 9p fs mountpoint /xpy_syst folder. (I should remove this in my README example). You can try to different VM_9P_OPTS and mount option to see if ACL works with xpenology. Maybe you want your xpenology to be more expose by setting it its own fixed IP. You can do it by creating a macvlan then add "--network MyMacvlanName --ip=192.168.x.x" (then i wont need -p option no more) Check this : https://docs.docker.com/network/network-tutorial-macvlan/ HTH, what VM_9P_OPTS which has ACL permission setting? Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 21, 2022 Share #103 Posted February 21, 2022 (edited) 11 hours ago, hendry said: 192.168.10.3 can be access but it's not xpenology, it's debian.. what is missing ? If you can ping it, then it should work as long as you use the right port to access it and this is not block by any firewall! (sometimes I'm not sure you even tried to find a solution before posting ... and again, as i said in my last post, you don't need port mapping option "-p" no more ... and you should find your solution.) Well, what you need to know is that I already made it working ... and this is already a big thing to know ... so it should work for u as well normally! 50 minutes ago, hendry said: what VM_9P_OPTS which has ACL permission setting? 9p seems to have posix acl abilities ... but i don't know if modules has been compile with this option and even if it does, I not sure it will still works with dsm ACL. You need to try and test and if it succeed to make it working let us know. Otherwise you have other fs option like SMB/CIFS or NFS. HTH, Edited February 21, 2022 by uxora-com Quote Link to comment Share on other sites More sharing options...
hendry Posted February 22, 2022 Share #104 Posted February 22, 2022 (edited) 20 hours ago, uxora-com said: If you can ping it, then it should work as long as you use the right port to access it and this is not block by any firewall! (sometimes I'm not sure you even tried to find a solution before posting ... and again, as i said in my last post, you don't need port mapping option "-p" no more ... and you should find your solution.) Well, what you need to know is that I already made it working ... and this is already a big thing to know ... so it should work for u as well normally! 9p seems to have posix acl abilities ... but i don't know if modules has been compile with this option and even if it does, I not sure it will still works with dsm ACL. You need to try and test and if it succeed to make it working let us know. Otherwise you have other fs option like SMB/CIFS or NFS. HTH, Please listen to me carefully.. I compare the container running without using -p options, put macvlan, and running with using -p options and bridge network this is running without using -p options & macvlan. dockerbridge: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 20.20.20.1 netmask 255.255.255.0 broadcast 20.20.20.255 ether 66:4f:06:f4:03:26 txqueuelen 1000 (Ethernet) RX packets 126 bytes 24414 (23.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 960 (960.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.3 netmask 255.255.255.0 broadcast 192.168.10.255 ether 02:42:c0:a8:0a:03 txqueuelen 0 (Ethernet) RX packets 322 bytes 96417 (94.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 380 (380.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 and this is running using -p & bridge network dockerbridge: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 20.20.20.1 netmask 255.255.255.0 broadcast 20.20.20.255 ether de:a8:6c:da:82:bd txqueuelen 1000 (Ethernet) RX packets 181 bytes 29210 (28.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 96 bytes 13214 (12.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.100.3.2 netmask 255.255.255.0 broadcast 10.100.3.255 ether 02:42:0a:64:03:02 txqueuelen 0 (Ethernet) RX packets 85 bytes 14131 (13.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 78 bytes 8496 (8.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as you can see, the eth0 from running without using -p and macvlan, eth0 has correct ip address (192.168.10.3). but it cannot goes to synology web ui.. if you say problem with my firewall, i have installed xpenology running on vmware, and i get no problem accesing synology web ui. the eth0 get ip address 10.100.3.2, it's the ip getting from host docker0 interface. lxcbr0 Link encap:Ethernet HWaddr 32:F8:58:15:90:97 inet addr:10.100.3.1 Bcast:10.100.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3702913 errors:0 dropped:0 overruns:0 frame:0 TX packets:58708689 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1025316624 (977.8 MiB) TX bytes:55022732708 (51.2 GiB) [~] # docker network inspect bridge [ { "Name": "bridge", "Id": "2f2cde56377e07a439bce2b23cacfac49109d02c174c7152b4efa57988aa11d1", "Created": "2022-02-17T16:57:51.504626029+07:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "10.100.3.0/24", "Gateway": "10.100.3.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "04f8642d34b2a4910bb7a3e9bd728529424e488f115efe7fef515b70c53b6447": { "Name": "xpenology", "EndpointID": "386a35245b2d80245eb76347ccb68405ffc4c0c511e6a8a6714acc082f73ec77", "MacAddress": "02:42:0a:64:03:02", "IPv4Address": "10.100.3.2/24", "IPv6Address": "" } }, "Options": { "com.docker.network.bridge.default_bridge": "true", "com.docker.network.bridge.enable_icc": "true", "com.docker.network.bridge.enable_ip_masquerade": "true", "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0", "com.docker.network.bridge.name": "lxcbr0", "com.docker.network.driver.mtu": "1500" }, "Labels": {} } ] hope you can give me some clue.. the ip 192.168.10.3 is the debian container host where xpenology running. weird.. why the xpenology cannot broadcast port 5000 to debian container itself ? tried to curl from docker host but also failed.. [~] # curl http://192.168.10.3:5000 curl: (7) Failed to connect to 192.168.10.3 port 5000: No route to host Edited February 22, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 22, 2022 Share #105 Posted February 22, 2022 1 hour ago, hendry said: Please listen to me carefully.. Indeed ... good luck then. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 23, 2022 Share #106 Posted February 23, 2022 12 hours ago, uxora-com said: Indeed ... good luck then. what's the use of dockerbridge which has ip address 20.20.20.1 ? how if when starting qemu, the xpenology network configuration using bridge to eth0 not to dockerbridge? sorry, i'm not so familiar with nat & firewall setting in linux. Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 26, 2022 Share #107 Posted February 26, 2022 UPDATE of xpenology-docker: - DHCP is now available (Check README for more information) - Now works without "--privileged" docker option for more security # On docker host # Create a macvlan matching your local network $ docker network create -d macvlan \ --subnet=192.168.0.0/24 \ --gateway=192.168.0.1 \ --ip-range=192.168.0.100/28 \ -o parent=eth0 \ macvlan0 # Run xpenology docker (Warning: --device-cgroup-rule number may be different for you) $ docker run --name="xpenodock" --hostname="xpenodock" \ --cap-add=NET_ADMIN --device-cgroup-rule='c 235:* rwm' \ --device=/dev/net/tun --device=/dev/kvm --device=/dev/vhost-net \ --network macvlan0 -e VM_NET_DHCP="Y" \ -e BOOTLOADER_URL="http://myurl/synoboot.tgz" \ -e RAM="512" -e DISK_SIZE="16G" \ -e GRUBCFG_SN="1234ABC012345" \ -e GRUBCFG_SATAPORTMAP="6" -e GRUBCFG_DISKIDXMAP="00" \ -e DISK_PATH="/xpy/diskvm" -e VM_9P_PATH="/xpy/share9p" \ -v /host_dir/kvm:/xpy/diskvm -v /host_dir/data:/xpy/share9p \ uxora/xpenology HTH, Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 27, 2022 Share #108 Posted February 27, 2022 UPDATE of xpenology-docker: - Instead of using BOOTLOADER_URL, you can now pass local bootloader file with: "-v /local_path/synoboot.tgz:/bootloader" - Add BOOTLOADER_FORCE_REPLACE variable to replace existing bootloader in DISK_PATH Well, let me know if something does not work. Enjoy. HTH, Quote Link to comment Share on other sites More sharing options...
hendry Posted February 28, 2022 Share #109 Posted February 28, 2022 (edited) @uxora-com i will pull your latest image and try again using your new dhcp ip dockervlan. as far as i tried, i never succeas getting macvlan works. port 5000 still not works, but i will try your new images. can u please give me the dockercompose.yaml file for configuration using dhcp macvlan? because in qnap container station, if using the docker run command, it cannot start automatic everytime the nas startup. EDIT: tried and now success getting IP Address from my router, and also i can access port 5000 DSM Web UI from that DHCP IP Address. samba also works from my local network. good job bro.. One more things, how to give permission on synology drive if i mount /volume1/homes from 9p shared folder ? I still cannot getting work if I open synology office apps from drive. it seems cannot have access on /volume1/homes folder. this is the options i use to mount using 9p, i added ACL options, but still synology drive cannot access that folder. hostdata3 on /volume1/homes type 9p (rw,relatime,dirsync,trans=virtio,version=9p2000.L,posixacl,msize=262144,cache=loose) when opening spreadsheet or documents, it has error like this.. Edited February 28, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
uxora-com Posted February 28, 2022 Share #110 Posted February 28, 2022 8 hours ago, hendry said: this is the options i use to mount using 9p, i added ACL options, but still synology drive cannot access that folder. Can you provide me your "Docker run" command line and your "9p mount" command line ... and I may give a try to see if dsm ACL works with 9p. Quote Link to comment Share on other sites More sharing options...
hendry Posted February 28, 2022 Share #111 Posted February 28, 2022 1 hour ago, uxora-com said: Can you provide me your "Docker run" command line and your "9p mount" command line ... and I may give a try to see if dsm ACL works with 9p. i run docker using docker-compose. here's the docker-compose.yml file version: '3' services: xpenology-app: container_name: xpenology image: uxora/xpenology:latest cap_add: - NET_ADMIN devices: - "/dev/net/tun:/dev/net/tun" - "/dev/kvm:/dev/kvm" - "/dev/vhost-net:/dev/vhost-net" device_cgroup_rules: - 'c 235:* rwm' environment: RAM: 1536 DISK_SIZE: "16G" DISK_PATH: "/xpy_syst" VM_9P_PATH: "/xpy_data /xpy_data1 /xpy_data2 /xpy_data3" GRUBCFG_DISKIDXMAP: "00" GRUBCFG_SATAPORTMAP: "1" VM_NET_DHCP: "Y" volumes: - /share/CACHEDEV2_DATA/MUSIC:/xpy_data - /share/CACHEDEV1_DATA/Public/XPE/syst:/xpy_syst - /share/CACHEDEV1_DATA/QVRProSpace_DataVol1:/xpy_data1 - /share/CACHEDEV2_DATA/PHOTO:/xpy_data2 - /share/CACHEDEV1_DATA/Public/XPE/data:/xpy_data3 restart: always privileged: true networks: dockervlan: ipv4_address: 192.168.10.3 networks: dockervlan: name: dockervlan driver: macvlan driver_opts: parent: qvs0 ipam: config: - subnet: "192.168.10.0/24" gateway: "192.168.10.1" and this is the mount command i put it as /usr/local/etc/rc.d/S99mount.sh file, so it will run at startup. #!/bin/sh # # This goes in /usr/local/etc/rc.d and gets run at boot-time. case "$1" in start) /bin/mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata0 /volume1/music /bin/mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata1 /volume1/surveillance /bin/mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata2 /volume1/photo /bin/mount -t 9p -o trans=virtio,version=9p2000.L,posixacl,msize=262144,cache=loose hostdata3 /volume1/homes ;; stop) /bin/umount /volume1/music /bin/umount /volume1/surveillance /bin/umount /volume1/photo /bin/umount /volume1/homes ;; *) echo "usage: $0 { start | stop }" >&2 exit 1 ;; esac Quote Link to comment Share on other sites More sharing options...
hendry Posted February 28, 2022 Share #112 Posted February 28, 2022 @uxora-com why if i tried using fixed ip on macvlan configuration, cannot work ? i already follow the docker run command from your github site.. can u pls try it again ? Quote Link to comment Share on other sites More sharing options...
uxora-com Posted March 2, 2022 Share #113 Posted March 2, 2022 On 2/28/2022 at 12:11 PM, hendry said: why if i tried using fixed ip on macvlan configuration, cannot work ? It still works for me, I think it is something to do with your macvlan directly connected to the vswitch instead of a ethX interface. On 2/28/2022 at 10:53 AM, uxora-com said: and I may give a try to see if dsm ACL works with 9p Well it does not work - posix acl does not seem to be compiled in 9p modules, even if it works it is not use by dsm which use proprietary syno_acl compile in their fs - xattr seems to works but it's not use by dsm - Dsm office seems to be based on synoacl (for security and share management) and cannot work without it So there is nothing much to do about that. HTH, Quote Link to comment Share on other sites More sharing options...
hendry Posted March 3, 2022 Share #114 Posted March 3, 2022 (edited) On 3/2/2022 at 7:02 AM, uxora-com said: It still works for me, I think it is something to do with your macvlan directly connected to the vswitch instead of a ethX interface. Well it does not work - posix acl does not seem to be compiled in 9p modules, even if it works it is not use by dsm which use proprietary syno_acl compile in their fs - xattr seems to works but it's not use by dsm - Dsm office seems to be based on synoacl (for security and share management) and cannot work without it So there is nothing much to do about that. HTH, then there's no way to give permission same as synology has given on 9p mount shared as below ? ash-4.4# ls /volume1 -ale total 4 drwxr-xr-x 1 root root 386 Mar 3 09:58 . drwxr-xr-x 22 root root 4096 Feb 28 19:40 .. drwxr-xr-x 1 root root 204 Mar 3 09:58 @appconf drwxr-xr-x 1 root root 204 Mar 3 09:58 @appdata drwxr-xr-x 1 root root 204 Mar 3 09:58 @apphome drwxr-xr-x 1 root root 204 Mar 3 09:58 @appstore drwxr-xr-x 1 root root 204 Mar 3 09:58 @apptemp drwxrwxrwx 1 root root 120 Feb 28 19:20 @database drwxrwxrwx+ 1 root root 78 Mar 3 09:59 @eaDir [0] everyone::allow:rwxpdDaARWcCo:fd-- (level: 0) drwx--x--x+ 1 root root 34 Mar 1 18:28 homes [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level: 0) [1] owner::allow:rwxpdDaARWcCo:fd-- (level: 0) [2] everyone::allow:--x----------:fd-- (level: 0) d---------+ 1 root root 12 Mar 1 18:19 music [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level: 0) d---------+ 1 root root 12 Mar 3 09:59 photo [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level: 0) drwxr-xr-x 1 root root 88 Feb 28 19:41 @S2S drwxrwxrwx 1 root root 12 Mar 3 09:58 surveillance drwxr-xr-x 1 SurveillanceStation SurveillanceStation 404 Mar 3 10:01 @surveillance drwxr-xr-x 1 root users 22 Mar 1 18:30 @SynoDrive drwxr-xr-x 1 SynoFinder SynoFinder 26 Feb 28 19:20 @SynoFinder-etc-volume drwxr-xr-x 1 SynoFinder SynoFinder 84 Feb 28 19:20 @SynoFinder-log drwxr-xr-x 1 root root 24 Mar 1 18:22 @SynologyApplicationService drwxrwxrwt 1 root root 46 Mar 3 09:59 @tmp drwxrwxrwx 1 root root 62 Mar 1 18:50 @userpreference why docker macvlan for static ip not working ? but dhcp one is working.. as i saw on the virtual switch on the QNAP nas itself, it seems the nas create 1 interface named qvs0 which has mac address same as real eth1 interface port. on qvs0 interface has ip address from the router. you can see this figure i show you... [~] # ifconfig docker0 Link encap:Ethernet HWaddr 8E:45:A1:9B:B6:F4 inet addr:10.100.5.1 Bcast:10.100.5.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1207 errors:0 dropped:0 overruns:0 frame:0 TX packets:24740 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63796 (62.3 KiB) TX bytes:6321764 (6.0 MiB) eth0 Link encap:Ethernet HWaddr 24:5E:BE:40:26:F9 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:132 eth1 Link encap:Ethernet HWaddr 24:5E:BE:40:26:FA UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:179478129 errors:0 dropped:19721 overruns:0 frame:0 TX packets:20858775 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:179571334415 (167.2 GiB) TX bytes:6765255544 (6.2 GiB) Interrupt:133 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:6541413 errors:0 dropped:0 overruns:0 frame:0 TX packets:6541413 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2039041101 (1.8 GiB) TX bytes:2039041101 (1.8 GiB) lxcbr0 Link encap:Ethernet HWaddr B6:B1:EB:13:DE:0F inet addr:10.100.3.1 Bcast:10.100.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6369404 errors:0 dropped:0 overruns:0 frame:0 TX packets:105214576 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1510851333 (1.4 GiB) TX bytes:99263118332 (92.4 GiB) lxdbr0 Link encap:Ethernet HWaddr BA:FA:9B:C6:A4:6E inet addr:10.100.7.1 Bcast:10.100.7.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:21915 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:2971302 (2.8 MiB) qvs0 Link encap:Ethernet HWaddr 24:5E:BE:40:26:FA inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::265e:beff:fe40:26fa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:156085163 errors:0 dropped:148 overruns:0 frame:0 TX packets:15473562 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:153744465305 (143.1 GiB) TX bytes:5821617644 (5.4 GiB) veth29b1ea5 Link encap:Ethernet HWaddr B6:B1:EB:13:DE:0F UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:105188 errors:0 dropped:0 overruns:0 frame:0 TX packets:173221 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25534182 (24.3 MiB) TX bytes:233515172 (222.6 MiB) veth608a897 Link encap:Ethernet HWaddr 8E:45:A1:9B:B6:F4 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1207 errors:0 dropped:0 overruns:0 frame:0 TX packets:24636 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:80694 (78.8 KiB) TX bytes:6296240 (6.0 MiB) vethgw01 Link encap:Ethernet HWaddr 42:68:85:B6:18:3F inet addr:253.253.253.253 Bcast:253.253.253.255 Mask:255.255.255.0 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:21423 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:2874483 (2.7 MiB) vnet0 Link encap:Ethernet HWaddr FE:54:00:B7:F2:3D UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:267250 errors:0 dropped:0 overruns:0 frame:0 TX packets:11551350 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:153308345 (146.2 MiB) TX bytes:10424552052 (9.7 GiB) Edited March 3, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
hendry Posted April 18, 2022 Share #115 Posted April 18, 2022 (edited) hi, @uxora-com any update for DSM 7.1 build 42661 for docker xpenology ? i tried to install it, install process completely but the hostdata not found on running docker xpenology. it seems virtio-9p-pci devices not compatible with the latest build. can u fix your script so can install the latest build ? the latest build used different linux kernel. Linux XPENOLOGY 4.4.180+ #42661 SMP Fri Apr 1 15:33:06 CST 2022 x86_64 GNU/Linux synology_apollolake_918+ does it bring the virtio 9p drivers not working ? Edited April 18, 2022 by hendry Quote Link to comment Share on other sites More sharing options...
quoc vu Posted July 24, 2022 Share #116 Posted July 24, 2022 After install DSM, enter the portal ip:5000, It shows Welcome Back! ... had moved the hard drive .... Press Recover and getting log below. Like HDD image related. /usr/syno/bin/reg_ssdp_service 20.20.20.21 0011322ca785 7.0-42218 synology_bromolow_3615xs eth0 Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh... Starting synoagentregisterd... Running /usr/syno/etc/rc.d/J30DisableNCQ.sh... Running /usr/syno/etc/rc.d/J80ADTFanControl.sh... Running /usr/syno/etc/rc.d/J98nbnsd.sh... Starting nbnsd... Running /usr/syno/etc/rc.d/J99avahi.sh... [ 52.315064] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 52.319223] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 52.329271] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 52.342666] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 52.346820] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 52.357182] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Starting Avahi mDNS/DNS-SD Daemon cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf :: Loading module hid ... [ OK ] :: Loading module usbhid[ 52.595790] usbcore: registered new interface driver usbhid [ 52.599147] usbhid: USB HID core driver ... [ OK ] Excution Error ============ Date ============ Sun Jul 24 04:31:51 UTC 2022 ============================== starting pid 6213, tty '': '/sbin/getty 115200 console' Sun Jul 24 04:31:51 2022 DiskStation login: [ 67.120635] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 67.134596] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 67.166172] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 69.020303] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.028835] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.044414] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 69.189657] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.195278] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.204443] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 69.217123] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.222604] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) [ 69.234154] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Quote Link to comment Share on other sites More sharing options...
kroese Posted March 26, 2023 Share #117 Posted March 26, 2023 I have exactly the same problem as the previous post (which is almost a year old). The initial installation goes without problems, but after rebooting I get the recovery screen and even when doing the recovery, it always returns to that screen every reboot in a loop. So it would be really nice if someone could help us out with what could be wrong. Because I spend hours trying to figure it out, as I suspect it must be something very simple, but I'm still stuck :( Quote Link to comment Share on other sites More sharing options...
miikew Posted April 5, 2023 Share #118 Posted April 5, 2023 hi all can i use this solution to increase camera license ? im running DS3617xs on i5 3450 with 10gb ram , i have 2 cameras working from 6, is it enough hardware to handle those 6 cameras? Quote Link to comment Share on other sites More sharing options...
apriliars3 Posted April 5, 2023 Share #119 Posted April 5, 2023 hi all can i use this solution to increase camera license ? im running DS3617xs on i5 3450 with 10gb ram , i have 2 cameras working from 6, is it enough hardware to handle those 6 cameras?Not possible to licenses. Is only a vDSM without licenses for cameras. Quote Link to comment Share on other sites More sharing options...
hendry Posted October 7, 2023 Share #120 Posted October 7, 2023 is this project still continue for the latest DSM version ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.