📖 ~1 min read
Table of contents
Symptom & Impact
Server stops at LED 553 or 581 during boot and does not reach login.
Environment & Reproduction
After bosboot, rootvg disk replacement, or interrupted update.
bootlist -m normal -o
bosboot -ad /dev/hdisk0
shutdown -Fr
Root Cause Analysis
Bootlist points to a disk without a valid boot image or /etc/inittab is corrupt.
Quick Triage
Boot from maintenance media and inspect rootvg.
bootlist -m normal -o
lspv
check via SMS or HMC
Step-by-Step Diagnosis
Mount rootvg in maintenance mode and inspect /etc/inittab and /sbin/rc.boot.
getrootfs hdisk0
cat /etc/inittab
ls /sbin/rc.boot

Solution – Primary Fix
Rebuild the boot image and correct /etc/inittab, then update bootlist.
Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.
bosboot -ad /dev/hdisk0
bootlist -m normal hdisk0 hdisk1
shutdown -Fr

Solution – Alternative Approaches
Boot an alternate disk created by alt_disk_install or restore mksysb to recover.
Verification & Acceptance Criteria
System completes boot to runlevel 2 and lpp services start.
who -r
lssrc -a | head
errpt | head
Rollback Plan
Boot from a previous bootlist entry or alt_disk while the issue is fully resolved.
bootlist -m normal -o
bootlist -m normal hdisk1
shutdown -Fr
Prevention & Hardening
Maintain mirrored rootvg, regular mksysb, and run bosboot after critical updates.
Related Errors & Cross-Refs
Related to LVM SA quorum loss, JFS2 superblock errors, and update_all failures.
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 AIX 7.3 boot recovery and SMS reference.
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.