It is currently Thu, 21 Aug 2014 01:12:50 GMT



 
Author Message
 LED 552 INFO
I got over a dozen requests for this, and since I would prefer that
everyone have _ALL_ the facts, I will post this.  I have seen an
awful lot of misinformation, and some good and poor assumptions on
what causes the machine to fail on booting up with whatever LED codes.
The Table of contents are as follows

LED 201
LED 223-229
LED 551
LED 552
LED 553
LED C99
LED C31
Article on using /etc/continue from the bosboot diskettes and bootable
        tapes

Print it out because you won't be able to get to it when you need it otherwise.

Changed 12/03/91                LED 201       Procedures verified on AIX 3.1.5

If a 6000 stops at led 201 during boot it may be due to either a software
problem or a hardware problem.  Most likely a software problem.

If the leds first go past 299, and then back to 201 -- it's most likely a
corrupted boot logical volume (a software problem).

If the leds never get to 299 - it can't be software because the boot process
hasn't yet loaded any software, so it's time to suspect hardware.

Resolution to SOFTWARE problem:

The corruption of the boot logical volume will usually occur if the /(root) or
/tmp filesystems are full when the bosboot command is run.  Bosboot is run
during installation of updates.  The following procedure can be used to correct
this problem.

  - With the key in the 'SERVICE' position, boot from your
    installation media

  - Select option 5 from the installation menu

  - Type the following commands to vary on the root volume group

        /etc/continue hdisk0

  - Correct the out of space condition

        Use 'df' to check for free space in /dev/hd4 and /dev/hd3.
        Erase files as necessary to correct the problem.

  - Create the new boot image.

        bosboot -a -d /dev/hdisk0

  - Place the key in 'NORMAL', execute the following command

        shutdown -Fr

Resolution to HARDWARE problem:

The hardware problem of the led 201 is commonly due to a hardware problem with
the system planar.  The hardware issued a check stop error during boot because
of a detected hardware problem.  Usually the error log will contain an entry
for the check stop.

You should go ahead and try the software procedures just in case but be
prepared to have a CE brought into the picture.  The CE should contact L2
hardware support.  The hardware guys are supposed to be aware of the problem.

                                        LED 223 - 229

        1.  boot in service mode off bosboot diskettes
        2.  choose option 5
        3.  run /etc/continue hdisk0
        4.  run bootlist -m normal hdisk0
        5.  reboot in normal mode with the "shutdown -Fr" command

                                                June 13, 1991

                        LED 551 SYSTEM RECOVERY

 There are several reasons for an LED 551:

        PROBLEM                                 Solution
_____________________________________________________________________________
        /dev missing, or corrupted              - mkdir /dev
        /bin empty or missing                   - reinstall
        bad boot logical volume                 - bosboot -a
        /etc problems                           - restore selective files
                                                  if possible, or reinstall
        corrupted filesystems                   - fsck /dev/hd4 as per LED552
        a bad install of the system             - install AIX properly

**********************************************************************

                        LED 552 SYSTEM RECOVERY

 There are, so far, several known causes, of the 552 LED upon IPL.  One is
 bad savebase information.  The second is the the log logical volume (hd8)
 has somehow gotten corrupted.  The third is that the odm may be corrupted.
 To diagnose and fix a 552, I recommend these not always so simple steps:

 1) Boot from bosboot diskette or tape and get to install/maint menu
    - Key in service position

 2) choose option 5

 3) run "/etc/continue hdisk#"
    - Check out the article on "running /etc/continue"

 4) If there are any mounted filesystems (whether /etc/continue ran cleanly
    or not) unmount them.  To check for mounted filesystems, issue the
    following command.

        # mount

    If /dev/ram0 is the only mounted filesystem, then goto step 5.  If
    /dev/hd4 is mounted onto /mnt then

        # umount all
        # mount

    If /dev/hd4 is still mounted, then execute the following instructions
        # exit;
        # umount all
        # mount
        (The only mounted filesystem should be /dev/ram0 on /)

 5) Now run fsck on the following filesystems:

                # fsck -y /dev/hd1
                # fsck -y /dev/hd2
                # fsck -y /dev/hd3
                # fsck -y /dev/hd4

    If this fails, or the logredo process fails, or indicates any
    filesystems with unknown log record type then go to step 6, else go
    to step 7.

 6) run "/etc/aix/logform  /dev/hd8"

    Answer YES to the question asking if you want to destroy your LOG.
    Logform will reformat the log logical volume.

      repeat step 5.

 7) reboot
    - Key in normal position

 8) If LED 552 still persists, then repeat steps 1-3, and make certain that
   you have chosen the proper drive that has hd5 on it.  Then, goto Step 9.

 9) execute the

