I've been watching this, after I checked the hosts and convinced myself there was no reason for them to be causing it I set up Performance Monitors on the guests to identify the source of the problem and... it stopped. Typical. :) I'm convinced it was something a user was doing, we do a lot of testi...

Here are the log files: https://1drv.ms/f/s!An_uTU8KpVOAajvxdd4xHSWRlH0 The two nodes are in a cluster together. There aren't any backup tasks. Both CSVs sit on RAID10 arrays made of 10 2TB HDDs @ 7200RPM? (ST2000DM001). Each node supports 4 VMs. There's a picture I made of how it works on that link...

Occasionally, although not every day, at about 1200 I am getting a string of about a dozen messages from one of my nodes about Storage Performance Degradation. The messages stop after maybe a minute. I have two nodes and have received warnings from both about different CSVs. I've seen these warnings...

I've learned that you can't rely on the RAID management software to tell you if there's a problem, so now I have a filtered event log getting items from the System log in the Task Category "Storage Service" which has much more useful information for you. With Michael's help I also sorted o...

I'm going to tell myself that you all deal with this stuff so you know how I feel. Forgive my rambling on but I decided to try something and go to the old standby, restart it. I moved the Roles and stopped Starwind on the node which isn't synchronised and didn't appear to be getting anywhere. I've j...

I've been reading https://www.starwindsoftware.com/technical_papers/starwind-virtual-san-installation-and-configuration-of-hyperconverged-2-nodes-with-hyper-v-cluster.pdf this morning. I've found one thing which doesn't match the document I used to set mine up. My nodes have, amongst other things, a...

Hello D9BDCEA2CE, Your theory is correct - when one node fails, everything should switch to another node, so in Failover Cluster Manager, CSV should change the owner without any interruptions. Firstly, please check from StarWind Management console that all StarWind devices are synchronized on both ...

I never got round to it over the weekend, however I've come in this morning and there seems to be a problem. The Starwind Virtual SAN service on one node was stopped and when I started it the system began synchronisation. However that doesn't seem to be working. I'm getting this and similar messages...

That's my theory anyway, when I cancelled it everything came back. I have two Nodes hosting several Roles. I have seen (more than once until I learned how to deal with driver updates better) the Roles go to FAILED because they've lost their storage. I resolve the problem with connecting to Starwind ...

It's been a while but I find myself hunting around the internet and coming across answers from a while ago so I'll finish the story... What I wasn't doing, as Rajesh was directing me towards although I didn't understand, was stopping the Starwind service before I fiddled about with things - it doesn...

Reading back through this post (see Rajesh's comment), I'm beginning to wonder - if I had stopped the Starwind Virtual SAN service on Node2 before I did the maintenance, would Starwind have brought the copy of CSV1 it has on Node1 online and used that until I started the service on Node2 again? That...

Each cluster node has five discs, two are real and three are called STARWIND STARWIND Multi-Path Disk Device. They correlate to CSV1, CSV2 and Witness1. On Node 1: CSV1 is Offline, CSV2 is online, Witness1 is online. On Node 2: CSV1 is Online, CSV2 is offline, Witness1 is offline. I think that means...

More info: These all happened at about 08:37 High Availability Device iqn.2008-08.com.starwindsoftware:cls01-csv1, all heartbeat Connections with Partner Node iqn.2008-08.com.starwindsoftware:cls02-csv1 lost High Availability Device iqn.2008-08.com.starwindsoftware:cls01-csv1, current Node passed to...

Hmmm... Today I decided to update the NIC drivers on one of my nodes - I like to keep firmware and drivers up to date where possible. I left it all alone after the last incident but I've been aware the two nodes were using different drivers and felt I should resolve it. I planned to space the update...

It was several times in one morning. It sounds like I need to space out my updates if I try to do it again.