Issue with Microsoft updates - HyperV S2D

Question

Hello team,

I have an s2d cluster, (3 nodes) and starting from the last week i'm seing many crashes on the 3 nodes :

Event ID 41 : The system has rebooted without cleanly shutting down first

Details :

  BugcheckCode 127 
  BugcheckParameter1 0x8 
  BugcheckParameter2 0xffffca80d088ae50 
  BugcheckParameter3 0xffff9e0d05048ff0 
  BugcheckParameter4 0xfffff80128684cab 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI false 
  CheckpointStatus 0 

Note that the only thing that changed is the installation of the following KBs in the 3 nodes last week : KB5032306
KB5031984
KB5033371

The crashes has started the day after the install of these KBs on the 3 nodes

Anyone here had an issue with the following KBs ?

I'm waiting to uninstall them.

Another question, is there any way to reset the system of an s2d hyperV node without recreating the cluster ? what is the action plane for this?

Thanks

Answer 1

Hi Mohamed, Hope you're doing well. Event ID 41 with BugcheckCode 127 indicates a critical error that led to a system reboot. The BugcheckParameters provide additional details about the error, but further analysis would typically require examining memory dump files or other diagnostic logs. As for the KBs you mentioned (KB5032306, KB5031984, KB5033371), these are Windows Update packages, and sometimes updates can cause compatibility issues. It's not uncommon for administrators to experience problems after installing updates. Uninstalling these updates is a reasonable step to take if you suspect they may be the cause of the crashes. Regarding resetting the system of an S2D Hyper-V node without recreating the cluster:

1. Pause Node: You can temporarily pause a node in Storage Spaces Direct (S2D) without evicting it from the cluster. This is useful if you need to perform maintenance on a specific node. Use the "Pause-ClusterNode" PowerShell cmdlet to pause a node. Pause-ClusterNode -Name <NodeName> -Cluster <ClusterName>
2. Drain Roles: Before performing any maintenance on a node, it's a good idea to drain the roles from that node. This ensures that no VMs or other cluster resources are running on the node. Get-ClusterGroup | Where-Object {$_.State -eq 'Online'} | Move-ClusterGroup -Node <NodeName>
3. Reset Node: Perform the necessary maintenance or troubleshooting on the node. If you need to reset the node, you can use the "Reset-ClusterNode" cmdlet. Reset-ClusterNode -Name <NodeName> -Cluster <ClusterName>
4. Resume Node: After completing the necessary tasks, you can resume the node to allow it to participate in the cluster again. Resume-ClusterNode -Name <NodeName> -Cluster <ClusterName> Remember to replace "<NodeName>" and "<ClusterName>" with the actual names of your node and cluster. Before performing any actions, make sure you have a backup and understand the potential impact on your environment. At the same time, it's best to choose downtime to do these operation. If you are worried about something going wrong, I suggest you to go to the Microsoft Customer Service Center to open a Premier-level case so that with their permission level and resource, Microsoft could provide you with better help on your request. This is the best option. I hope this helps! Best Regards Best Regards, Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.