Asm Health Checker Found 1 New Failures Hot! May 2026

ASM Health Checker Found 1 New Failures

Summary

ASM Health Checker detected one new failure in your environment. This post explains what that means, likely causes, immediate checks you should run, step-by-step troubleshooting, and recommended fixes to restore full health.

if len(new_failures) > 0: send_alert( title="ASM Health Checker found 1 new failure", details=list(new_failures), count=len(new_failures) ) else: log.info("No new ASM failures detected")
  1. Replace a failed disk: If the failure is due to a disk error, replace the disk and re-add it to the ASM disk group.
  2. Check and correct connectivity: Verify that the storage connections are stable and functioning correctly.
  3. Free up disk space: If the failure is due to insufficient disk space, free up space by deleting unnecessary files or expanding the disk group.
  4. Reconfigure ASM: If the failure is due to an ASM configuration error, reconfigure ASM with the correct settings.

Suspected Root Causes

Based on standard ASM operational patterns, the failure is likely attributed to one of the following scenarios: asm health checker found 1 new failures

3. ASM Metadata Corruption

Rare, but serious. Corruption in the file directory (KFD) or allocation tables can cause "stale metadata" errors. Often seen after abnormal cluster shutdowns. ASM Health Checker Found 1 New Failures Summary

Check the Alert Log: Locate the exact timestamp of the error in the ASM alert log. Look for preceding errors like ORA-15130 (diskgroup being dismounted) or specific path-related I/O errors. For storage/ASM, degraded redundancy increases risk of data

Immediate actions (first 10 minutes)

  1. Don’t panic — gather context.
  2. Check the Health Checker details/console immediately for: