ISCSI Software Target - Disk is corrupt (locally) not on on the target

Question

Hi,
I have a Windows 2008R2 server on which i have installed Microsoft iSCSI Software Target. I have created a Virtual Disk and an iSCSI target configuration on this server.
The target is a virtual server running Windows 2012R2. The target has the virtual disk mounted succesfully as a R: drive and i can use it, create files, delete files with no apparent problems.
However on the Win2008R2 box where i have created the virtual disk, i cann see that the virtual disk is also mounted and generates hundreds of errors in the system logs: "The file system structure on the disk is corrupt and unusable. Please run chkdsk
utility on the volume n" The goal is to have the Virtual Disk mounted on the target server but not on the server where the Vdisk is created. Any help would be greatly appreciated.

Answer 1

Hi,
I have a Windows 2008R2 server on which i have installed Microsoft iSCSI Software Target. I have created a Virtual Disk and an iSCSI target configuration on this server.
The target is a virtual server running Windows 2012R2. The target has the virtual disk mounted succesfully as a R: drive and i can use it, create files, delete files with no apparent problems.
However on the Win2008R2 box where i have created the virtual disk, i cann see that the virtual disk is also mounted and generates hundreds of errors in the system logs: "The file system structure on the disk is corrupt and unusable. Please run chkdsk utility
on the volume n" The goal is to have the Virtual Disk mounted on the target server but not on the server where the Vdisk is created. Any help would be greatly appreciated.
If you're trying to mount iSCSI disk from the multiple initiators @ the same time it's not something you can do straightforward because NTFS is not a cluster-aware file system and has no clue about somebody else changing metadata in-place. There many
options (using CSV, using SMB on top of iSCSI, using cluster-aware file system and using distributed lock manager), see detailed description and options listed here:
iSCSI instead of SMB
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
(hosted on StarWind site but is true for any Windows and SAN implementation including one you use)
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.