This document applies to AIX 3.1 or 3.2. It contains instructions for using the bosboot command to recover from a corrupted boot logical volume.
WARNING: Please do not use this document if the system is a /usr client, diskless client, dataless client, or you are not running AIX Version 3.
During boot up with AIX 3.1 or 3.2, a hang on LED 517 or the LED sequence 888-103-207-299 or 888-103-208-299 may be caused by a corrupted boot logical volume.
There may be other symptoms which are also caused by a corrupted boot logical volume. If you suspect that your boot logical volume is corrupt, follow the steps below.
WARNING: If you boot a 3.2 system with 3.1 media, or boot a 3.1 system with 3.2 media, you will not be able to use the standard scripts (getrootfs or /etc/continue) to bring your workstation into full Maintenance mode. |
Moreover, performing the scripts on a 3.1 system with 3.2 boot media may actually remove some files and prevent your system from booting successfully in Normal mode until missing files (/etc/mount and /etc/umount) are replaced on the disk.
NOTE:
Follow the prompts to the installation/maintenance menu.
FOR AIX 3.2.4 OR LATER
Run:
getrootfs
The output indicates the disk that should be used with getrootfs in the next step.
FOR AIX 3.1 TO 3.2.3E
Run:
lqueryvg -Atp [hdisk#] | grep hd5
for each hdisk# (hdisk0, hdisk1, etc.) until you get output that looks like the following:
00005264feb3631c.2 hd5 1
The exact output will be different but will follow the form:
large_number.x hd5 1
You may find that more than one disk with this output. These will all be disks which belong to the rootvg volume group. You may use any of the disks identified to be in rootvg in the following step.
For AIX 3.1 only, run:
/etc/continue [hdisk#]
For AIX 3.2 only, run:
getrootfs [hdisk#]
If you receive errors from /etc/continue or getrootfs, do not continue with this procedure. Correct the problem causing the error.
ODMDIR=/etc/objrepos
lslv -m hd5WARNING:Please do not proceed further if the system is a /usr client, diskless client, or dataless client.
syncvg -v rootvg synclvodm -v rootvg bosboot -a -d/dev/[hdisk#] sync; sync
reboot
[ Doc Ref: 90605202614652 Publish Date: Oct. 16, 2000 4FAX Ref: 2463 ]