Cannot access DSM after initial setup

[andreschoppe]

Operating system

Unraid

Description

Hi there,
I absolutely want to get this VDSM going but I am not able to set it up properly apparently :-)
So my setup is an Unraid server (with docker installed obviously) and I want the VDSM to have an own IP within my network. It seems to work at the beginning - I can watch the DSM setup for approx. 20 seconds with the given IP adress+port but then all of a sudden my browser looses connection and I cannot re-establish it. Docker logs didn't give me any hints so I hope, someone can help with this issue.
Thanks in advance for any hints on this,
André

Docker compose

services:
  dsm:
    container_name: dsm
    image: vdsm/virtual-dsm
    environment:
      DISK_SIZE: "256G"
    devices:
      - /dev/kvm
      - /dev/net/tun
    device_cgroup_rules:
      - 'c *:* rwm'
    cap_add:
      - NET_ADMIN
    volumes:
      - ./dsm:/storage
    restart: always
    stop_grace_period: 2m
    networks:
      br0:
        ipv4_address: 192.168.0.10

networks:
  br0:
    external: true

Docker log

[  OK  ] Started Syno Data Protection - Btrfs Snaptree reconstruct.

[  OK  ] Started Synology task resume for Storage Manager.

         Starting Synology daemon for monitoring space/disk/cache status...

[  OK  ] Started Syno Data Protection - Btrfs Deleted Subvolume Clean.

[  OK  ] Started Check Synology shared folders.

         Starting Migrate all volume and share to quota DB...

         Starting Check share snapshot...

[  OK  ] Started Migrate all volume and share to quota DB.

[  OK  ] Started Check share snapshot.

[  OK  ] Started Set IP Conflict Detect.

[  OK  ] Reached target Synology shared folders.

         Starting Shared Folder Sync Daemon...

         Starting Accountdb cache database...

         Starting Remove session if the option enabled....

         Starting Daemon for Recycle Bin...

         Starting synotifyd...

         Starting daemon for handle hotplug event...

         Starting Build DB link for synolog...

         Starting deal with remote/ISO mount during when bootup and poweroff...

[  OK  ] Started Accountdb cache database.

[  OK  ] Started synotifyd.

[  OK  ] Started Daemon for Recycle Bin.

[  OK  ] Started Synology daemon for monitoring space/disk/cache status.

         Starting Sync data scrubbing config...

[  OK  ] Started Shared Folder Sync Daemon.

[  OK  ] Reached target Packed In File Protocols.

[  OK  ] Started Remove session if the option enabled..

[  OK  ] Started move user preference folder to volume..

         Starting Synology CGI Auth Daemon...

[  OK  ] Started Synology CGI Auth Daemon.

[  OK  ] Started deal with remote/ISO mount during when bootup and poweroff.

[  OK  ] Started daemon for handle hotplug event.

[  OK  ] Started SNMP Daemon.

         Starting Daemon for Resource Monitor...

[  OK  ] Started Daemon for Resource Monitor.

[  OK  ] Started daemon for monitor logs and generate alert.

[  OK  ] Started Set Policy Route.

[  OK  ] Started Sync data scrubbing config.

[  OK  ] Started Build DB link for synolog.

[   18.135053] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)

[  OK  ] Started Nginx.

         Starting install builtin packages for priority high...

         Starting SSDP service...

[  OK  ] Started SSDP service.

[   18.299492] Synotify use 16384 event queue size

[   18.300269] Synotify use 16384 event queue size

[  OK  ] Started Synology SCGI SocketIO.

         Starting synodrnode_reset...

[  OK  ] Started synodrnode_reset.

[  OK  ] Reached target Multi-User System.

[  OK  ] Started Preload synopki data to cache.

         Starting Preload synopki data to cache...

         Starting Check if DS has a connected printer. If so, enable cups....

[  OK  ] Started Synology Get EW Info Status.

         Starting Synology Get EW Info Status...

         Starting Synology Cache Advisor Boot Clean Up...

         Starting Execute packages' scripts during the boot-up...

         Starting Update synoinfo.conf suppo...ding to virtual hardware spec...

         Starting Customized post-install configuration...

         Starting Initial Disk Health Database...

         Starting Before upgrade ready...

         Starting Check normal shutdown or improper shutdown...

         Starting Support channel checker...

         Starting Periodic Command Scheduler...

         Starting Check malware and execute rc.local...

         Starting Synology Web console login prepare...

