I have tried a few times to reload an mksysb image onto a eServer p5 type 9110-510; the image was loaded successfully through NIM with PULL action.
The problem is when the server starts, it hangs up with error code 0554 (can be seen on HMC). The image is AIX 5200-06.作者: yddll 时间: 2008-04-29 04:52
LED 552, 554, and 556 - Super block corrupted or corrupted customized ODM database
1. Boot to maintenance mode, to access the rootvg before mounting any file systems
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
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. If Your ODM database is corrupted. then Boot to maintenance mode, to access the rootvg before mounting any file systems
6. Mount the root and usr file system as follows:
mount /dev/hd4 /mnt
mount /usr
7. Copy system configuration to a backup directory:
mkdir /mnt/etc/objrepos/backup
cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup
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 boot disk 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 the system. If system does not come up, reinstall BOS.作者: richac 时间: 2008-04-29 10:46
Thanks my friend for such a detailed procedure!! It is appreciated!!!