boot after kernel panic
Rick Stevens
rstevens at vitalstream.com
Tue Feb 13 01:58:57 UTC 2007
On Mon, 2007-02-12 at 18:19 -0600, Luis Rodríguez wrote:
> i check the options you tell me...
>
> about fsck
>
> i rescue boot and the filesystem put in /mnt/sysimage
>
> so
>
> is safe to ran fsck /mnt/sysimage/root
>
> or need to umount and ran fsck over dev hd?
Take note of what's mounted as /mnt/sysimage, then unmount it and run
fsck against it. Your fsck should look like:
fsck -y /dev/hda1
The "hda1" may be "hda2" or some other name. If it checks out, reboot
again in rescue mode and let the volume mount again. You need to know
what kernel version you're running and you'll need to run the following
commands:
# chroot /mnt/sysimage
# cd /boot
# mkinitrd -f -v initrd-(kernel-version).img (kernel-version)
# exit
# exit
Replace "(kernel-version)" with the version of the kernel you normally
run on that machine. The first "exit" will exit the chroot environment,
the second exits the rescue mode. Pop out the CD and see if it'll boot.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- All generalizations are false. -
----------------------------------------------------------------------
More information about the Redhat-install-list
mailing list