I am running a 2-node Hyper-V Hyperconverged Starwind SAN and have started having some issues with the software (it's being slow and occasionally timing-out to the point where my entire cluster dies). I see lots of the follow error message in my Server Log in StarWind Management Console (even now, s...

I can confirm that I also have the same problem (not thousands though, just a few every few days) on both nodes of my Hyperconverged 2-node setup (with 2 10GbE links cross-connected for iSCSI and heartbeat). I have the latest version, with only L1 cache (as I had some severe corruption problems with...

I spoke too soon. :- ( I've still had the problem and have spent the last month trying to track down the issue. I've finally figured it out (sort of). Essentially, there are 2 issues (using Failover Only as the MPIO policy): 1) The MPIO paths aren't sticking around between boots. For example, the CS...

We're working on a set of Intel I/O Meter scripts you could run to get fixed (10%, 25%, 50% and 75% etc) "cache hit" ratios so real performance could be tested. Impact on 100% cache miss is 5-10% compared to a non-cached config. RAM cache does another job except speed up - it "adsorb...

<snip> After setting up the 2TB virtual hard drive, I launched Replication Manager and added a replica of CSV1 on Server 2, specifying the VLAN IP addresses. This is where I noticed the first issue. It took 5 hours and 40 minutes to create the replica. <snip> The recommendation from https://knowled...

I can confirm that the most recent build (8198) still has the same problem with "large" caches (~33GB L1 and 1TB L2), attached to a 1GB device (that gets expanded to a 5TB device after initial synchronization). The problem previously appeared with build 8116.

Thanks.

Branin

Vitaliq,

Thank you very much! I know this will all be worth it in the end. :- )

I just emailed the requested documents (except for the minidump files, which don't seem to have been generated this time).

Thanks!

Branin

Branin- Earlier in the thread, it was mentioned that you connect the opposite witness to pass the failover cluster validation. If you connected those targets (connected to witness2 from node1 and witness1 from node2), make sure that they are disconnected from the Targets tab and also removed from t...

Branin, May I wonder if there are any updates than those described here https://forums.starwindsoftware.com/viewtopic.php?f=5&t=4274 ?? I believe I was able to "fix" this particular issue with the previous build (i.e. before 8116 and the L2 cache functionality), through 1 of 2 differe...

I hope you agree with me that it does not look like StarWind related issue. And I understand that MS support might not be helpful since StarWind is installed. MS and StarWind might point each other (sorry guys :roll: ), but as far as I know StarWind guys troubleshoot even indirect issues that are n...

I went to lunch and when I came back, I was able to start Starwind on the first node. Neither of my replicated targets/devices synchronized though. I had to manually pick one and "Mark as synchronized".

Is this normal?

Thanks!

Branin

I seem to be getting all sorts of errors, but can't figure out what I'm doing wrong. I've downloaded and am now using version 8116 (the most recent, as far as I can tell). I've followed the instructions in the Hyper-Converged 2 Nodes Scenario 2 Nodes with Hyper-V Cluster document, while also followi...

LOL. Don't worry.

Me as well. I'm about out of ideas and may just go to Hyper-V Replicas (which could result in a minute of data loss, but at least work...). Still trying a few more things though to try to work around the Starwind issue. If any of them work, I'll write it up here.

They are (the witness is typically on NW-VMHOST01 and I'm putting the CSVs on NW-VMHOST02). It doesn't matter. Generally, at least one of the CSVs failing over don't finish successfully (timing out and leading to a "failed" status). 15 minutes later, the CSV is good, but then I still need ...