# mount

   command, and you should have /dev/ram0, /dev, /dev/hd4, /dev/hd2 and
   /dev/hd3 all mounted.  If they are all there, goto step 10.

   If not, then run
# fsck -y /dev/hd#
   where # is the number that matches the missing filesystem.
   If it gives you an error message that it could not read block
   8, then the filesystem is most likly unrecoverable.
   If you get a bad argument error, then run

# dd count=1 bs=4k skip=31 seek=1 < /dev/hd{N} > /dev/hd{M}

  where {N} is a working logical volume number, and N is the LV that
  fsck is failing on.

  then run  
# fsck /dev/hd#
   again.  if it still fails, then that filesystem is unrecoverable, and
   needs to be recreated.  hd2 and hd3 can be recreated, hd4 will require
   a reinstall.  
   If hd3 is missing, then run
* # lsvg -l rootvg

*   NOTE the number of PP's on the /dev/hd3

*# rmlv -f /dev/hd3
*# mklv -y'hd3' rootvg N

*   (N is the number of PP's in the Logical volume)
   If hd2 is the volume missing then you will need to have a backup of /usr
   handy.

   run
%# lsvg -l rootvg

%   NOTE the number of PP's on the /dev/hd2

*# rmlv -f /dev/hd2
*# mklv -y'hd3' rootvg N

*   (N is the number of PP's in the Logical volume)

*# mount /dev/hd2 /usr
*# restore -xvdf/dev/rmt0 ./usr

*   (This assumes that there are no filesystems under /usr.  Your milage may
*    differ)

    If /dev/hd4 has the bad super block, then you will need to install AIX
    on that system again.

10) set the TERM variable to the proper terminal type for your console.

# export TERM=hft   (or ibm3151 or vt100... whatever you happen to be running)

    Using your favorite editor, modify the /etc/rc.boot4 file.  Change

# bring up the root volume group
/etc/ipl_varyon -v
if [ $? != 0 ]
then
        while :
        do
                showled 0x552
        done
fi

-----  TO

# bring up the root volume group
/etc/ipl_varyon -v
RC=$?
if [ $RC != 0 ]
then
        while :
        do
                showled 0x552
                sleep 1
                showled $RC
                sleep 1
        done
fi

11)  Save the file, and run
# bosboot -a

12)  Next, if you don't have a lot of system configuration (tty's really),
     then run
# mkdir /etc/objrepos/bak
# cp /etc/objrepos/Cu* /etc/objrepos/bak
# cp /etc/objrepos/boot/Cu* /etc/objrepos
# savebase

13)  Reboot in Normal mode again.

14)  If LED 552 persists you should also have the return code from ipl_varyon
     in the LED.  If that value is 2, 3, 4, 8, or 9  and you did not
     perform step #12, then do so.  
     If you get a value of 6, 7, 8, or C, then go to step 15
     If you get a value of A, then check /etc/drivers/hd_pin because
     it cannot be loaded.
     If the value is B, then the IPL record is bad, and this may be
     unrecoverable, we haven't figured out how to fix that one yet.
     Call us up, and we'll work on it with you.  It is caused by an invalid
     IPL record on the volume group.

15)  You got here because ipl_varyon failed to either open, or modify the
     /dev/ipldevice entry.  This may be due to a bad boot LV, or because of
     a bad ODM.  Most likly, it is a problem with the ODM.  Perform step 12,
     if you haven't yet done so.  

**********************************************************************

LED 553

The system will stop during IPL with 553 in the LEDs if init has a problem
running or in reading the inittab file.  This will often occur when the
/tmp or the / filesystem is full.
The following procedure can be used to correct this problem.

  - With the key in the 'SERVICE' position, boot from your
    installation media

  - Select option 5 from the installation menu

  - Type the following command to vary on the root volume group

        /etc/continue hdisk0

  - check for and correct an out of space condition

        Use 'df' to check for free space in /dev/hd4 and /dev/hd3.
        Erase files as necessary to correct the problem.  Suspect
        /smit.log and /smit.script as being the problem.

  - Check the /etc/inittab for corruption:  Usually it will be empty, or
    missing or have an entry in it that is not correct:

  - If inittab is corrupted then do the following:
   - Create the /etc/inittab file using your favorite editor.  You
    must set your TERM environment variable using commands similar
    to the following prior to starting the editor.

# export  TERM=hft

  -  if the inittab file was ok, then check the following files for
     any modification or permissions problem:

        /etc/environment
        /bin/sh
        /bin/bsh
        /etc/fsck missing or corrupted.  This can be copied from the ram filesystem
        /etc/brc
        /etc/profile
        /.profile

  - Place the key in 'NORMAL', execute the following command

        shutdown -Fr

