How it works
Fault diagnosis
FMA reports diagnosed faults with identifiers and recommended actions.
Do not blindly clear
Clearing a fault without fixing the underlying problem can hide evidence.
Correlation
Combine FMA findings with storage and system logs.
Worked examples
Each example explains the question it answers, a reproducible starting point, what to look for, and operational precautions.
1. List faults
Use this as a starting point for list faults.
fmadm faultyInterpretation: Check command output against the expected host configuration; record the before/after state.
Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.
2. Inspect faults
Use this as a starting point for inspect faults.
fmdump -vInterpretation: Check command output against the expected host configuration; record the before/after state.
Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.
3. Check storage
Use this as a starting point for check storage.
zpool status -vInterpretation: Check command output against the expected host configuration; record the before/after state.
Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.
4. Inspect system messages
Use this as a starting point for inspect system messages.
tail -100 /var/adm/messagesInterpretation: Check command output against the expected host configuration; record the before/after state.
Operational note: Run commands in a test environment first; confirm device names, privileges and release-specific options.
Primary documentation
Read the relevant Oracle documentation for exact version-specific flags, supported platforms and limitations: Oracle primary reference ↗.
This field manual is independent, not affiliated with or endorsed by Oracle. Command examples should be adapted to your environment.