Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic

90 events across 3 channels

Event ID	Title	Channel
1		Operational
1	Disk %1 has arrived.	Operational
2		Operational
2	Disk %1 is claimed by clusbflt.	Operational
3		Operational
3	Disk %1 is not claimed by clusbflt, Status %2.	Operational
8		Operational
8	Disk %1 was removed.	Operational
51		Operational
51	Enclosure arrived	Operational
52		Operational
52	Enclosure removed	Operational
101		Operational
101	Path %1 (attributes=%3, type=%4) was created for device %2.	Operational
102		Operational
102	Path %1 (attributes=%3, type=%4) was removed for device %2.	Operational
103		Operational
103	Path %1 (attributes=%3, down path=%4) was paused for device %2.	Operational
104		Operational
104	Path %1 (attributes=%3, down path=%4) was resumed for device %2.	Operational
105		Operational
105	Path %1 (attributes=%3, down path=%4) was resumed on timeout for device %2.	Operational
151		Operational
151	Received request to update membership to %1, flags = %2.	Connectivity
152		Operational
152	Completed request to update membership to %1, flags = %2, status %3.	Connectivity
153		Operational
153	Completed request to set registration key to %1, status %2.	Connectivity
154		Operational
154	Client cluster with Id %1 and instance id %2 registered.	Connectivity
155		Operational
155	Client cluster with Id %1 and instance id %2 unregistered on client request.	Connectivity
156		Operational
156	Client cluster with Id %1 and instance id %2 unregistered because no hearbeat …	Connectivity
157		Operational
157	Received client cluster membership update from node id %1.	Connectivity
158		Operational
158	Applied client cluster membership update from node id %1.	Connectivity
159		Operational
159	Target create for cluster node id %1 for path %2 with cluster Id %3, instance id …	Connectivity
160		Operational
160	Target create request rejected from cluster node id %1 for path %2 with cluster …	Connectivity
201		Operational
201	Node %1 connected to path %2 device %3.	Connectivity
202		Operational
202	Node %1 disconnected from path %2 device %3.	Connectivity
251		Operational
251	Remove all partitions from device %1 (%2), Status=%3.	Operational
252		Operational
252	Trim device %1 (%2), Status=%3.	Operational
253		Operational
253	Create Hdd Cache partition on device %1 (%2), Status=%3.	Operational
254		Operational
254	Initialize Hdd Cache partition on device %1 (%2), Status=%3.	Operational
255		Operational
255	Initialize Ssd Cache Store partition on device %1 (%2), PartitionId %3, …	Operational
256		Operational
256	Create Ssd Cache Store partition on device %1 (%2), Reserve %3 percent, …	Operational
257		Operational
257	Bind Hdd device %1 (%2) to Cache Store Partition %3 on device %4 (%5), …	Operational
258		Operational
258	UnBind Hdd device %1 (%2), Options %3, AddedMissingPages=%4, Status=%5.	Operational
259		Operational
259	Disable Binding on Sdd device %1 (%2), Partition Id %3, Binding %4, Hdd Device …	Operational
260		Operational
260	Set Binding Attributes on device %1 (%2), Partition Id %3, Binding %4, Hdd …	Operational
261		Operational
261	Disabled Read and Write Cache on Ssd Cache Store partition on device %1 (%2), …	Operational
301		Operational
301	Runtime error in %1@%2, Status=%3.	Operational
351		Operational
351	Starting to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.	Operational
352		Operational
352	Loaded Cache Store on device %1 (%2), PartitionId %3, Status=%4.	Operational
353		Operational
353	Failed to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.	Operational
401		Operational
401	Data mismatch detected at bottom layer.	Operational
402		Operational
402	Data mismatch detected at top layer.	Operational
403		Operational
403	Data mismatch detected at standby.	Operational
404		Operational
404	Bad IO completion at bottom layer.	Operational
405		Operational
405	Bad IO completion at top layer.	Operational
406		Operational
406	Overlapping IOs detected	Operational
407		Operational
407	Prohibited IOCTL was rejected.	Operational

Event ID 1 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceId`	—

Event ID 1 — Disk %1 has arrived.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disk %1 has arrived

Fields

Name	Description
`DeviceId`	—

Event ID 2 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceId`	—

Event ID 2 — Disk %1 is claimed by clusbflt.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disk %1 is claimed by clusbflt

Fields

Name	Description
`DeviceId`	—

Event ID 3 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceId`	—
`Status`	—

Event ID 3 — Disk %1 is not claimed by clusbflt, Status %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disk %1 is not claimed by clusbflt, Status %2

Fields

Name	Description
`DeviceId`	—
`Status`	—

Event ID 8 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceId`	—

Event ID 8 — Disk %1 was removed.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disk %1 was removed

Fields

Name	Description
`DeviceId`	—

Event ID 51 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Event ID 51 — Enclosure arrived

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Enclosure arrived

Event ID 52 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Event ID 52 — Enclosure removed

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Enclosure removed

Event ID 101 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`PathType`	—

Event ID 101 — Path %1 (attributes=%3, type=%4) was created for device %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Path %1 (attributes=%3, type=%4) was created for device %2

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`PathType`	—

Event ID 102 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`PathType`	—

Event ID 102 — Path %1 (attributes=%3, type=%4) was removed for device %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Path %1 (attributes=%3, type=%4) was removed for device %2

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`PathType`	—

Event ID 103 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 103 — Path %1 (attributes=%3, down path=%4) was paused for device %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Path %1 (attributes=%3, down path=%4) was paused for device %2

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 104 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 104 — Path %1 (attributes=%3, down path=%4) was resumed for device %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Path %1 (attributes=%3, down path=%4) was resumed for device %2

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 105 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 105 — Path %1 (attributes=%3, down path=%4) was resumed on timeout for device %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Path %1 (attributes=%3, down path=%4) was resumed on timeout for device %2

Fields

Name	Description
`PathId`	—
`DeviceId`	—
`Attributes`	—
`DownPathId`	—

Event ID 151 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`Membership`	—
`Flags`	—
`Status`	—

Event ID 151 — Received request to update membership to %1, flags = %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Received request to update membership to %1, flags = %2

Fields

Name	Description
`Membership`	—
`Flags`	—
`Status`	—

Event ID 152 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`Membership`	—
`Flags`	—
`Status`	—

Event ID 152 — Completed request to update membership to %1, flags = %2, status %3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Completed request to update membership to %1, flags = %2, status %3

Fields

Name	Description
`Membership`	—
`Flags`	—
`Status`	—

Event ID 153 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`RegistrationKey`	—
`Status`	—

Event ID 153 — Completed request to set registration key to %1, status %2.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Completed request to set registration key to %1, status %2

Fields

Name	Description
`RegistrationKey`	—
`Status`	—

Event ID 154 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 154 — Client cluster with Id %1 and instance id %2 registered.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Client cluster with Id %1 and instance id %2 registered.

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 155 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 155 — Client cluster with Id %1 and instance id %2 unregistered on client request.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Client cluster with Id %1 and instance id %2 unregistered on client request.

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 156 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 156 — Client cluster with Id %1 and instance id %2 unregistered because no hearbeat was received for 1 minute.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Client cluster with Id %1 and instance id %2 unregistered because no hearbeat was received for 1 minute.

Fields

Name	Description
`ClusterId`	—
`InstanceId`	—

Event ID 157 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`ClusterId`	—
`InstanceId`	—
`SequenceNumber`	—
`MembershipMask`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—
`CurrentSequenceNumber`	—
`CurrentMembershipMask`	—

Event ID 157 — Received client cluster membership update from node id %1.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Received client cluster membership update from node id %1. Cluster Id %2, instance id %3, membership sequence %4, nodeset mask %5. Existing cluster id %6, instance id %7, membership sequence %8, nodeset mask %9

Fields

Name	Description
`NodeId`	—
`ClusterId`	—
`InstanceId`	—
`SequenceNumber`	—
`MembershipMask`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—
`CurrentSequenceNumber`	—
`CurrentMembershipMask`	—

