pivotroot: pivot_root (/sysroot,/sysroot/initrd) failed 2
<frees 236K of memory>
kernel panic: no init found. try passing init= option to kernel
Dead in the water from there.
Any other suggestions? Anyone?
Does anyone know what's happening here?
Michael
--- Rick Stevens <rste...@vitalstream.com> wrote:
> ... your /boot/grub/grub.conf
> should have this sort of thing in it:
I have this (amongst other lines):
title Red Hat Linux (2.4.9-21)
root (hd0,0)
kernel /vmlinuz-2.4.9-21 ro root=/dev/hda15
initrd /initrd-2.4.9-21.img
I have a separate /boot partition on /dev/hda1.
My / partition is /dev/hda15.
I only have a /etc/lilo.conf.anaconda which looks like below...
> and/or your /etc/lilo.conf should have:
image=/boot/vmlinuz-2.4.9-21
label=linux
initrd=/boot/initrd-2.4.9-21.img
read-only
root=/dev/hda15
I use Grub as the boot loader, so do I need a lilo.conf
because there's not one there. Do I need that?
It's well after the grub menu when I get the kernel panic given below.
Michael
--- Rick Stevens <rste...@vitalstream.com> wrote:
> Michael Oatman wrote:
> > Hi,
> >
> > On boot, right after the root filesystem is mounted,
> > I'm getting a kernel panic and it hangs at:
> >
> > pivotroot: pivot_root (/sysroot,/sysroot/initrd) failed 2
> > <frees 236K of memory>
> > kernel panic: no init found. try passing init= option to kernel
> >
> > I'm using Grup to boot 2.4.9-21 kernel from
> > /boot/initrd-2.4.9-21.img.
>
> Huh? The initrd isn't the kernel image, it's the ramdisk image of
> modules that must be loaded to get at your root filesystem. The
> kernel image would be /boot/vmlinuz-2.4.9-21.
Okay.
> Assuming your root filesystem is on /dev/hda1, your /boot/grub/grub.conf
> should have this sort of thing in it:
>
> title Red Hat Linux (2.4.9-21)
> root (hd0,0)
> kernel /boot/vmlinuz-2.4.9-21 ro root=/dev/hda1 hdd=ide-scsi
> initrd /boot/initrd-2.4.9-21.img
>
> and/or your /etc/lilo.conf should have:
>
> image=/boot/vmlinuz-2.4.9-21
> label=linux
> initrd=/boot/initrd-2.4.9-21.img
> read-only
> root=/dev/hda1
>
> Replace "/dev/hda1" with the partition your root filesystem is on.
> ----------------------------------------------------------------------
> - Rick Stevens, SSE, VitalStream, Inc. rste...@vitalstream.com -
> - 949-743-2010 (Voice) http://www.vitalstream.com -
> - -
> - "I'd explain it to you, but your brain might explode." -
> ----------------------------------------------------------------------
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
_______________________________________________
Redhat-install-list mailing list
Redhat-in...@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-install-list
Look and see if you have the directory "initrd" in your root directory.
If not create it. If the /initrd directory is missing it will cause the
problem you have.
Regards,
Jim H
Any idea why the /initrd directory went missing
after a power outage and subsequent fsck's on all
partitions while unmounted?
My entire Apache & Apache Toolbox installation
also went missing somehow. There's no httpd in
services, either. Think that might be somehow
related? Any idea how to prevent this in the
future? I'm restoring from backup now. Or would
anyone recommend a reinstall?
Michael
--- J Hayward <jimha...@earthlink.net> wrote:
> Look and see if you have the directory "initrd" in your root directory.
> If not create it. If the /initrd directory is missing it will cause the
> problem you have.
>
>
> Regards,
> Jim H
>
>
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-in...@redhat.com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
_______________________________________________
Linux caches it's writes. Now the updates are dma'ed to disk. A dma
activity says to take x data from memory and write, starting a loc y,
onto the disk.
If you're lucky, and you were, the power hit munged the
dma write to address lines and scrambled the disk partition information.
Prevention, buy an uninterruptable powersupply.
Here, feel free to use my search engine
http://www.google.com/search?hl=en&q=linux+uninterruptable+power+supply