alt_disk_install reboot hangs at 0517
Dave
for a DR test.
It worked when the systems in question were running 4.3.2, but in the
last year they have upgraded to 5.2.
The alt_disk_install completes fine, then when you reboot (takes over
30 minutes to reboot this pig) it loads the kernel then hangs at 0517.
I have booted to a maintenance shell off the CD and ran fsck on all
filesystems, regenerated the /etc/filesystems file, verified the
bootlist is correct etc.
if I exit the maintenance shell, as it tries to mount the new
filesystems, it continuously scrolls the errormessage "/etc/getrootfs
killed (8135)"
the 8135 is the pid and that increments for about 300 numbers then
starts over... we have let it stay in this condition for 24 hours with
no change and hanging at the 0517 for 24 hours with no change...
Any ideas?
takar...@yahoo.com
0517 happens during ipl_varyon. It means that it (ipl_varyon)
completed successfully. The next thing in rc.boot 2 is fsck -f of
/dev/hd4 (/), and mounting it. Failure here should throw a 555 or 557.
If you are not getting the error codes on the LED, that suggests that
the fsck -f of /dev/hd4 never completes. Odd, if you can complete it
when booted from CD.
did you 'fsck -f' when booted from CD?
> Any ideas?
Dave
Today we tried again... this time the system stops at 0554 saying it
cannot find the boot device... booted to maintenance shell, verified
bootlist, bootlist is correct at hdisk2 for the first device... I have
also tried to do a bosboot -ad /dev/hdisk2 from the maintenance shell,
but the bosboot command cannot be found...
I guess my next test is to see how to restore files from a mksysb file
to a filesystem without doing an alt_disk_install
takar...@yahoo.com
> Yep... fsck -f on all the filesystems went fine...
> Today we tried again... this time the system stops at 0554 saying it
> cannot find the boot device... booted to maintenance shell, verified
> bootlist, bootlist is correct at hdisk2 for the first device... I have
> also tried to do a bosboot -ad /dev/hdisk2 from the maintenance shell,
> but the bosboot command cannot be found...
> I guess my next test is to see how to restore files from a mksysb file
> to a filesystem without doing an alt_disk_install
That 554 suggests a corrupted superblock or a corrupted Cu ODM
database. Not sure where you want to go from there, a corrupted Cu ODM
database might explain why the fsck works when booted from CD, but not
when booting from disk . . .
vlad...@gmail.com
here is what you can do:
Boot into service mode from the installation cds.
#fsck -y /dev/hd2
#fsck -y /dev/hd3
#fsck -y /dev/hd4
#fsck -y /dev/hd9var
#fsck -y /dev/hd10opt
#logform /dev/hd8
#exit -> filesystems will be mounted for service work.
#cd /dev
Is IPL_rootvg is missing?
Is ipldevice is a block file not a character file?
If so, follow these steps.
#rm ipldevice
#mknod IPL_rootvg c 10 0
#chmod 660 IPL_rootvg
#lslv -m hd5 -> this will tell you which hdisk your bootlv is located
on.
#ln rhdisk# ipldevice (rhdisk# will be the corresponding hdisk that
hd5 is located on)
#bosboot -ad /dev/hdisk# (hdisk# being the hdisk that hd5 is located
on)
#shutdown -Fr (to boot into normal mode. Remove the cd)
I know, that isn't what you would expect but seems like a bug in one of
the version of alt_disk_install...
Dave
group before mounting filesystems"
/etc/getrootfs[586]: 9526 Killed
/etc/getrootfs[586]: 9528 Killed
/etc/getrootfs[586]: 9530 Killed
/etc/getrootfs[586]: 9532 Killed
/etc/getrootfs[586]: 9534 Killed
/etc/getrootfs[586]: 9536 Killed
/etc/getrootfs[586]: 9538 Killed
/etc/getrootfs[586]: 9540 Killed
/etc/getrootfs[586]: 9542 Killed
/etc/getrootfs[586]: 9544 Killed
/etc/getrootfs[586]: 9546 Killed
/etc/getrootfs[586]: 9548 Killed
/etc/getrootfs[586]: 9550 Killed
/etc/getrootfs[586]: 9552 Killed
and the LED sits at 0C48