Sent in. Please let me know if the ZIP comes down properly.

Yep, that's it. Sending it shortly.
Sorry if I missed the fact that it should be less than 20MB.

I attempted to post the case this morning and after pushing submit I got a 500 error. Can you tell me if you received the logs? If not I'll post them up again.

Hi Oleg - I uploaded the logs to the support site as requested. I actually did this on Wednesday when you asked for the logs but I didn't post a reply here until this morning. I named the support case the same as this forum post in my subject.

The logs are uploaded. Hoping that this was some kind of hardware issue.
I will comment that I updated to the latest build of VSAN while we were out (because I like to play fast and loose like that) and it seems to have resolved a memory leak issue I was experiencing.

I will upload the logs now. I grabbed logs when the problem first happened. I will upload those. One drive was not able to come back, but the rest of the drives are online and HA now.

So having done absolutely nothing other than letting both systems sit... I'm now seeing a status of Synchronizing on one drive and the others are waiting. Not sure what happened for 24h but I guess it was courting the HA replica? Maybe they took a night out to get re-acquainted? I'm not sure...

The more I look at this the more I'm thinking that something happened to one of my nodes and caused all of the HA devices on it to become corrupt. Is there a way that I can remove the HA from the existing volumes and then recreate HA by adding a replica partner? or do I need to create all new HA_LSF...

Earlier this morning one of my nodes stopped syncing with the other. Everything on the node which experienced the issue effectively shut off and operations continued as normal. I now have both systems back online and for the past hour and a half watched the first of nine HA devices synchronize. Howe...

I've just completed my second set of patching sessions since we replaced the bad mellanox cards. The system is back up and 100% synchronized with no external intervention within about 30 minutes of the reboot. So I'm going to say that it was deff the Mellanox cards or the DAC cables, that were givin...

Just wanted to report back. This morning I removed and added the replica node back to the system. Where a re-sync on a drive with data would have taken approximately 15 minutes no matter what the drive size, this took approximately 30 seconds. I believe we may have either had bad Mellanox cards or d...

Well in an interesting twist the sync between nodes seems to be a bit more stable and quick... however one of my drives is now refusing to sync with a "mount status: Failed" listed. Trying to bring it back but it is being stubborn.

X520-DA2's installed today. Just going through the initial resync and then we'll turn up all of the services. Thus far we've configured the Intel NICs at the Low Latency setting with Jumbo's enabled and left the rest alone. Using the latest drivers from Intel's site.

We are working to source some replacement Cables and nice for testing. Will report back when we have updates. Thanks!

The files must have been too large for upload. Got the case created and uploaded the files to you. Will report back if/when we figure out what is going wrong.