Recovery from LED 551, 555, or 557 in AIX V4

Contents

About this document

Causes of an LED 551, 555, or 557

Recovery procedure

1. Power down your system. If it has a key mode select switch (that is, if it is a Microchannel-based system), turn the key to the Service position.

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
   • NON_AUTOINSTALL mksysb
   • Bootable Install Tape

   Follow the screen prompts to the following menu:

      Welcome to Base Operating System 
      Installation and Maintenance 
   

3. Choose Start Maintenance Mode for System Recovery (Option 3). The next screen has the Maintenance Menu.
   • Choose Access a Root Volume Group (Option 1).

     The next screen displays a warning that indicates you will not be able to return to the Base OS menu without rebooting.

   • Choose 0 continue.

     The next screen displays information about all volume groups on the system.

   • Select the root volume group by number.

   • Choose Access this volume group and start a shell before mounting the filesystems (Option 2).

   If you get errors indicating that a physical volume is missing from the rootvg, run diagnostics on the physical volumes to find out if you have a bad disk. Do not continue with the rest of the steps in this document.

   If you get other errors from the preceding option, do not continue with the rest of the steps in this document. Correct the problem causing the error. If you need assistance correcting the problem, contact one of the following:

   • your local branch office
   • your point of sale
   • your AIX support center

4. Format the default jfslog for the rootvg JFS file systems.

      /usr/sbin/logform /dev/hd8 
   

   Answer yes when asked if you want to destroy the log.

5. Next, run the following commands to check and repair file systems. (The -y option gives fsck 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 
   

6. Type exit. The file systems will automatically mount after you type exit.

7. 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. Otherwise, skip to step 8.

      cd /sbin/helpers 
      ls -l v3fshelper* 
   

   If you have only one version of the v3fshelper file (for example, v3fshelper), proceed to step 8.

   If there is a version of v3fshelper marked as original (for example, v3fshelper.orig), run the following commands:

      copy v3fshelper v3fshelper.afs 
      copy v3fshelper.orig v3fshelper 
   

8. 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 
   

   WARNING: Do not proceed further if the system is a /usr client, diskless client, or dataless client.

9. Recreate the boot image and alter the boot list. (hdisk# is the boot disk determined in step 8.)

      bosboot -a -d /dev/<hdisk#>
      bootlist -m normal <hdisk#>
   

   NOTE: If the preceding bosboot command fails with an error message indicating the boot logical volume does not exist on the device specified, this generally indicates the hdisk numbering in Normal mode is different than the hdisk numbering in Service mode. You must specify the special device file representing the PV with the PVID which matches the PVID in the lslv -m hd5 output in step 8.

10. If you copied the v3fshelper file in step 7, copy AFS file system helper back to v3fshelper:

       copy v3fshelper.afs v3fshelper 
    

11. With the key in Normal position, run

       shutdown -Fr 
    

If you followed all of the preceding steps and the system still stops at an LED 551, 555, or 557 during a reboot in normal mode, you may want to pursue further system recovery assistance from one of the following:

• your local branch office
• your point of sale
• your AIX support center

For reasons of time and the integrity of your AIX operating system, the best alternative at this point may be to reinstall AIX.

[ Doc Ref: 90605189014742     Publish Date: Oct. 12, 2000     4FAX Ref: 4190 ]