
OPERATIONAL DEFECT DATABASE
...


...

The following message may appear in the MC UI "Event Management" tab on an Avamar Gen4S node: <MRMON063> Controller ID: 0 Consistency Check found inconsistent parity on VD#nnn strip: #nnn ( VD = n, strip#nnn = xxxxxxxx)
Possible causes: If the Logical Units (LUNs) were not fully initialized at the factory, the first Consistency Check may fail. The node has been replaced with disk transplant. One of the physical disks within a virtual disk (VD) experienced some hardware problems.
1. Log in to the node as admin. 2. Verify if the message has been reported during single of multiple consistency checks: grep MRMON063 /var/log/messages bzcat /var/log/messages*.bz2 | grep MRMON063 xzcat /var/log/messages*.xz | grep MRMON063 MRMON063 events can be ignored if seen only once per Virtual Disk after installation or node replacement. If the messages are seen more than once, Create a Service Request for assistance from the Dell Technologies Avamar Support team.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.