AIX F80 0554错误

qinglory

http://www.loveunix.net/discuz/viewthread.php?tid=48461

qinglory

LED 552, 554, and 556 - Super block corrupted and corrupted customized ODM
database
1. Repeat steps 1 through 2 for LEDs 551, 555, and 557.
2. If fsck indicates that block 8 is corrupted, the super block for the file system is
corrupted and needs to be repaired. Enter the command:
dd count=1 bs=4k skip=31 seek=1 if=/dev/hdn of=/dev/hdn
where n is the number of the file system.
3. Rebuild your JFS log by using the command:
/usr/sbin/logform /dev/hd8
4. If this solves the problem, stop here; otherwise, continue with step 5.
5. Your ODM database is corrupted. Restart your system and follow the procedure
given in 4.4.2, “Accessing a system that will not boot” on page 105 to access rootvg
with choice 2 on the Volume Group Information screen.
6. Mount the root and usr file systems as follows:
mount /dev/hd4 /mnt
mount /usr
7. Copy the system configuration to a back up directory:
mkdir /mnt/etc/objrepos/backup
cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup
8. Copy the configuration from the RAM file system as follows:
cp /etc/objrepos/Cu* /mnt/etc/objrepos
9. Unmount all file systems by using the umount all command.
10. Determine the boot disk by using the lslv -m hd5 command.
11. Save the clean ODM to the boot logical volume by using the command:
savebase -d/dev/hdiskn
where n is the disk number of the disk containing boot logical volume.
12. Reboot, if the system does not come up, and reinstall BOS.

qinglory

先查资料，后实践；机器在机房，离公司较远

qinglory

http://www.google.com/search?q=l ... lla:zh-CN

qinglory

3.6.2 LED 552, 554, or 556 halt
This section discusses the known causes of LED 552, 554, and 556, including a
procedure for recovery from these errors.
An LED code of 552, 554, or 556 during a standard disk based boot indicates a
failure occurred during the varyon of the rootvg volume group.
The known causes of an LED 552, 554, or 556 halt are as follow:

A corrupted file system

A corrupted Journaled File System (JFS) log device

A bad IPL-device record or bad IPL-device magic number (The magic number
indicates the device type.)
Note: Do not proceed further if the system is a /usr client, diskless
client, or dataless client.
Chapter 3. Boot problems 61

A corrupted copy of the Object Data Manager (ODM) database on the boot
logical volume

