Booting Problems

Generally, if you encounter a problem in the booting process, you see a three-digit
display value. This section describes these common display values and what you can do
about them. If you need to access a system that does not boot from the hard disk, see
Accessing a System That Will Not Boot.
For more values related to booting problems, see List of Three-Digit Display Values:
500-599.
Find the three-digit display value in the following and go to the appropriate recovery
location:
Display Value Recovery Location
201 Display Value 201
223 through 229 and Display Value 223-
xxx- xxx 229 and xxx-xxx
Display Values 551,
551, 555, and 557
555, and 557
Display Values 552,
552, 554, and 556
554, and 556
553 Display Value 553
c31 Display Value c31
c99 Display Value c99
Note: You must have root user authority to perform any of the following
procedures.

Display Value 201

If the system stops at 201 during the boot process, the problem may be either a software
problem or a hardware problem.
If the display first goes past 299, and then back to 201, it is most likely a damaged boot
image.
If the display never gets to 299, it is not a software problem because the boot process
hasn't loaded any software yet.
Did the system display a value of 299 or greater before displaying 201?
Yes Go to Rebuilding the Boot Image.
No Go to Hardware Problems.
Rebuilding the Boot Image
To rebuild a boot image, perform the following:
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Will Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group. This
allows access to the file systems in the volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Enter the following to check the free column:
df /dev/hd3
df /dev/hd4
If the free column for either /dev/hd3 or /dev/hd4 is less than 1000, erase some files
from that file system (such as /smit.log, /smit.script, core files in / or /tmp and/or any
subdirectories of these file systems that are not separate mount points, such as /etc, /dev,
and user created directories.
Also, check for any large files in the /dev directory. Large file can end up in /dev as a
result of a mistyped command (such as backup, tar, or dd).
Determine which disk is the boot disk with the lslv command. The boot disk will be
shown in the PV1 column of the lslv output.
lslv -m hd5
Recreate the boot image.
bosboot -a -d /dev/hdisk#
Where hdisk# is the boot disk.
To see if there are any CHECKSTOPs in the error log, generate an error report. For
example:
errpt -a | grep CHECKSTOP
The errpt command processes a report of logged errors. This example generates a
 report of just the CHECKSTOP errors. If you get output of the form:
LABEL: CHECKSTOP
Contact your hardware support organization for assistance.
Place the key mode switch in the Normal position, shut down, and reboot the system.
For example:
shutdown -Fr
The shutdown command ends system operation. The previous example performs
a fast shutdown, bypassing the messages to other users and bringing down the
system as quickly as possible. Then, it restarts the system.
Did this solve the problem?
Yes Stop.
If the LED is different than 201, go back to the display values in Booting Problems .
No If the LED is the same (201), complete the Problem Summary Form and report the
problem to your hardware service organization.
Hardware Problems
The display value 201 may be due to a hardware problem with the system planar.
Usually, the error log contains an entry for the checkstop. You must turn your system off
and then back on again before you reboot.
Note: When a machine checkstops, the machine will try to reboot itself. If the
reboot is unsuccessful, the system will attempt to reboot itself two more times. If
each subsequent reboot is unsuccessful, the machine will stop with the value 201
in the operator display panel. If this occurs, contact your service representative for
assistance.
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Will Not Boot for more information.
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group. This
allows access to the file systems in the volume group. Go to step 6.
 Otherwise, select 99 to display the list of volume groups and go to step 4.
To see if there are any CHECKSTOPs in the error log, generate an error report. For
example:
errpt -a | grep CHECKSTOP
The errpt command processes a report of logged errors. This example generates a
report of just the CHECKSTOP errors. If you get output of the form:
LABEL: CHECKSTOP
Contact you hardware support organization for assistance.

Display Values 223-229 and xxx-xxx

If the system cycles display values (the display changes from 223 to 229 to 223 and so
on), the IPL list in nonvolatile random access memory (NVRAM) is incorrect. It is most
likely pointing to a device without a boot record, or the device is unavailable.
Note: This procedure also applies to alternating display values 221-229, 225-229,
233-235 and solid display values 221 and 721.
Reboot your machine with the key mode switch in the Service position.
If the display sequence continues normally, change the key mode switch back to the
Normal position after the display value reaches 299.
If you get to a login prompt, login as root and go to step 6 in Modify the Boot
List.
If the display sequence continues to flash between 223 and 229, go to step 3 of
this section.
shutdown -Fr
Check that all external devices are properly attached. Change cables if necessary.
Did this solve the problem?
Yes Stop.
No Go to Modify the Boot List.
Modify the Boot List
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Will Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
 system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group. This
allows access to the file systems in the volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Determine which disk is the boot disk by entering the lslv command. The boot disk is
show in the PV1 column of the lslv output. For example:
lslv -m hd5
Now use the bootlist command to set the bootlist. For example:
bootlist -m normal hdisk#
Where hdisk# is the boot disk.
The bootlist command alters the list of boot devices (or ordering of the devices)
available to the system.
Place the key mode switch in the Normal position, shut down and reboot the system:
shutdown -Fr
The shutdown command ends system operation. This example does a f ast
shutdown, bypassing the messages to other users and bringing down the system as
quickly as possible, and then restarts the system.
Did this solve the problem?
Yes Stop.
No Go back to the Hardware Diagnostics in in AIX Problem Solving Guide and Reference.

Display Values 551, 555, and 557

If the boot process halts with a display value of 551, 555, or 557, there may be several
causes, such as a corrupted file system, a corrupted journaled-file-system (JFS) log
device, or a bad disk in the machine that is a member of the rootvg. Use the following
steps to determine the problem area.
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Does Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
 system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 2 to access the volume group and start a
shell, before mounting file systems. This allows access to the file systems in the
volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Enter the following:
fsck -y /dev/hd1
fsck -y /dev/hd2
fsck -y /dev/hd3
fsck -y /dev/hd4
fsck -y /dev/hd9var
The fsck command checks file system consistency and interactively repairs the
file system.
Enter the following to format the default jfslog for the rootvg jfs file systems:
/usr/sbin/logform /dev/hd8
Type exit to continue the process of accessing the root volume group and mount the
file systems.
Enter the lslv command to determine which disk is the boot disk. The boot disk will
be shown in the PV1 column of the lslv output.
lslv -m hd5
Enter the following to recreate the boot image.
bosboot -a -d /dev/hdisk#
Where # is the boot disk.
Did this solve the problem?
Ye
Stop.
s
For reasons of time and the integrity of your AIX operating system, reinstall AIX from either
No
a mksyb tape or an install tape.

Display Values 552, 554, and 556

The main symptom for the 552, 554 or 556 display values is a loop displaying the
respective display value. To correct this problem, perform the steps that follow to clean
up file systems and to check the log volume.
With the key mode switch in the Service position, boot from your installation media.
 See Accessing a System That Does Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 2 to access the volume group and start a
shell, before mounting file systems. This allows access to the file systems in the
volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Run the fsck command on the following file systems:
fsck -y /dev/hd1
fsck -y /dev/hd2
fsck -y /dev/hd3
fsck -y /dev/hd4
fsck -y /dev/hd9var
The fsck command checks file system consistency and interactively repairs the
file system.
If fsck indicates that block 8 could not be read, the file system is probably
unrecoverable. (The easiest way to fix an unrecoverable file system is to delete
the file system from the system and restore it from a backup. Note that hd4 cannot
be recreated. If hd4 is unrecoverable, you must reinstall AIX.)
If fsck indicates that block 8 could be read but one of the following errors is
given:
fsck: Not an AIXV4 file system
fsck: Not a recognized file system type
Repair the file system by entering:
dd count=1 bs=4k skip=31 seek=1 if=/dev/hd# of=/dev/hd#
Where hd# is the file system.
If errors are indicated from any of the fsck commands in step 6, go to step 8. If no
errors occur, go to step 9.
Run the following command:
/usr/sbin/logform /dev/hd8
The system asks you if you want to destroy your log. The answer should be yes.
 logform reformats the log logical volume.
Type exit to continue the process of accessing the root volume group and mount the
file systems.
Reboot your machine with the key mode switch in the Normal position.
Did this solve the problem?
Yes Stop.
No Go to Rebuild the ODM
Rebuild the ODM
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Does Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 2 to access the volume group and start a
shell, before mounting file systems. This allows access to the file systems in the
volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Mount the /dev/hd4 and /usr file systems. (/dev/hd4 is being mounted in a temporary
location for maintenance purposes.)
mount /dev/hd4 /mnt
mount /usr
Copy the system configuration to a backup directory:
mkdir /mnt/etc/objrepos/backup
cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup
Copy the configuration from RAM:
cp /etc/objrepos/Cu* /mnt/etc/objrepos
Unmount the file system (include the path for the unmount command).
cd /etc/umount all
Note: An error messages might occur indicating that the system is
 not able to unmount /dev/ram0.
Enter exit to exit from the shell. The file systems will automatically mount after you
enter exit.
Enter the lslv command to determine which disk is the boot disk. The boot disk will
be shown in the PV1 column of the lslv output.
lslv -m hd5
Enter the following to save the clean ODM database to the boot logical volume:
savebase -d /dev/hdisk#
Where hdisk# is the boot disk.
Reboot your machine with the key mode switch in the Normal position.
Did this solve the problem?
Ye
Stop.
s
For reasons of time and the integrity of your AIX operating system, reinstall AIX from either
No
a mksyb tape or an install tape.

Display Value 553

If the system stops at display value 553 during boot, it may be due to a problem running
or reading the /etc/inittab file. This often occurs when the /tmp, /usr or / (root) file
systems are full. If your default shell is missing (such as /bin/sh), the system might also
stop at display value 553.
Perform the following steps:
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Does Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group. This
allows access to the file systems in the volume group. Go to step 6.
Otherwise, select 99 to display the list of volume groups and go to step 4.
Check for free space in /dev/hd2, /dev/hd3, and /dev/hd4 by entering:
df /dev/hd2
OR
df /dev/hd3
OR
df /dev/hd4
If df indicates that any of the file systems is out space, three files you could remove
include /smit.log,/smit.script, and /.sh_history.
Check the /etc/inittab file for damage. Problems include:

•/etc/inittab may be empty.

•/etc/inittab may be missing.

•/etc/inittab may have an entry in it that is not correct.

The /etc/inittab file controls the initialization process. The following is a sample
/etc/inittab file:
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 # Power Failure Detection
rc:2:wait:/etc/rc 2>&1 | alog -tboot > /dev/console
# Multi-User checks
fbcheck:2:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot
> /dev/console # run /etc/fi
rstboot
srcmstr:2:respawn:/usr/sbin/srcmstr # System Resource Controller
rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP
daemons
lafs:2:once:/usr/vice/etc/lafs
rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons
install_assist:2:wait:/usr/sbin/install_assist </dev/console
>/dev/console 2>&1
cons:0123456789:respawn:/usr/sbin/getty /dev/console
cron:2:respawn:/usr/sbin/cron
qdaemon:2:wait:/usr/bin/startsrc -sqdaemon
writesrv:2:wait:/usr/bin/startsrc -swritesrv
uprintfd:2:respawn:/usr/sbin/uprintfd
lft:2:respawn:/usr/sbin/getty /dev/lft0
If the /etc/inittab file is damaged, create it again.
Set your TERM environment variable. For example:
TERM=lft
export TERM
Create the /etc/inittab file using your preferred editor.
 If the /etc/inittab file is not damaged, check for modification or permission problems
with the following files:

•/etc/environment

•/bin/sh

•/bin/bsh

•/etc/fsck (This file may be missing or damaged. Make a copy from the RAM
file system.)

•/etc/profile

•/.profile
Reboot your machine with the key mode switch in the Normal position. For example:
shutdown -Fr
The shutdown command ends system operation. This example does a fast
shutdown, bypassing the messages to other users and bringing down the system as
quickly as possible. Then, it restarts the system.
Did this solve the problem?
Ye
Stop.
s
For reasons of time and the integrity of your AIX operating system, reinstall AIX from either
No
a mksyb tape or an install tape.

Display Value c31

If the system stops at display value c31, look for a message to select your console. The
system cannot locate the system console if the console device is defined but not enabled
or the console is a tty that cannot be reached. This error also occurs if a non-terminal
device (such as a plug, modem, or printer) is plugged into S1 or S2.
Check for loose asynchronous cables.
Check for a non-terminal device (such as a wrap plug, a modem, or a printer) plugged
into S1 or S2; if you find one, remove it.
If you find loose asynchronous cables or a non-terminal device in S1 or S2, reboot
the machine with the key in the Normal position.
If you still get display value c3 after the reboot, continue with step 3.

With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Does Not Boot for more information .
 Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group and start a
shell. This allows access to the file systems in the volume group. Go to step 8.
Otherwise, select 99 to display the list of volume groups and go to step 6.
Enable the console. For example:
chcons -a login=enable /dev/lft/0
The chcons command redirects the system to a specified device or file to be
effective on the next start of the system. This example changes the system console
to the physical LFT display associated with the /dev/lft/0 device and ensures
a login at the console.
With the key mode switch in the Normal position, reboot your system.
Did this solve the problem?
Ye
Stop.
s
For reasons of time and the integrity of your AIX operating system, reinstall AIX from either
No
a mksyb tape or an install tape.

Display Value c99

If the system stops at display value c99 while booting, it may be due to a problem
running or reading the /usr/bin/odmget command. This could be caused by a missing
/usr file system or a corrupted /etc/filesystems file.
Perform the following steps:
With the key mode switch in the Service position, boot from your installation media.
See Accessing a System That Does Not Boot for more information .
Select Maintenance from the Installation menu.
Select the option to access a volume group from the Maintenance menu.
Note: Once you select this option, you cannot return to the
 Installation menu or Maintenance menu without rebooting the
system.
Select the volume group you believe to be the root volume group. An information
screen displays the list of logical volumes that belong to the volume group you
selected. The root volume group usually includes logical volumes hd2 and hd4.
If you selected the root volume group, select 1 to access the volume group. This
allows access to the file systems in the volume group. Go to step 6.
Check the /etc/filesystems file to make sure it contains a stanza for the /usr file
system.
Enter the df command to make sure/usr is mounted. For example:
df /usr
Sample output:
Filesystem Total KB free %used iused %iused
Mounted on
/dev/hd2 405504 12756 96% 28877 28% /usr
If /usr is not found, you need to mount /usr.
If /usr is found, continue with step 8.
Check for the existence of the /usr/bin directory by trying to change to that directory:
cd /usr/bin
If the command fails, /usr/bin needs to be restored.
If the command is successful, continue with step 9.
Check for the existence of the /usr/bin/odmget file with the following command:
ls -l /usr/bin/odmget
If there is no odmget file, then check to see if other files are missing from /usr/bin.
To find out how many files you have in /usr/bin, type:
ls -l | grep -c 1
Restore missing files if possible.
Were you able to restore the files?
Ye
Stop.
s
For reasons of time and the integrity of your AIX operating system, reinstall AIX from either
No
a mksyb tape or an install tape.
888 in the Three-Digit Display
A flashing 888 in the three-digit display indicates that a message is encoded as a string of
three-digit display values. Obtain the display values to record on the Problem Summary
Form by performing the procedures for the following:

•Three-Digit Display Values

•System Halts (Type 102)

•Dump Status Three-Digit Display Values

•Diagnostic Messages

Three-Digit Display Values

Obtain the string of three-digit display values by performing the following procedures:
Turn the key mode switch to the Normal position.
Press the Reset button to display the next value in the string.
Note: Every time you press the Reset button, hold it for about 1
second to allow the system to sense the change.
Record this value in item 5 of the Problem Summary Form.
Repeat steps 2 and 3 until a flashing 888 is displayed again. Up to 30 three-digit
display values may be included in the string.
To display the entire string of values again, repeat this procedure.
The first value following the 888 indicates the type of information contained in the
remainder of the string. If the value is 102, go to "System Halts." For any value other
than 102, go to "Diagnostic Messages" .

System Halts (Type 102)

For unexpected system halts, the string of three-digit values has the following format:
888 102 mmm ddd
An initial value of 102 indicates that an unexpected system halt occurred during normal
operations. The value of the mmm variable indicates the cause of the halt, and the ddd
value indicates whether your system completed a system dump. If the mmm value is 300,
400, or 700, go to "Dump Status Three-Digit Display Values" .

For further information on system halts, refer to "Hardware Diagnostics" in in AIX

Problem Solving Guide and Reference. If the diagnostic programs return a service request
number (SRN), record this number on item 4 on the Problem Summary Form.
The following list gives the possible values of mmm, the first value following the 888,
and the cause of the system halt starting that value:
00
Unexpected system interrupt.
0
20
Machine check due to memory bus error (RAS/CAS parity).
0
20
Machine check due to memory time out.
1
20
Machine check due to memory card failure.
2
20
Machine check due to address exception: address out of range.
3
20
Machine check due to attempted store into ROM.
4
20
Machine check due to uncorrectable error correction code due to address parity.
5
20
Machine check due to uncorrectable error correction code.
6
20
Machine check due to undefined error.
7
20
Machine check due to an L2 uncorrectable ECC.
8
30
Data storage interrupt: processor type.
0
32 Data storage interrupt: input/output exception&mdash;input/output channel controller. The
x number represented by x is the bus unit identification.
38 Data storage interrupt: input/output exception&mdash;serial link adapter. The number
x represented by x is the bus unit identification.
40
Instruction storage interrupt.
0
External interrupt: scrub&mdash;memory bus error (RAS/CAS parity).
50
External interrupt: direct memory access&mdash;memory bus error (RAS/CAS parity).
0
External interrupt: undefined error.
 External interrupt: input/output channel controller type&mdash;channel check.

52 External interrupt: input/output channel controller type&mdash;bus time out.

x External interrupt: input/output channel controller type&mdash;keyboard external.

The number represented by x is the input/output channel controller number.

53
External interrupt because of an IOCC bus timeout; x represents the I/O bus number.
x
54
External interrupt because of an IOCC keyboard check.
x
70
Program interrupt.
0
80
Floating point unavailable.
0

Dump Status Three-Digit Display Values

The value of ddd (the second value following the 888) indicates the dump status. If any
of the ddd value descriptions lead you to another step, return to "Diagnostic Messages" .
The possible values and meanings of ddd are:
The kernel debugger is started. If there is an ASCII terminal attached to one of the native
serial ports, enter q dump at the debugger prompt (>) on that terminal and then wait for
000
flashing 888s to appear in the three-digit display. After the flashing 888 appears, go to
"System Dump Facility" in in AIX Problem Solving Guide and Reference.
The dump completed successfully. To retrieve the dump, go to "System Dump Facility"
0c0
in in AIX Problem Solving Guide and Reference.

An I/O error occurred during the dump. A partial dump was written to the dump device.
0c1 To retrieve the partial dump, go to "System Dump Facility" in in AIX Problem Solving
Guide and Reference.

0c2 A user-requested dump is in progress. Wait at least 1 minute for the dump to complete
and for the three-digit display value to change. If the three-digit display value changes,
find the new value on this list. If the value does not change, then the dump did not
complete due to an unexpected error. Complete the Problem Summary Form, and report
the problem to your software service department.

0c4 The dump did not complete successfully. A partial dump was written to the dump device.
 There is not enough space on the dump device to contain the entire dump. To prevent this
problem from occurring again, you must increase the size of your dump media. Go to
"System Dump Facility" in in AIX Problem Solving Guide and Reference.

A system-initiated or user-requested dump did not complete. To retrieve the system

dump, which may be a partial dump, go to "System Dump Facility" in in AIX Problem
0c5
Solving Guide and Reference. Complete the Problem Summary Form, and report the
problem to your software service department.
A network dump is in progress, and the host is waiting for the server to respond. The
value in the three-digit display should alternate between 0c7 and 0c2 or 0c9. If the
0c7 value does not change, then the dump did not complete due to an unexpected error.
Complete the Problem Summary Form, and report the problem to your software service
department.
The dump device has been disabled. The current system configuration does not designate
0c8 a device for the requested dump. Enter the sysdumpdev command to configure the dump
device.
A system-initiated dump has started. Wait at least 1 minute for the dump to complete and
for the three-digit display value to change. If the three-digit display value changes, find
0c9 the new value on the list. If the value does not change, then the dump did not complete
due to an unexpected error. Complete the Problem Summary Form and report the
problem to your software service department.
(For AIX 4.2.1 and later).An error occured dumping to the primary device; we've
switched over to the secondary device. Wait at least 1 minute for the dump to complete
and for the three-digit display value to change. If the three-digit display value changes,
Occ
find the new value on this list. If the value does not change, then the dump did not
complete due to an unexpected error. Complete the Problem Summary Form, and report
the problem to your software service department.
The kernel debugger exited without a request for a system dump. Enter the quit dump
c20
subcommand. Read the new three-digit value from the LED display.

Diagnostic Messages
An initial value other than 102 indicates a diagnostic message. Diagnostic messages
display in the three-digit display when the console display is not present or is unavailable
because of a display or adapter failure, or when a failure is detected that prevents the
completion of a system restart.

 If your system is hanging at LED 517 or 518 during a Normal mode boot, it is possible the /etc/filesystems file is corrupt or missing. To
temporarily replace the disk-based /etc/filesystems file, run the following commands:
mount /dev/hd4 /mnt
mv /mnt/etc/filesystems /mnt/etc/filesystems.[MMDDYY]
 cp /etc/filesystems /mnt/etc/filesystems
umount /mnt
MMDDYY represents the current two-digit representation of the Month, Day and Year, respectively.

Type exit to exit from the shell. The file systems should automatically mount after you type exit. If you receive error messages, reboot into a
limited function maintenance shell again to attempt to address the failure causes.

If you have user-created file systems in the rootvg volume group, run fsck on them now. Enter:
fsck /dev/[LVname]
LVname is the name of your user-defined logical volume.

If you used the preceding procedure to temporarily replace the /etc/filesystems file, and you have user-created file systems in the rootvg
volume group, you must also run the following command:
imfs -l /dev/[LVname]

If you have file systems in a volume group other than rootvg, run fsck on them now. Enter:
varyonvg [VGname]
fsck /dev/[LVname]
VGname is the name of your user-defined volume group.

If you used the preceding procedure to temporarily replace the /etc/filesystems file, also run the following command:
imfs [VGname]
The preceding commands can be repeated for each user-defined volume group on the system.

If your system was hanging at LED 517 or 518 and you are unable to activate non-rootvg volume groups in Service mode, you can manually
edit the /etc/filesystems file and add the appropriate entries.
The file /etc/filesystems.MMDDYY saved in the preceding steps may be used as a reference if it is readable. However, the imfs method is
preferred since it uses information stored in the logical volume control block to re-populate the /etc/filesystems file.

If your system has a mode select key, turn it to the Normal position.

Reboot the system into Normal mode using the following command:
sync;sync;sync;reboot
If you followed all of the preceding steps and the system still stops at an LED 517 or 518 during a reboot in Normal mode, you may want to
consider reinstalling your system from a recent backup. Isolating the cause of the hang could be excessively time-consuming and may not be
cost-effective in your operating environment. To isolate the possible cause of the hang, would require a debug boot of the system.
Instructions for doing this are included in the document "Capturing Boot Debug", available at
http://techsupport.services.ibm.com/server/aix.srchBroker. It is still possible, in the end, that isolation of the problem may indicate a restore
or reinstall of AIX is necessary to correct it.