If a disk group reaches near-total capacity (e.g., 99% full) or a failure group violates redundancy requirements (e.g., missing mirrored extents), the health checker can classify this as a configuration failure.
AI Mode history New thread AI Mode history You're signed out To access history and more, sign in to your account Manage public links See my AI Mode history Shared public links
Apply the latest Oracle Grid Infrastructure patches. Oracle frequently releases fixes for ASM bugs that could otherwise lead to disk group corruption. asm health checker found 1 new failures updated
Bad blocks on physical storage devices are another common cause. Even if the storage appears healthy at a high level, individual blocks can become corrupted due to:
The disk group is normal; the issue might be confined to a single disk. If a disk group reaches near-total capacity (e
This command allows Oracle ASM to automatically fix any errors it can, such as correcting broken metadata pointers or updating stale allocation tables. In practice, executing this command often resolves the alert entirely.
The REPAIR clause instructs Oracle ASM to automatically fix any inconsistencies found during the check process. After running this command, the alert will be resolved, and the disk group will be consistent. Bad blocks on physical storage devices are another
This message comes from , typically when you run:
ls -la /dev/oracleasm/disks/ # or ls -la /dev/mapper/