: @(#)inittab   1.22  com/cfg/etc,3.1,9021 4/6/90 17:18:07
init:2:initdefault:
brc::sysinit:/etc/brc >/dev/console 2>&1 # Phase 2 of system boot
rc:2:wait:/etc/rc > /dev/console 2>&1  # Multi-User checks
srcmstr:2:respawn:/etc/srcmstr          # System Resource Controller
rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons
cons:0123456789:respawn:/etc/getty /dev/console
piobe:2:once:/bin/rm -f /usr/lpd/pio/flags/*  # Clean up printer flags files
cron:2:respawn:/etc/cron
qdaemon:2:once:/bin/startsrc -sqdaemon
writesrv:2:once:/bin/startsrc -swritesrv

LED C99

The LED C99 is usually caused by a bad /usr/bin/odmget command.
/usr may be missing, or the /etc/filesystems file may be corrupted.

 1) Boot from bosboot diskette or tape and get to install/maint menu
    - Key in service position

 2) choose option 5

 3) run "/etc/continue hdisk#"
    - Check out the article on "running /etc/continue"

 4) Check to see if /etc/filesystems has the /usr filesystem in it.

 5) use the mount command to check to see if /usr is mounted.

 6) # cd /usr/bin
    If the command fails, then /usr/bin needs to be restored.

 7) # ls -l /usr/bin/odmget
    If there is no odmget, then check to see if other files are missing from
    /usr/bin.

LED C31
 1) Boot from bosboot diskette or tape and get to install/maint menu
    - Key in service position

 2) choose option 5

 3) run "/etc/continue hdisk#"
    - Check out the article on "running /etc/continue"

 4) chcons -a login=enable /dev/hft/0

 5) reboot in normal mode.

 6) If you still have LED C31, then repeat step 1-3, and goto step 7.

 7)  Next,
# mkdir /etc/objrepos/bak
# cp /etc/objrepos/Cu* /etc/objrepos/bak
# cp /etc/objrepos/boot/Cu* /etc/objrepos
# savebase

Article on /etc/continue:

1) lqueryvg -?                                : Provides you the valid
                                                options and syntax
2) lqueryvg -p hdisk? -At                     : Provides you LV names,
                                                numbers and LV STATES
3) getlvodm -P                                : To aquire the association
                                                of the hdisk_name with the hdisk PVID
4) lquerypv -p PVID -N hdisk# -At | grep LVID : Lists in column format (from L to R)
                                             PVID STATUS LVID EXTENSION LP#
-----------------------------------------------------------------------------
The above commands should be run PRIOR to executing /etc/continue from
maintenance mode if you find that you are having problems getting filesystems
to mount or are getting error messages executing /etc/continue that may be
related.

The reason for this is that the Installation/Maintenance Diskettes will
assign an hdisk name to a PV that may/will be different from the names
the customer is familiar with when booted in Multi User Mode.

I will illistrate the command and its output providing information that will
be needed to help determining many things prior to executing /etc/continue.
The order in which the illistration is given should be the order in which the
commands should be executed, Most of the time.

NOTE: that if you are working with a 552 LED then this procedure will
provide you with the hdisk name for the command 'bosboot -a -d hdisk?'

START:

1) Your first step is to locate PV's that are part of the rootvg. To do this
   GOTO step 2.

   *) After issuing the command 'getlvodm -P' write down all the hdisk_names associated
      with the rootvg. This command will show the the VG's the hdisk(s) are associated
      with only if importvg and varyonvg have already been run. (ie. after /etc/continue)
      Otherwise this command is good to see if the system recognizes any hard drives.

2) Now you will need to find out which PV contains hd5 (blv)
   GOTO step 3

   * ) After issuing the command 'lqueryvg -p hdisk? -At' look for hd5 and write down
       the LVID number (ie. 00000503b567e4.3). Its this number you will have to search
       for in the next step.

3) Now the goal is to find out which PV the hd5 LV resides on. Once you find this you
   will know which Hdisk_name to supply the /etc/continue command
   GOTO step 4

   * ) NOTE: You do not have use of the 'pg' command. Use Ctrl-s and Ctrl-q to scroll
       You will issue the 'lquerypv -p PVID -N hdisk_name -At' once for each hdisk
       associated with the rootvg until you spot the LVID for hd5 on the output.

-----------------------------------------------------
First:

# lqueryvg -?          
lqueryvg: illegal option -- ?
Usage: lqueryvg [-g VGid | -p PVname] [-NsFncDaLPAvt]

-----------------------------------------------------
Second:

# getlvodm -P
   ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD hdisk_name
   3                   ZDDDDDDDDDDDDDDDDDDDDDDD PVID
   3                   3              ZDDDDDDDD VG_Name
ZDD^DD?        ZDDDDDDD^DDDDDD?    ZDD^DD?
hdisk0         00000305b28a03e1    rootvg        
hdisk1         00000305b23ff460    rootvg

-----------------------------------------------------
Third:

# lqueryvg -p hdisk0 -At
Max LVs:        256
PP Size:        22
Free PPs:       43
LV count:       11
PV count:       2
Total VGDAs:    3

                       ZDDDDDDDDDDDDDDDDDDDDDDD Logical Volume Identifier (LVID)
                       3         ZDDDDDDDDDDDDD Minor device number (see /dev)
                       3         3    ZDDDDDDDD Logical Volume Name (LVN)
                       3         3    3  ZDDDBD LV state
                       3         3    3  3   C  ( 0 indicates LV is not defined to a VG )
                       3         3    3  3   C  ( 1 indicates LV is defines to a VG )
                       3         3    3  3   @  ( 2 indicates LV has stale logical partitions )
                ZDDDDDD^DDDDDDD?          
Logical:        00000305b2403191.1   hd6 1  
                00000305b2403191.2   hd61 1  
                00000305b2403191.3   hd5 1  
                00000305b2403191.4   hd7 1  
                00000305b2403191.5   hd8 1  
                00000305b2403191.6   hd4 1  
                00000305b2403191.7   hd2 1  
                00000305b2403191.8   hd3 1  
                00000305b2403191.9   hd1 1  
                00000305b2403191.10  paging00 1  
                00000305b2403191.11  lv00 1  

                                 ZDDDDDDDDDDDDDD Number of VGDA's
                                 3   ZDDDDDDDDDD State
Physical:       00000305b28a03e1 2   0  
                00000305b23ff460 1   0
                @DDDvDDY        
                    3
                    @DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD Type of H.W. (See uname -m)

-----------------------------------------------------
Fourth:
                     /* Note this command is run once for each PVID the customer has */
                     /* Make sure you change the hdisk_name to match the PVID number */
                     /* See the "getlvodm -P" command for PVID's and hdisk_names     */
                     /* See "lqueryvg -p hdiskX -At" for LVID's                      */

# lquerypv -p PVID -N hdisk_name -At |grep LVID  

PP Size:        22
PV State:       0
Total PPs:      76
Alloc PPs:      38
Total VGDAs:    2

                ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD PVID
                3        ZDDDDDDDDDDDDDDDDDDDDDDDDD Minor Device number of a LV
                3        3    ZDDDDDDDDDDDDDDDDDDBD (0 indicates PP is free)      
                3        3    3                  CD (1 indicates PP is allocated)
                3        3    3                  CD (2 indicates PP has stale data)
                3        3    3                  @D (4 indicates PP is being resynced)
                3        3    3                       ( See lvm.h ; PP STATES )
                3        3    3
                3        3    3                  ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD LVID.VGID
                3        3    3                  3        ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD Minor Device number of a LV
                3        3    3                  3        3   ZDDDDDDDDDDDDDDDDDDDDDDDDDD LV number  
                3        3    3                  3        3   3             ZDDDDDDDDDDDD 1st Alt Volume ID's
                3        3    3                  3        3   3             3        ZDDD Minor Device number of a LV
                3        3    3                  3        3   3             3        3    2nd Alt Volume ID's
                3        3    3                  3        3   3             3        3            3
        ZDDDDDDD^DDDDDD?                 ZDDDDDDD^DDDDDD?           ZDDDDDDD^DDDDDD?      ZDDDDDDD^DDDDDD?
PVMAP:  00000305b28a03e1:1    1 ODMtype  00000305b2403191.3   1     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:2    1 ODMtype  00000305b2403191.3   2     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:3    1 ODMtype  00000305b2403191.4   1     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:4    1 ODMtype  00000305b2403191.4   2     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:5    0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:6    0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:7    0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:8    0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:9    0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:10   0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  
PVMAP:  00000305b28a03e1:11   0 ODMtype  0000000000000000.0   0     0000000000000000:0    0000000000000000:0  



 Sun, 17 Jul 1994 03:56:54 GMT   
 
   [ 1 post ] 

Similar Threads

1. LED display status 223, 552

2. aix-digest V3 #552

3. 552, logform failure

4. code 552 on RS6000 (non)boot

5. led-stat LED meter / parallel port?

6. LED is C32 then blank, no signal both in monitor and LED

7. led-stat LED meter / load generator

8. led on

9. IDE CDROM and HD LED light


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software