📖 ~1 min read
Table of contents
Symptom & Impact
Reboot after TL update yields 0c31/0c32 LED and won’t boot.
Environment & Reproduction
bosboot was not re-run or bootlist points to wrong disk.
Root Cause Analysis
Boot image on hdisk is stale or missing after fileset change.
Quick Triage
From SMS, boot to maintenance and run ipl_varyon -i.
Step-by-Step Diagnosis
Inspect lslv -m hd5 and bootlist -m normal -o.

Solution – Primary Fix
Run bosboot -ad /dev/hdiskN then bootlist -m normal hdiskN.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Boot from mksysb DVD/NIM to repair if hd5 corrupted.
Verification & Acceptance Criteria
System reboots to multi-user without LED stalls.
Rollback Plan
Restore mksysb if bosboot can’t write a valid image.
Prevention & Hardening
Always run bosboot after kernel/TL changes via NIM script.
Related Errors & Cross-Refs
Pairs with mirrored rootvg failed copy on hd5.
Related tutorial: View the step-by-step tutorial for aix-7.3.
View all aix-7.3 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
IBM Docs: bosboot, bootlist.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.