NAS Codex › Synology › Synology iSCSI: initiator can't find or connect to the target, or sees no LUN
Synology iSCSI: initiator can't find or connect to the target, or sees no LUN
Synology's Knowledge Center splits iSCSI connection problems into three cases: the initiator cannot find the target, it finds the target but fails to connect, or it connects but discovers no LUN. Each has its own checks. Synology's troubleshooting article uses the DSM 6.x name iSCSI Manager; in DSM 7 the same settings are in SAN Manager.
Written against: DSM 7 SAN Manager (Synology KB articles last updated Jan 18, 2021 and Sep 16, 2026, plus the SAN Manager iSCSI help page). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
If discovery fails, try it with CHAP turned off. Synology says discovery on the initiator may fail when CHAP authentication is enabled on the NAS: complete discovery first, then enable CHAP before connecting. Alternatively, connect to the target directly with its IP address and IQN.
The initiator can't find the target
- In Windows iSCSI Initiator, go to Discovery > Discover Portal > Advanced Settings > General. If both the initiator and the NAS have more than one network interface, specify the interface to use for iSCSI.
- Make sure Enable CHAP log on is not ticked at this stage. Synology says CHAP can be enabled later, when you connect under Targets.
The initiator finds the target but fails to connect
- In Windows iSCSI Initiator, go to Targets > Connect > Advanced Settings and specify the network interface if both sides have more than one.
- CHAP credentials: the name and password in Windows (Name and Target secret) must be identical to those set on the NAS.
- One host at a time: unless Multiple Sessions (Allow multiple sessions) is enabled on the target, it can only be connected to one host at a time. Synology says to enable it only for cluster-aware storage such as VMFS or OCFS that must be connected to several hosts.
- CRC checksum: it must be enabled on both the initiator and the target, or disabled on both. Synology does not recommend enabling it unless necessary, because it may affect system performance.
- Network binding: in DSM 7, go to SAN Manager > iSCSI, select the target and click Edit > Network Binding to choose which interfaces can reach it.
- Target enabled: targets can be enabled or disabled from the Action menu.
The initiator connects but finds no LUN
- Make sure the LUNs are mapped to the target. In SAN Manager, a target is created with LUN mapping (create a new LUN or map existing LUNs).
- Edit the target and check Masking: the permission for the initiator must be Read/Write or Read Only.
Disconnections, timeouts and slow LUNs
Synology lists sudden disconnection, connection failure, timeouts and high latency as signs of a performance problem. Its suggestions include:
- Choose a smaller stripe cache size for RAID 5, 6, F1 or SHR pools with more than three drives (Storage Manager > Storage, pool Settings > Stripe cache size). Synology notes this can reduce latency but may lower throughput and RAID resync speed.
- Keep all drives in Healthy status, and avoid high volume usage (for example, above 90%).
- Use a dedicated storage pool or volume for busy LUNs, and consider an SSD cache.
- Use a Thick Provisioned LUN instead of a Thin Provisioned one.
- Schedule backups and snapshot retention at different times so heavy I/O doesn't overlap.
- Put iSCSI on a dedicated network, or connect the host directly to the NAS, and bind the target to only that interface.
- On VMware hosts, Synology recommends disabling ATS heartbeat and setting the iSCSI adapter's LoginTimeout to 60, NoopTimeout to 30 and DelayedAck to false.
When to stop and get help
Synology warns that removing a LUN deletes all data on it. If more than one initiator must use the same target, Synology strongly suggests a shared or cluster file system such as VMFS or OCFS to protect against corruption or data loss.
Questions
Why can't my iSCSI initiator discover my Synology target?
Synology says discovery may fail if CHAP authentication is enabled on the NAS. Complete discovery first and enable CHAP afterwards, or connect with the target's IP address and IQN.
Why does my iSCSI initiator connect to my Synology NAS but show no disk?
Synology says to make sure the LUN is mapped to the target and that the target's Masking permission is Read/Write or Read Only for the initiator.
Can a Synology iSCSI target be connected to two hosts?
Only if Multiple Sessions is enabled. Synology says otherwise a target can only be connected to one host at a time, and recommends a cluster file system such as VMFS or OCFS for shared use.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.