BAD ERROR: Corrupoted file system, JFS log bad IPL record, corrupted boot LV or defecitve disk. The VG rootvg could not be varied on. Most likely scenario is that the VGDA on the default boot drive (hdisk0) got hammered/corrupted. To resolve this problem, try the following:
1) Boot system in service mode. Either boot the system from boot diskettes or boot tape
2) Select option to perform system maintenance functions from the INSTALL and MAINTENANCE menu.
3) Enter the following command:/usr/sbin/getrootfs
hdisk0 from maintenance mode. If there are at least two PVs in the VG rootvg, if one fails to work with this
command, try any of the remaining PVs (eg, /etc/continue hdisk0 or /etc/continue hdisk1)
4) If the importvg command fails, as should the varyonvg command, then perform the following from the command line:
exportvg <VG_NAME>
EXAMPLE: exportvg vg2 removes LV references from ODM but wont write any info to VGDA
importvg -y <VG_NAME> <PV_NAME> EXAMPLE: importvg -y vg2 hdisk1 restores
ODM database from information read from VGDA
varyonvg -m1 <VG_NAME>
EXAMPLE: varyonvg vg2 This command will INSURE that the ODM database MATCHES the characteristics stored in the VGDA (syncs VGDA to ODM)
5) If no error messages are reported by importvg or varyonvg, then goto step ’11’
6) Execute the command: mount
7) If /dev/ram0 is the only mounted filesystem, try the following script entered interactively from the command line: EXAMPLE:
for VG rootvg – if it fails to varyon
for i in hd2 hd3 hd4
do
synclvodm rootvg $i
if [ “$?” -eq 0 ]; then
fsck -fp /dev/$i
fi
done
8) If there are no error messages from the synclvodm command or the fsck command, then mount the following file systems:
mount /dev/hd3 /tmp
mount /dev/hd2 /usr
mount /dev/hd4 /mnt
9) If there are no error messages from these mount commands, then goto step ’11’
10) If the previous step fails or the log redo process fails or indicates any filesystems with an unknown log device, then do the following 2 steps:
/etc/aix/logform /dev/hd8 ( Answer ‘y’ to the “Destroy /dev/hd8 (y)?” prompt )
LogForm will reformat the log logical volume. The next IPL will take a little longer.
11) Turn key to normal mode
12) Shutdown the system via the command shutdown -Fr. If this doesn’t appear to be working, type
the following at the command line:
sync; sync;
halt
13) If the problem still persists, consult your local SE before you attempt to RE-INSTALL your system.
If your system is hung, the user MUST initiate or force a dump of the kernel data via the following:
