Sometimes, the alert is triggered not by a real failure but by a bug. For example, users of CloudLinux with CageFS enabled reported false-positive health check warnings on cPanel v134 and newer. In this case, the solution was to wait for a patch (e.g., cagefs-7.6.31-1 ) or update your software.
: If the affected disk group contains critical files like the OCR, Voting files, or database data files, the associated Oracle instance or Clusterware may crash. Common Root Causes Lost Storage Connectivity
If the analysis confirms a correctable form of corruption, the most direct solution is to run the CHECK command with the REPAIR clause.
:
flowchart TD A[ASM Alert Log Message<br>"ASM Health Checker found 1 new failures"] --> B(Step 1:<br>Run Diagnostic CHECK) B --> CCheck<br>V$ASM_OPERATION C --> D[Step 2:<br>Generate Health Check Report] D --> E[Step 3:<br>Analyze Failure] E --> FCorruption Found? F -- Yes --> G(Step 4:<br>Execute CHECK ALL REPAIR) G --> H[Step 5:<br>Monitor Rebalance] H --> I[Step 6:<br>Re-validate & Verify] I --> J[Step 7:<br>Document & Prevent] F -- No --> K[False Positive?<br>Engage ASM Team] asm health checker found 1 new failures
The GET_RUN_REPORT output will contain sections like 'Run Findings And Recommendations', which will show the specific failure (e.g., a specific datafile or disk), its priority, and a descriptive message.
: The subsystem encounters a physical or logical I/O read/write error on a disk path.
When this failure hits your system, prioritize stabilization and diagnostic isolation to avoid database downtime.
sqlplus / as sysasm SET LINESIZE 200 COL failure_type FORMAT a30 COL detail FORMAT a60 SELECT failure_id, failure_type, check_name, time_detected, status, detail FROM v$asm_health_check WHERE status = 'FAIL' ORDER BY time_detected DESC; Sometimes, the alert is triggered not by a
Run the health checker in verbose mode to identify exactly which assertion failed.
SQL> select run_id, name, check_name, start_time, end_time, status from v$hm_run;
To investigate the failure, follow these steps:
After fixing the issue, the ASM health checker will automatically re-evaluate within 1 hour (by default). To force an immediate recheck: : If the affected disk group contains critical
If you manage Oracle Grid Infrastructure (GI) or a standalone Automatic Storage Management (ASM) instance, one notification can send a chill down your spine:
If this guide helped you resolve the issue, please share your experience or let others know which specific fix worked for you in the comments below.
Any SAN, multipath, or OS upgrade should trigger a manual health check: