- 论坛徽章:
- 0
|
系统启动，停在了0554
LED 552, 554, or 556
A LED code of 552, 554, or 556 during a standard disk-based boot indicates that
a failure occurred during the varyon of the rootvg volume group. This can be the
cause of:
A damaged file system
A damaged 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 damaged 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
A damaged superblock
To diagnose and fix the problem, you need to boot from the installation media,
navigate the menus to access the volume group, and start a shell before
mounting the file systems.
If the fsck command indicates that block 8 could not be read when used, as
shown in 3.4.1, “LED 551, 555, or 557” on page 26, the file system is probably
unrecoverable. 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 /dev/hd4 cannot be recreated. If /dev/hd4 is unrecoverable, you must
reinstall AIX.
A corrupted ODM in the BLV is also a possible cause for these LED codes. To
create a usable one, run the following commands that remove the system's
configuration and save it to a backup directory:
# /usr/sbin/mount /dev/hd4 /mnt
# /usr/sbin/mount /dev/hd2 /usr
# /usr/bin/mkdir /mnt/etc/objrepos/bak
# /usr/bin/cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/bak
# /usr/bin/cp /etc/objrepos/Cu* /mnt/etc/objrepos
# /usr/sbin/umount all
# exit
After this, you must copy this new version of the ODM in the RAMFS to the BLV.
This is done with the savebase command. Before that, make sure you place it on
the disk used for normal boot by executing:
# lslv -m hd5
Save the clean ODM database to the boot logical volume. For example:
# savebase -d /dev/hdisk0
Finally, recreate the BLV and reboot the system. For example:
# bosboot -ad /dev/hdisk0
# shutdown -Fr
Another possible reason for these error codes is a corrupted superblock. If you
boot in maintenance mode and receive error messages such as Not an AIX file
system or Not a recognized file system type, it is probably due to a corrupted
superblock in the file system.
Each file system has two super blocks: One in logical block 1 and a copy in
logical block 31. To copy the superblock from block 31 to block 1 for the root file
system, issue the following command (before you use this command, check the
product documentation for the AIX release you are using to make sure all of the
parameters shown are correct):
# dd count=1 bs=4k skip=31 seek=1 if=/dev/hd4 of=/dev/hd4
LED 551, 555, or 557
There can be several reasons for a system to halt with LED codes 551, 555, or
557. For example:
A damaged file system
A damaged journaled file system (JFS) log device
A failing disk in the machine that is a member of the rootvg
To diagnose and fix these problems, you need to boot from a bootable media,
access the maintenance menus, choose Access a Volume Group, and start a
shell before mounting file systems, and then do one or all of the following actions:
To ensure file system integrity, run the fsck command to fix any file systems
that may be corrupted:
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
To ensure the correct function of the log device, run the logform command on
/dev/hd8 to recreate the log device:
# /usr/sbin/logform /dev/hd8
If the BLV is corrupted, recreate the BLV and update the bootlist:
# bosboot -a -d /dev/hdisk0
# bootlist -m normal hdisk0 |
|
免费注册
发表于 2004-11-14 21:33
