iSCSI
-
What Is an iSCSI LUN? What Backs It and Who Owns It
An iSCSI LUN is a block volume inside a target that one host sees as a raw local disk. What backs it, how mapping works, and when to skip it.
-
iSCSI vs SMB for a Homelab NAS: Which One to Pick
iSCSI vs SMB on a homelab NAS: pick SMB for shared files, Macs and Time Machine, and an iSCSI LUN only for a disk one machine owns.
-
NFS vs iSCSI for a Homelab: Which One to Pick
NFS vs iSCSI for a homelab NAS: pick NFS for shared media, ISOs and backups, and iSCSI only for a disk one host owns. Here is why.
-
How to Set Up an iSCSI Target on TrueNAS: Zvol to Login
Set up an iSCSI target on TrueNAS 25.10: create a zvol, run the block share wizard, lock it to one IQN with CHAP, then connect from Linux or Windows.
-
iSCSI Target Setup on Windows Server: LUNs and MPIO
Install the iSCSI Target Server role, create a VHDX LUN, mask it to an initiator IQN, then connect with CHAP and MPIO using PowerShell.
-
iSCSI vs NFS vs SMB: Choosing a Storage Protocol
This comparison explains how iSCSI, NFS and SMB differ in filesystem ownership, locking, path redundancy, security and failure behavior.
-
Unraid iSCSI Target Setup: Plugins, LUNs and CHAP
Set up Unraid iSCSI with a community target plugin, pool-backed LUNs and CHAP, then follow TrueNAS, Synology and Proxmox connection workflows.
-
iSCSI Troubleshooting: Login, Timeout and Path Errors
A layered method for iSCSI faults: portal reachability, discovery, login, ACL and CHAP mismatches, MTU stalls, and the timers that decide when I/O fails.
-
What Is an iSCSI LUN? Targets, Initiators and MPIO
An iSCSI LUN is the address of a logical unit in a target. Learn how initiators, IQNs, CHAP and MPIO fit together, and why MPIO is not link aggregation.