Hello, after researching, these Events Critical Isolation of the physical disk causing consistency mismatch is detected as the system essentially indicates that there is a data parity mismatch. The system corrects itself (rebuilds the disks) when encountering an anomaly. This error can occur after recovering from a failed disk pool/virtual disk. If the drives belong to a recovered disk pool or disk group, it is recommended that you perform a full backup of the affected disk pool or disk group, restore, and restore the data. This error can occur when outdated data is entered on the virtual disk.  I found two similar threads please take a look at them.  [URL] [URL]   But I feel this may be the case for IPS and PSE engineers to look into. So if the solution in these forums doesn't work, you may need to register with the local support team and have a product support engineer review it. In other words, there may be a situation above the L3 level. Because I can't see a workaround or explanation directly related to this event.
We have an MD3200i with 12 x 10TB SAS drives installed with 11 in a RAID6 config and the 12th as hot spare. Yesterday, two drives were showing as "Failed" and after reseating the drives and reviving, they both came back online and the RAID state changed to Optimal after copyback finished. Today, I'm noticing thousands of instances of the following error: - Event type: 2046Event category: InternalPriority: CriticalEvent needs attention: trueEvent send alert: trueEvent visibility: trueDescription: Isolation of physical disk causing consistency mismatchEvent specific codes: 0/0/0Component type: Physical DiskComponent location: Enclosure 0, Slot 3Logged by: RAID Controller Module in slot 0 The RAID is still showing as optimal yet I've seen numerous corrupted files and folders, many of which cannot be deleted. Note: The disk at 0, 3 is one of the two that failed and was revived. There are no errors for the other revived disk.  
Isolation of physical disk causing consistency mismatch on MD3200i