Event ID 158 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`ClusterId`	—
`InstanceId`	—
`SequenceNumber`	—
`MembershipMask`	—

Event ID 158 — Applied client cluster membership update from node id %1.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Applied client cluster membership update from node id %1. Cluster Id %2, instance id %3, membership sequence %4, nodeset mask %5.

Fields

Name	Description
`NodeId`	—
`ClusterId`	—
`InstanceId`	—
`SequenceNumber`	—
`MembershipMask`	—

Event ID 159 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`PathId`	—
`ClusterId`	—
`InstanceId`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—
`Status`	—

Event ID 159 — Target create for cluster node id %1 for path %2 with cluster Id %3, instance id %4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Target create for cluster node id %1 for path %2 with cluster Id %3, instance id %4. Existing cluster id %5, instance id %6. Status=%7

Fields

Name	Description
`NodeId`	—
`PathId`	—
`ClusterId`	—
`InstanceId`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—
`Status`	—

Event ID 160 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`PathId`	—
`ClusterId`	—
`InstanceId`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—

Event ID 160 — Target create request rejected from cluster node id %1 for path %2 with cluster Id %3, instance id %4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Target create request rejected from cluster node id %1 for path %2 with cluster Id %3, instance id %4. Existing cluster id %5, instance id %6.

Fields

Name	Description
`NodeId`	—
`PathId`	—
`ClusterId`	—
`InstanceId`	—
`CurrentClusterId`	—
`CurrentInstanceId`	—

Event ID 201 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`PathId`	—
`DeviceId`	—

Event ID 201 — Node %1 connected to path %2 device %3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Node %1 connected to path %2 device %3

Fields

Name	Description
`NodeId`	—
`PathId`	—
`DeviceId`	—

Event ID 202 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`NodeId`	—
`PathId`	—
`DeviceId`	—

Event ID 202 — Node %1 disconnected from path %2 device %3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Connectivity

Message

Node %1 disconnected from path %2 device %3

Fields

Name	Description
`NodeId`	—
`PathId`	—
`DeviceId`	—

Event ID 251 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 251 — Remove all partitions from device %1 (%2), Status=%3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Remove all partitions from device %1 (%2), Status=%3.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 252 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 252 — Trim device %1 (%2), Status=%3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Trim device %1 (%2), Status=%3.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 253 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 253 — Create Hdd Cache partition on device %1 (%2), Status=%3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Create Hdd Cache partition on device %1 (%2), Status=%3.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 254 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 254 — Initialize Hdd Cache partition on device %1 (%2), Status=%3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Initialize Hdd Cache partition on device %1 (%2), Status=%3.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Status`	—

Event ID 255 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 255 — Initialize Ssd Cache Store partition on device %1 (%2), PartitionId %3, Status=%4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Initialize Ssd Cache Store partition on device %1 (%2), PartitionId %3, Status=%4.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 256 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`ReservePercentage`	—
`UnusedSize`	—
`Status`	—

Event ID 256 — Create Ssd Cache Store partition on device %1 (%2), Reserve %3 percent, UnusedSize %4, Status=%5.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Create Ssd Cache Store partition on device %1 (%2), Reserve %3 percent, UnusedSize %4, Status=%5.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`ReservePercentage`	—
`UnusedSize`	—
`Status`	—

Event ID 257 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`CacheStoreDeviceGuid`	—
`CacheStoreDeviceId`	—
`Attributes`	—
`Status`	—

Event ID 257 — Bind Hdd device %1 (%2) to Cache Store Partition %3 on device %4 (%5), Attributes %6, Status=%7.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Bind Hdd device %1 (%2) to Cache Store Partition %3 on device %4 (%5), Attributes %6, Status=%7.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`CacheStoreDeviceGuid`	—
`CacheStoreDeviceId`	—
`Attributes`	—
`Status`	—

Event ID 258 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Options`	—
`AddedMissingPages`	—
`Status`	—

Event ID 258 — UnBind Hdd device %1 (%2), Options %3, AddedMissingPages=%4, Status=%5.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