A hard disk in the inactive state in the root volume group
To diagnose and fix the problem, you will need to boot from bootable media and
run the fsck command on each file system. If the file system check fails, you may
need to perform other steps.
To recover from an LED 552, 554, or 557, complete the following steps:
1. Turn the key to the Service position (MCA machines) then power on. On PCI
machines, power on, press F5 or 5 when the Icon screen appears. This will
start the Service mode boot from CD-ROM or mksysb.
2. Using bootable media at the same version and level as the system, boot the
system. The bootable media can be any one of the following:
– A bootable CD-ROM
– mksysb
– A bootable install tape
Follow the prompts to the Welcome to Base OS menu.
3. Choose Start Maintenance Mode for System Recovery (option 3). The next
screen displays prompts for the Maintenance menu.
Choose Access a Root Volume Group (option 1).
At this stage, the console will display information about all the volume groups
on the system. rootvg will usually be the top one in the list. Choose 1 and the
console will display the logical volumes contained within the chosen volume
group. If it does not appear to be rootvg, take the option to return and choose
another volume group. When rootvg has been found, choose Access this
volume group and start a shell before mounting the file systems (option 2).
If you get errors from the preceding option, such as missing hard disk
messages, do not continue with the rest of this procedure. Correct the
problem causing the error. If you need assistance correcting the problem
causing the error, contact your AIX support personnel.
4. Run the following commands to check and repair file systems. The -y option
gives the fsck command permission to repair file systems when necessary.
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
Note: Do not use this procedure if the system is a /usr client, diskless
client, or dataless client.
62 Problem Solving and Troubleshooting in AIX 5L
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
If any of the following conditions occur, proceed accordingly.
If fsck indicates that block 8 could not be read, the file system is probably
unrecoverable. If fsck indicates that block 8 could be read, but one of the
following errors is given:
fsck: Not an AIX V3 file system.
fsck: Not a recognized file system type.
Then go to next step.
If fsck indicates that a file system has an unknown log record type, or if fsck
fails in the logredo process, then go to step 6.
If the file system checks were successful, skip to step 8.
The easiest way to fix an unrecoverable file system is to recreate it. This
involves deleting it from the system and restoring it from a backup. Note that
hd2 and hd3 can be recreated but hd4 cannot be recreated. If hd4 is
unrecoverable, you must reinstall AIX. For assistance with unrecoverable
file systems, contact your AIX support personnel.
Do not follow the rest of the steps in this procedure.
Attempt to repair the file system with this command:
# fsck -p /dev/hd#
Replace hd# with the appropriate file system logical volume name.
Now skip to step 7.
5. A corruption of the JFS log logical volume has been detected. Use the
logform command to reformat it:
# /usr/sbin/logform /dev/hd8
Answer yes when asked if you want to destroy the log.
6. Repeat step 4 for all file systems that did not successfully complete fsck the
first time.
If step 4 fails a second time, the file system is almost always unrecoverable. In
most cases, step 4 will be successful. If step 4 is successful, continue to step
8.
7. With the key in the Normal position, run the following commands to reboot the
system:
# exit
# sync;sync;sync
# shutdown -Fr
Chapter 3. Boot problems 63
As you reboot in Normal mode, notice how many times LED 551 appears. If
LED 551 appears twice, fsck is probably failing because of a bad fshelper
file. If this is the case, and you are running AFS, see step 11.
The majority of instances of LED 552, 554, and 556 will be resolved at this
point. If you still have an LED 552, 554, or 556, repeat step 1 through step 3.
8. Run the following commands that remove much of the system's configuration
and save it to a backup directory:
# mount /dev/hd4 /mnt
# mount /dev/hd2 /usr
# mkdir /mnt/etc/objrepos/bak
# cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/bak
# cp /etc/objrepos/Cu* /mnt/etc/objrepos
# /etc/umount all
# exit
9. 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
10.Save the clean ODM database to the boot logical volume. (# is the number of
the fixed disk, determined with the previous command.)
# savebase -d /dev/hdisk#
If you are running AFS, go to step 11; otherwise, go to step 12.
11.If you are running the Andrew File System (AFS), use the following
commands to find out whether you have more than one version of the
v3fshelper file:
# cd /sbin/helpers
# ls -l v3fshelper*
If you have only one version of the v3fshelper file (for example, v3fshelper),
proceed to step 12.
If there is a version of v3fshelper marked as original (for example,
v3fshelper.orig), run the following commands:
# cp v3fshelper v3fshelper.afs
# cp v3fshelper.orig v3fshelper
Recreate the boot image (hdisk# is the fixed disk determined in step 10):
# bosboot -a -d /dev/hdisk#
Note: Do not proceed further if the system is a /usr client, diskless
client, or dataless client.
64 Problem Solving and Troubleshooting in AIX 5L
12.If you copied files in the previous step, copy the AFS file system helper back
to v3fshelper:
# cp v3fshelper.afs v3fshelper
Turn the key to Normal position and run the following command:
# shutdown -Fr
If you followed all of the preceding steps, and the system still stops at an LED
552, 554, or 556 during a reboot in Normal mode, you may want to ask for further
system recovery assistance from your AIX support personnel.
For reasons of time, and the for integrity of your AIX operating system, the best
alternative at this point may be to reinstall AIX.

qinglory

aix 4.3
3.6.2 LED 552, 554, or 556 halt
This section discusses the known causes of LED 552, 554, and 556,
including a procedure for recovery from these errors.
An LED code of 552, 554, or 556 during a standard disk based boot indicates
a failure occurred during the varyon of the rootvg volume group.
The known causes of an LED 552, 554, or 556 are:
• A corrupted file system.
• A corrupted Journaled File System (JFS) log device.
• A bad IPL-device record or bad IPL-device magic number. (The magic
number indicates the device type.)
• A corrupted copy of the Object Data Manager (ODM) database on the boot
logical volume.
• A hard disk in the inactive state in the root volume group.
To diagnose and fix the problem, you will need to boot from BOOTABLE
MEDIA and run the fsck command on each file system. If the file system
check fails, you may need to perform other steps.
To recover form an LED 552, 554, or 557, complete the following steps:
1. Turn the key to the Service position (MCA machines) then power on. On
PCI machines, power on, press F5 or 5 when the Icon screen appears.
This will start the Service mode boot from CD or mksysb.
2. With bootable media of the same version and level as the system, boot the
system. The bootable media can be any one of the following:
• Bootable CD-ROM
Do not use this procedure if the system is a /usr client, diskless client, or
dataless client.
Note
Boot problems 49
• mksysb
• Bootable Install Tape
Follow the prompts to the Welcome to Base OS menu.
3. Choose Start Maintenance Mode for System Recovery (Option 3). The
next screen displays prompts for the Maintenance menu.
Choose Access a Root Volume Group (Option 1).
At this stage, the console will display information about rootvg and a menu
with two options.
Choose Access this volume group and start a shell before mounting
the filesystems (Option 2).
If you get errors from the preceding option, do not continue with the rest of
this procedure. Correct the problem causing the error. If you need
assistance correcting the problem causing the error, contact your AIX
support function.
4. Run the following commands to check and repair file systems. The -y
option gives the fsck command permission to repair file systems when
necessary.
fsck -y /dev/hd1
fsck -y /dev/hd2
fsck -y /dev/hd3
fsck -y /dev/hd4
fsck -y /dev/hd9var
If any of the following conditions occur, proceed accordingly.
If fsck indicates that block 8 could not be read, the file system is probably
unrecoverable. See step 5 for information on unrecoverable file systems.
5. If fsck indicates that block 8 could be read, but one of the following errors
is given:
•fsck: Not an AIXV3 file system.
•fsck: Not a recognized file system type.
Then go to step 6.
If fsck indicates that a file system has an unknown log record type, or if
fsck fails in the logredo process, then go to step 7.
If the file system checks were successful, skip to step 9.
The easiest way to fix an unrecoverable file system is to recreate it. This
involves deleting it from the system and restoring it from a backup. Note
that hd2 and hd3 can be recreated but hd4 cannot be recreated. If hd4 is
50 Problem Solving and Troubleshooting in AIX Version 4.3
unrecoverable, you must reinstall AIX. For assistance with unrecoverable
file systems, contact your AIX support function.
Do not follow the rest of the steps in this procedure.
Attempt to repair the file system with this command:
fsck -p /dev/hd#
Replace hd# with the appropriate file system logical volume name.
Now skip to step 8.
6. A corruption of the JFS log logical volume has been detected. Use the
logform command to reformat it:
/usr/sbin/logform /dev/hd8
Answer yes when asked if you want to destroy the log.
7. Repeat step 4 for all file systems that did not successfully complete fsck
the first time.
If step 4 fails a second time, the file system is almost always
unrecoverable. See step 5 for an explanation of the options at this point. In
most cases, step 4 will be successful. If step 4 is successful, continue to
step 9.
8. With the key in the Normal position, run the following commands to reboot
the system:
exit
sync;sync;sync
shutdown -Fr
As you reboot in Normal mode, notice how many times LED 551 appears.
If LED 551 appears twice, fsck is probably failing because of a bad
fshelper file. If this is the case, and you are running AFS, see step 12.
The majority of instances of LED 552, 554, and 556 will be resolved at this
point. If you still have an LED 552, 554, or 556, repeat step 1 through step
3.
9. Run the following commands that remove much of the system's
configuration and save it to a backup directory:
mount /dev/hd4 /mnt
mount /dev/hd2 /usr
mkdir /mnt/etc/objrepos/bak
cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/bak
cp /etc/objrepos/Cu* /mnt/etc/objrepos
/etc/umount all
exit
Boot problems 51
10.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
11.Save the clean ODM database to the boot logical volume. (# is the number
of the fixed disk, determined with the previous command.)
savebase -d /dev/hdisk#
If you are running AFS, go to step 12;
otherwise, go to step 13.
12.If you are running the Andrew File System (AFS), use the following
commands to find out whether you have more than one version of the
v3fshelper file:
cd /sbin/helpers
ls -l v3fshelper*
If you have only one version of the v3fshelper file (for example,
v3fshelper), proceed to step 13.
If there is a version of v3fshelper marked as original (for example,
v3fshelper.orig), run the following commands:
cp v3fshelper v3fshelper.afs
cp v3fshelper.orig v3fshelper
Recreate the boot image (hdisk# is the fixed disk determined in step 11):
bosboot -a -d /dev/hdisk#
13.If you copied files in step 12, copy the AFS file-system helper back to
v3fshelper:
cp v3fshelper.afs v3fshelper
Turn the key to Normal position and run:
shutdown -Fr
If you followed all of the preceding steps, and the system still stops at an LED
552, 554, or 556 during a reboot in Normal mode, you may want to pursue
further system recovery assistance from your AIX support function.
For reasons of time and the integrity of your AIX operating system, the
best alternative at this point may be to reinstall AIX.