[  OK  ] Started Check if DS has a connected printer. If so, enable cups..

[  OK  ] Started Execute packages' scripts during the boot-up.

[  OK  ] Started Customized post-install configuration.

[  OK  ] Started Support channel checker.

[  OK  ] Started Check malware and execute rc.local.

[  OK  ] Started Synology Web console login prepare.

[  OK  ] Started Periodic Command Scheduler.

[  OK  ] Started Update synoinfo.conf suppor...ording to virtual hardware spec.

[  OK  ] Started Initial Disk Health Database.

[  OK  ] Started Check normal shutdown or improper shutdown.

[  OK  ] Started Synology Cache Advisor Boot Clean Up.

[  OK  ] Started Before upgrade ready.

Thu Dec 11 08:17:14 2025



VirtualDSM login: [   44.250977] iSCSI:target_core_rodsp_server.c:1025:rodsp_server_init RODSP server started, login_key(358e0fe2d1f3).

[   44.257630] syno_extent_pool: module license 'Proprietary' taints kernel.

[   44.258998] Disabling lock debugging due to kernel taint

[   44.260397] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized

[   44.268016] iSCSI:target_core_device.c:612:se_dev_align_max_sectors Rounding down aligned max_sectors from 4294967295 to 4294967288

[   44.270394] iSCSI:target_core_configfs.c:5763:target_init_dbroot db_root: cannot open: /etc/target

[   44.272341] iSCSI:target_core_lunbackup.c:366:init_io_buffer_head 2048 buffers allocated, total 8388608 bytes successfully

[   44.282756] iSCSI:target_core_file.c:152:fd_attach_hba RODSP plugin for fileio is enabled.

[   44.284420] iSCSI:target_core_file.c:159:fd_attach_hba ODX Token Manager is enabled.

[   44.285983] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.

[   44.287780] iSCSI:target_core_ep.c:795:ep_attach_hba RODSP plugin for epio is enabled.

[   44.289374] iSCSI:target_core_ep.c:802:ep_attach_hba ODX Token Manager is enabled.

[   44.338835] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512

❯ -----------------------------------------------------------

❯  You can now login to DSM at port 5000

❯ -----------------------------------------------------------

[   46.314327] findhostd uses obsolete (PF_INET,SOCK_PACKET)

[   48.281219] fuse init (API version 7.23)

Screenshots (optional)

No response

[timo1235]

Same here after updating my host to unraid 7.2.2

I used fixed IP with macvlan

services:
  vdsm:
    container_name: vdsm
    image: vdsm/virtual-dsm
    environment:
      GPU: "Y"
      DISK_SIZE: "200G"
      DISK2_SIZE: "2500G"
      DISK_FMT: "qcow2"
      HOST_SERIAL: XXXX
      HOST_MODEL: DS920+
      HOST_MAC: XXXXX
      MAC: XXXX
      GUEST_SERIAL: XXXX
    networks:
      br0:
        ipv4_address: 192.168.1.5
    devices:
      - /dev/dri
      - /dev/kvm
      - /dev/net/tun
      - /dev/vhost-net
    device_cgroup_rules:
      - 'c *:* rwm'
    cap_add:
      - NET_ADMIN
    ports:
      - 5000:5000
    volumes:
      - /mnt/user/vdsm/storage1:/storage
      - /mnt/user/vdsm/storage2:/storage2
    restart: unless-stopped
    stop_grace_period: 2m
    
networks: 
  br0:
    external: true

It worked before with the same config. What wonders me is that I can still reach it with caddy as reverse proxy, but not using the IP 192.168.1.5 directly, although I can ping it.

What I noticed:
Since I can access the DSM via reverse proxy, in the system settings under network the IP was before(when everything was working) something like 20.20.20.21 and after the OS update it changed to 172.30.1.5 (the interface is set to DHCP).
Also it seems that the DSM itself has no internet access anymore. Package manager says it's offline and I cannot install/update anything.

If I now change vdsm to use bridge networking and remove the fixed IP stuff, everything is working again. Also package Manager etc.

Seems that the OS update changed something here. Sadly Im not that familiar with networking.

Maybe someone with more networking knowledge can help out, and maybe its the same problem @andreschoppe has.