StarWind Software

Hi,

I have setup a two node VSAN cluster. Both nodes are running Windows Server 2012 R2 and have Storage Spaces RAID0 to store data (yes I know its not recommended).
Every time I launch the iSCSI connection the on either of the nodes the synchronization drops due to IO operation failed.
Creating a device works, replication works. But iSCSI connection just breaks it.

The exact log is < Anton removed VBS script >

Does this happen due to storage spaces or do I have anything else wrong in my setup?

Hi Ekowc, if you are using a free version, only SMB or NFS will work. You cannot use these HA devices as true iSCSI targets.

I've manually edited your post and had removed URL to Visual Basic script you put instead of a screenshot. No idea what you wanted to achieve with that (hope it's just a mistake...) but whatever... Be careful

Ekowc wrote:Hi,

I have setup a two node VSAN cluster. Both nodes are running Windows Server 2012 R2 and have Storage Spaces RAID0 to store data (yes I know its not recommended).
Every time I launch the iSCSI connection the on either of the nodes the synchronization drops due to IO operation failed.
Creating a device works, replication works. But iSCSI connection just breaks it.

The exact log is < Anton removed VBS script >

Does this happen due to storage spaces or do I have anything else wrong in my setup?

Hi,

darklight wrote:Hi Ekowc, if you are using a free version, only SMB or NFS will work. You cannot use these HA devices as true iSCSI targets.

As far as I have understood you have to make a iSCSI connection on the VSAN nodes, then share the disks via SMB.

anton (staff) wrote:I've manually edited your post and had removed URL to Visual Basic script you put instead of a screenshot. No idea what you wanted to achieve with that (hope it's just a mistake...) but whatever... Be careful

It was just a paste from a log, I dunno why it uses vbs at that service. For now I added the log as a screenshot to this post.

After spending a day trying various things I seemed to solve this by changing the sector size.
Setting the Storage Spaces sector size and StarWind VSAN virtual disk sector size to 4096 was the key.

Now lets see if I can get the lab running

StorageSpaces...

YEES! We will include it in StarWind best practices since 512b image block size on top of Storage Spaces may cause such weird issues.

Thanks for the update.