Unsolved
2 Posts
0
945
March 15th, 2023 11:00
Isolation of physical disk causing consistency mismatch on MD3200i
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: 2046
Event category: Internal
Priority: Critical
Event needs attention: true
Event send alert: true
Event visibility: true
Description: Isolation of physical disk causing consistency mismatch
Event specific codes: 0/0/0
Component type: Physical Disk
Component location: Enclosure 0, Slot 3
Logged 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.
DELL-Erman O
Moderator
•
2.9K Posts
0
March 16th, 2023 02:00
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.
https://dell.to/3mNLXl8
https://dell.to/3yG8a7F
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.
hamzazuberi
2 Posts
0
March 16th, 2023 04:00
@Dell-ErmanO thanks for the response! Yes, I had a look at these threads before posting my question since they didn't really offer a relevant solution for my specific case. I'm pretty sure the data has been mostly corrupted, so I will be formatting the affected mapped volumes. Do you think replacing the physical disk at slot 0,3 will resolve the inconsistency or would you recommend we remove and recreate the entire RAID volume.
DELL-Erman O
Moderator
•
2.9K Posts
0
March 16th, 2023 06:00
Honestly, I'm thinking on that and when using background-scanning media with redundancy checking enabled, the controller performs a parity-checking in the background. If one drive is causing a data parity mismatch (DPM), can isolate and recover it. In this case, the parity mismatch cannot be corrected. This is a sign of data corruption, I think. I would consider the last option to wipe and recreate the configuration and restore the data if the backup (if available).