UnBind Hdd device %1 (%2), Options %3, AddedMissingPages=%4, Status=%5.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`Options`	—
`AddedMissingPages`	—
`Status`	—

Event ID 259 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`BindingGuid`	—
`HddDeviceGuid`	—
`Status`	—

Event ID 259 — Disable Binding on Sdd device %1 (%2), Partition Id %3, Binding %4, Hdd Device %5, Status=%6.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disable Binding on Sdd device %1 (%2), Partition Id %3, Binding %4, Hdd Device %5, Status=%6.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`BindingGuid`	—
`HddDeviceGuid`	—
`Status`	—

Event ID 260 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`BindingGuid`	—
`HddDeviceGuid`	—
`Attributes`	—
`AttributesMask`	—
`Status`	—

Event ID 260 — Set Binding Attributes on device %1 (%2), Partition Id %3, Binding %4, Hdd Device %5, Attributes(mask) %6(%7), Status=%8.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Set Binding Attributes on device %1 (%2), Partition Id %3, Binding %4, Hdd Device %5, Attributes(mask) %6(%7), Status=%8.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`BindingGuid`	—
`HddDeviceGuid`	—
`Attributes`	—
`AttributesMask`	—
`Status`	—

Event ID 261 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 261 — Disabled Read and Write Cache on Ssd Cache Store partition on device %1 (%2), PartitionId %3 due to IO Error=%4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Disabled Read and Write Cache on Ssd Cache Store partition on device %1 (%2), PartitionId %3 due to IO Error=%4.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 301 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`Function`	—
`LineNumber`	—
`Status`	—

Event ID 301 — Runtime error in %1@%2, Status=%3.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Runtime error in %1@%2, Status=%3.

Fields

Name	Description
`Function`	—
`LineNumber`	—
`Status`	—

Event ID 351 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 351 — Starting to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Starting to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 352 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 352 — Loaded Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Loaded Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 353 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 353 — Failed to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Failed to load Cache Store on device %1 (%2), PartitionId %3, Status=%4.

Fields

Name	Description
`DeviceGuid`	—
`DeviceId`	—
`CacheStorePartitionId`	—
`Status`	—

Event ID 401 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 401 — Data mismatch detected at bottom layer.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Data mismatch detected at bottom layer. Disk %2, io_offset=%3, io_length=%4, mismatch_offset=%5, mismatch_length=%6

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 402 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 402 — Data mismatch detected at top layer.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Data mismatch detected at top layer. Disk %2, io_offset=%3, io_length=%4, mismatch_offset=%5, mismatch_length=%6

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 403 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 403 — Data mismatch detected at standby.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Data mismatch detected at standby. Disk %2, io_offset=%3, io_length=%4, mismatch_offset=%5, mismatch_length=%6

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`MismatchOffset`	—
`MismatchLength`	—

Event ID 404 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`Status`	—
`Informational`	—

Event ID 404 — Bad IO completion at bottom layer.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Bad IO completion at bottom layer. Disk %2, io_offset=%3, io_length=%4, status=%5, informational=%6

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`Status`	—
`Informational`	—

Event ID 405 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`Status`	—
`Informational`	—

Event ID 405 — Bad IO completion at top layer.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Bad IO completion at top layer. Disk %2, io_offset=%3, io_length=%4, status=%5, informational=%6

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`Status`	—
`Informational`	—

Event ID 406 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`ExistingIOOffset`	—
`ExistingIOLength`	—

Event ID 406 — Overlapping IOs detected

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Overlapping IOs detected

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOOffset`	—
`IOLength`	—
`ExistingIOOffset`	—
`ExistingIOLength`	—

Event ID 407 —

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOCTL`	—

Event ID 407 — Prohibited IOCTL was rejected.

Provider: Microsoft-Windows-FailoverClustering-ClusBflt-Diagnostic
Channel: Operational

Message

Prohibited IOCTL was rejected. Disk %2, ioctl=%3

Fields

Name	Description
`DeviceGuid`	—
`DeviceNumber`	—
`IOCTL`	—