TalAloni
Regarding the issue of spanned volumes
When I mount a spanned volume, and the spanned volume is larger than 3T, the loaded disk is wrong and the disk size is also wrong. When I mount a 600G spanned disk, it is correct, which is very strange.
Thanks for the report, please be more specific, what's the actual size and what's the size that's being displayed?
The spanned volume created by two 1788.12G disks is 3.49T together, but after being mounted, it is 4.4T, and the disks are garbled and unrecognizable.
Sorry, I'm too busy at the moment and was not able to get to it, feel free to take a look at the code and help me find the issue.
After recreating this scenario I now understand that what you are experiencing is not an issue with iSCSI Console, but rather a limitation of Microsoft Windows.
When you select a spanned volume as a disk to be served by iSCSI Console, it will serve that volume as a disk. This volume does not have a partition table, and if this volume is NTFS-formatted, this volume / served disk will start with the NTFS boot sector.
Windows does support disks with no partition table that start with an NTFS boot sector (that's how many USB flash drives are formatted), however to my understanding this support is limited to 2 TB NTFS volumes, when the volume is larger than that, it seems that Windows will not handle that situation as you expect.
For NTFS volumes > 2 TB to be mounted correctly, it seems that a GPT partition table is required. you can use iSCSI Console to serve an unformatted volume and then have the client initialize that disk as GPT and create an NTFS volume > 2 TB on it successfully.