Greetings,

We can confirm that 512 virtual disks cannot be created on a 4k sector-size physical disk (which is Perc12 VD in your case). We are working on implementing support for such scenario.

We will update the community once we have any updates.

Benoire,
Sounds great! Please keep us posted about the testing.

link855,
Unfortunately, everything looks like that your CPU does not support encryption method which we are using for our StarWind VSA.
Update for community: we are still working on the VSA 2.0. Please stay tuned for updates.

Benoire, Feel free to check the Storage Spaces inside the VM. StarWind will work perfect either on SS or VMDK. I would recommend assigning more Compute resources for VM with Storage Spaces. You can test both scenarios, compare it and we will much appreciate if you will share the results with our com...

Hello Matt001, If I understand you properly, I am not sure that it will work as expected, because VMs inside the HA general file server will be interrupted in case, if the role will migrate to the second server. Could you clarify, what the point of deploying two VMs to create the File-server if you ...

Hello Rob,
Please submit a support ticket here: https://www.starwindsoftware.com/support-form and mention the link to this thread, thus I believe we could resolve license issue.
Thank you.

Hello, InphinitePhractals,
Glad to hear that!
You are always welcome, feel free to contact us whether you have any additional questions or need our assistance.
Thank you.

Hello InphinitePhractals,
Thank you for your answer and information.
Please do not hesitate to contact StarWind support directly if you need our assistance on it.
Also, feel free to ask any additional questions.
Thank you!

Tiaccadi, In this way, I'll have two different 10 Gbit channels.. but I cannot understand what are you advicing me to do with them :D Do you suggest me to use 1 10 Gbit channel for sync and the other 10 Gbit channel for iSCSI? Yes, that's correct. To avoid any issues with sync channel and performanc...

Hello InphinitePhractals, Basic steps are: 1. Open Failover Cluster Manager and move all storage from the second node to the first node . 2. Open StarWind Management console (if exists). 3. Check synchronization status of StarWind devices. In case, your StarWind Management Console is expired you nee...

Hello tiaccadi, iSCSI1 and iSCSI2 will be the two 10 Gbit ports, and they will host StarWind replication traffic too I would recommend you to use different one 10 GB port per server for replication (StarWind Sync) and it is highly recommended direct connection for StarWind Synchronization (port-to-p...

Hello Brian,
You are always welcome.
Thank you.

Hello lupacexi, StarWind devices are block devices (working only on block level) and have no filesystem. I can suggest to create a test StarWind device, connect it via iSCSI and format the drive with ReFS filesystem which supports snapshots. However, ReFS is still not "rock solid". If you ...

Hello tiaccadi, The performance penalty of adding StarWind in to the mix on one node will be negligible. Once you add in the second node your write IO will go down slightly (which can be countered with write back L1 cache), however your reads IO will be nearly double what it was (due to read operati...

Hello TheBoy,
Unfortunately, right now we do not have any powershell script to create the Access rights. For now, you can specify the ACL only in a GUI.
We are working on adding the new powershell scripts to achieve the fully functional StarWindX as well as Management console.
Thank you.