WARNING: Please do not use this document if the system is a /usr client, diskless client, or dataless client.
WARNING: Do not use this procedure on an AFS fileserver. Doing so may remove all AFS fileserver data because fsck would be run on the AFS volumes.
The known causes of an LED 551, 555, or 557 during an IPL are:
To diagnose and fix the problem, you will need to boot from bootable media, run logform on /dev/hd8, and run fsck to fix any file systems that may be corrupted.
WARNING: Please do not use this document if the system is a /usr client, diskless client, or dataless client.
WARNING: If you boot a 3.2 system with 3.1 media, or boot a
3.1
system with 3.2 media, then you will not be able to use
the standard scripts (getrootfs or /etc/continue) to
bring your workstation into full maintenance mode.
Moreover, performing the scripts on a 3.1 system with
3.2 boot media may actually remove some files and
prevent your system from booting successfully in normal
mode until missing files (/etc/mount and /etc/umount) are
replaced on the disk.
Follow the prompts to the installation/maintenance menu.
Execute the following command:
getrootfs
The output indicates the disk that should be used with the getrootfs command in the next step.
Execute the following command:
lqueryvg -Atp hdisk# | grep hd5for each hdisk# (hdisk0, hdisk1, etc.) until you get output similar to the following:
00005264feb3631c.2 hd5 1The exact output you get will be different but will follow the form:
large_number.x hd5 1
You may find more than one disk with this output. These will all be disks which belong to the rootvg volume group. Any of the disks identified to be in rootvg may be used in the following step.
For AIX 3.1 only, enter:
/etc/continue hdisk# sh
For AIX 3.2 only, enter:
getrootfs hdisk# sh
If you get errors indicating that a physical volume is missing from the rootvg, run diagnostics on the physical volumes to find out if you have a bad disk. Do not continue with the rest of the steps in this document.
If you get other errors from getrootfs or /etc/continue, do not continue with the rest of the steps in this document. Correct the problem causing the error. If you need assistance correcting the problem causing the error, contact one of the following:
All of the preceding avenues for assistance may be billable.
ODMDIR=/etc/objrepos
For AIX 3.1 only, enter:
/etc/aix/logform /dev/hd8
For AIX 3.2 only, enter:
/usr/sbin/logform /dev/hd8
Answer YES when asked if you want to destroy the log.
fsck -y /dev/hd1 fsck -y /dev/hd2 fsck -y /dev/hd3 fsck -y /dev/hd4For AIX 3.2 only, also enter:
fsck -y /dev/hd9var
In AIX 3.1, enter:
cd /etc/helpers
In AIX 3.2, enter:
cd /sbin/helpers
Then in both AIX 3.1 and 3.2, enter:
ls -l v3fshelper*
If you have only one version of the v3fshelper file (for example, v3fshelper), proceed to step 11.
If there is a version of v3fshelper marked as original (for example, v3fshelper.orig), run the following series of commands:
copy v3fshelper v3fshelper.afs copy v3fshelper.orig v3fshelper
lslv -m hd5WARNING: Please do not proceed further if the system is a /usr client, diskless client, or dataless client.
bosboot -a -d /dev/hdisk# bosboot -u -d /dev/hdisk#
copy v3fshelper.afs v3fshelper
lppchk -c lppchk -v
cfgmgr -v > /tmp/cfgmgr.out 2>&1
shutdown -Fr
If you followed all of the preceding steps and the system still stops at an LED 551, 555, or 557 during a reboot in normal mode, you may want to pursue further system recovery assistance from one of the following:
For reasons of time and the integrity of your AIX operating system, the best alternative at this point may be to reinstall AIX.
[ Doc Ref: 90605189014740 Publish Date: Oct. 12, 2000 4FAX Ref: 1746 ]