Common Boot Time LEDs and Their Solution
LED 201 - Damaged Boot Image
----------------------------
1. Access your rootvg using a maintenance shell.
2. Check / and /tmp filesystems. If they are almost full create more space.
3. Determine the boot disk by using the command lslv -m hd5
4. Re-create boot image using bosboot -a -d /dev/hdiskn
5. Check for CHECKSTOP errors in the error log. If such errors are
found, it is probably failing hardware.
6. Shutdown and restart the system.
LED 223-229 - Invalid Boot List
-------------------------------
1. Set the key mode switch to service (F5 for systems without keylock)
and power up the machine.
2. If display continues normally, change the key mode switch to Normal
and continue with step 3. If you do not get the prompt, go to step 4.
3. When you get the login prompt, login and change the bootlist.
Continue with step 7.
4. Access your rootvg using a maintenance shell and continue with step 5.
5. Determine the boot disk by using the command lslv -m hd5.
6. Change the bootlist.
7. Shutdown and restart your system.
LED 551, 555, and 557 - Corrupted File System, Corrupted JFS log, and so on.
----------------------------------------------------------------------------
1. Access your rootvg using a maintenance shell, access the rootvg before
mounting any file systems (Option 2 on the Maintenance screen).
2. Verify and correct the file systems as follows:
fsck -y /dev/hd1
fsck -y /dev/hd2
fsck -y /dev/hd3
fsck -y /dev/hd4
fsck -y /dev/hd9var
3. Format the JFS log again by using the command:
/usr/sbin/logform /dev/hd8
4. Use lslv -m hd5 to find out the boot disk.
5. Recreate boot image by using the command:
bosboot -a -d /dev/hdiskn
Where n is the disk number of the disk containing boot logical volume.
LED 552, 554, and 556 - Super Block Corrupted or 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 Access your
rootvg using a maintenance shell, access the rootvg before
mounting any file systems (Option 2 on the Maintenance screen).
6. Mount the root and usr file system as follows:
mount /dev/hd4 /mnt
mount /usr
7. Copy system configuration to a back up directory:
mkdir /mnt/etc/objrepors/backup
cp /mnt/etc/objrepors/Cu* /mnt/etc/objrepos
8. Copy configuration from 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 bootdisk 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
12. Reboot, if system does not come up, reinstall BOS.
LED 553 - Corrupted /etc/inittab file
-------------------------------------
1. Access the rootvg with all file systems mounted.
2. Check for free space in /, /var and /tmp by using df command.
3. Check the /etc/inittab file and correct the inittab problems if there is
one empty inittab file, missing inittab file or wrong entry in inittab file.
4. Check problems with:
/etc/environment file
/bin/sh
/bin/bsh
/etc/fsck
/etc/profile
/.profile
5. Shutdown the system and reboot.
文章来源于领测软件测试网 https://www.ltesting.net/