Asm Health Checker Found 1 New Failures May 2026
If dd fails with "Input/output error", the disk is physically failing. Scenario A: Offline Disk (Most Common) Error example: Disk DATA_0001 is offline
ALTER DISKGROUP DATA SET ATTRIBUTE 'compatible.asm' = '12.2'; After fixing the issue, the ASM health checker will automatically re-evaluate within 1 hour (by default). To force an immediate recheck: asm health checker found 1 new failures
If you manage Oracle Grid Infrastructure (GI) or a standalone Automatic Storage Management (ASM) instance, one notification can send a chill down your spine: "ASM health checker found 1 new failures." If dd fails with "Input/output error", the disk
This message, often found in your alert log, crsd.log , or email alerts from Enterprise Manager (EM12c/13c), indicates that the automated ASM Health Checker has detected a new issue affecting the integrity, availability, or performance of your ASM environment. Ignoring it is not an option; unresolved failures can lead to disk group mount issues, I/O latency, or even database crashes. Ignoring it is not an option; unresolved failures
/sbin/udevadm trigger --subsystem-match=block Error example: Check: Metadata Consistency, Status: FAIL, Detail: Orphaned file directory entry
chown grid:asmadmin /dev/sdg chmod 660 /dev/sdg -- If persistent across reboot, fix udev rules: vi /etc/udev/rules.d/99-oracle-asm.rules -- Add: KERNEL=="sdg", OWNER="grid", GROUP="asmadmin", MODE="0660" Then restart the ASM instance or reload udev:
To the failure from the persistent repository (without waiting for auto-clear):
