This document applies to AIX Versions 3.1 or 3.2.
An LED 553 occurs during an IPL if the system cannot read or run the /etc/inittab file. On early releases, this could occur when the /tmp or / (root) file system is full. On level 2004 and beyond, the cause is more likely to be a missing /bin/bsh file or a problem with one of the shell profiles.
To recover from an LED 553, check /dev/hd3 and /dev/hd4 for space problems, and erase files if necessary. Check the /etc/inittab file for corruption, and fix it if necessary. If the inittab file was not corrupted, you will need to check the shell profiles, the /bin/bsh file, and some other files.
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:
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:
For AIX 3.2 only, enter:
If you get errors from /etc/continue or getrootfs, do not continue with this procedure. 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.
df /dev/hd3 df /dev/hd4
TERM=[xxx] export TERM
Now use an editor to create the /etc/inittab file. For an example, see the section "Sample /etc/inittab file for AIX 3.2" at the end of this document. If your /etc/inittab file was corrupt and you recreated it, you may not need to perform any of the following steps.
ls -al /.profile /etc/environment /etc/profileSample output:
-rw-r--r-- 1 root system 158 Dec 14 1993 /.profile -rw-rw-r-- 1 root system 1389 Oct 26 1993 /etc/environment -rw-r--r-- 1 root system 1214 Jan 22 1993 /etc/profile
One of the preceding files may contain a command that is valid only in the Korn shell. Change the command to something that is also valid in the Bourne shell. For example, change
PATH=/bin:/usr/bin/:/etc:/usr/ucb:. export PATH
Make sure the following files and directory are not missing or moved.
/bin/sh /bin/bsh /bin
Check for missing or moved files with the following command:
ls -al /bin /bin/bsh /bin/sh /bootrec /lib /u /unixSample output:
lrwxrwxrwx 1 root sys 8 Aug 5 1994 /bin -> /usr/bin -r-xr-xr-x 3 bin bin 256224 Jun 4 1993 /bin/bsh -r-xr-xr-x 3 bin bin 256224 Jun 4 1993 /bin/sh lrwxrwxrwx 1 root sys 17 Aug 5 1994 /bootrec -> /usr/sbin/bootrec lrwxrwxrwx 1 root sys 8 Aug 5 1994 /lib -> /usr/lib lrwxrwxrwx 1 root sys 5 Aug 5 1994 /u -> /home lrwxrwxrwx 1 root sys 18 Aug 5 1994 /unix -> /usr/lib/boot/unix
If any of the preceding files are missing, the problem may be a missing symbolic link. Use the commands from the list below that correspond to the missing links:
ln -s /usr/bin /bin ln -s /usr/lib/boot/unix /unix ln -s /usr/sbin/bootrec /bootrec ln -s /usr/lib /lib ln -s /home /u
Make sure the following are not missing or corrupt.
Use the following command to make sure that fsck and rc.boot are not missing or corrupt:
ls -l /etc/fsck /sbin/rc.bootSample output:
lrwxrwxrwx 1 root system 14 Aug 5 1994 /etc/fsck -> /usr/sbin/fsck -rwxrwxr-- 1 root system 33760 Aug 30 1993 /sbin/rc.boot
brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1For AIX 3.1, the line reads:
brc::sysinit:/etc/brc >/dev/console 2>&1
See the section "Sample /etc/inittab file for AIX 3.2" at the end of this document for an example.
cp /bin/bsh /bin/bsh.orig cp /bin/ksh /bin/bsh
If you can then reboot successfully, this indicates that one of the profiles was causing problems for bsh. Check the profiles again by running the following:
/bin/bsh.orig /.profile /bin/bsh.orig /etc/profile /bin/bsh.orig /etc/environmentIf you receive errors with any of the preceding commands, this indicates there is a command in that profile that bsh cannot handle.
If you followed all of the preceding steps and the system still stops at an LED 553 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.
: @(#)49 1.28 com/cfg/etc/inittab, bos, bos320 10/3/91 10:46:51 : COMPONENT_NAME: CFGETC init:2:initdefault: brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot powerfail::powerfail:/etc/rc.powerfail 2>&1 | alog -tboot > /dev/console rc:2:wait:/etc/rc > alog -tboot > /dev/console 2>&1 # Multi-User checks fbcheck:2:wait:/usr/lib/dwm/fbcheck > alog -tboot >/dev/console 2>&1 srcmstr:2:respawn:/etc/srcmstr # System Resource Controller rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2> &1 # Start TCP/IP daemons rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons cron:2:respawn:/etc/cron cons:0123456789:respawn:/etc/getty /dev/console piobe:2:wait:/usr/lib/lpd/pio/etc/pioinit > /dev/null 2>&1 # pb cleanup qdaemon:2:wait:/bin/startsrc -sqdaemon writesrv:2:wait:/bin/startsrc -swritesrv uprintfd:2:respawn:/usr/sbin/uprintfd dt:2:wait:/etc/rc.dt
[ Doc Ref: 90605189414748 Publish Date: Oct. 13, 2000 4FAX Ref: 1721 ]