[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Kernel panic: No init found
From: |
grenoml |
Subject: |
Re: Kernel panic: No init found |
Date: |
Fri, 28 Feb 2003 20:13:16 -0800 (PST) |
SOLVED - see end of document.
--- grenoml <address@hidden> wrote:
>
> --- grenoml <address@hidden> wrote:
> > Well hi again! Hey Dave Balazic thanks for your comments on my
> > 'GRUB
> > hangs' post. Got a little bit better grip on GRUB now.
> > I been making attempts at getting one of my Linux machines to
> boot
> > from a /boot partition rather than from a boot directory on /. I
> > have
> > two hard drives: hdc (set as BIOS boot device) and hde (my / is
> > here).
> > I made and configured a /boot partition on hdc and it has all the
> > boot
> > files. I have my /boot/grub/grub.conf configured as follows:
> >
> > # grub.conf generated by anaconda
> > default=0
> > timeout=10
> > splashimage=(hd0,1)/grub/splash.xpm.gz
> > title Red Hat Linux (2.4.18-14)
> > root (hd0,1)
> > kernel /vmlinuz-2.4.18-14 ro root=/dev/hde1
> > initrd /initrd-2.4.18-14.img
> > title DOS
> > rootnoverify (hd0,0)
> > chainloader +1
> >
> > I did a grub-install /dev/hdc and rebooted. Good thing is that I
> get
> > the GRUB splash menu. The bad thing is that I'm getting a kernel
> > panic
> > on mounting the root filesystem. Here are the boot messages:
> >
> > ...
> > Mounting /proc
> > (all the LVM stuff gets activated successfully - / is not under LVM
> > BTW)
> > Mounting root filesystem
> > kjournald starting. Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with ordered data mode.
> > pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> > umount /initrd/proc failed: 2
> > Freeing unused kernel memory: 212K freed
> > Kernel panic: No init found. Try passing init= option to kernel
> > ---
> >
> > Tried passing init=/bin/sh to see if / was really there somehow -
> > no
> > dice. It looks as though it may have mounted the filesystem but
> then
> > pivotroot doesn't succeed for some reason. I've been working with
> > this
> > for a while without any luck so I thought I would post what I'm
> > seeing
> > in hopes that maybe someone might have some pointers for me. :-)
> >
> >
> > Regards,
> > Gerry Reno
> >
> >
>
> Some followup. I was believing that perhaps the / ext3 journal might
> have been corrupted somehow so I removed the journal, changed the
> entry
> in /etc/fstab to ext2, crossed my fingers and rebooted but no luck -
> same errors. The odd thing is that the messages still showed it as
> trying to mount / as ext3. Isn't /etc/fstab controlling here? So I
> went back to rescue mode and used tune2fs to reinstall the journal
> and
> changed /etc/fstab back to ext3. I just can't see what this problem
> is
> with mounting root. In rescue mode the / partition is just fine and
> it
> gets mounted as ext3 under /mnt/sysimage. I can access all the files
> on it so it seems strange that it won't mount during the regular
> boot.
> Anyone seen this before?
>
> Thanks,
> Gerry Reno
>
>
OK, here's what finally worked for me. I rebuilt initrd in rescue
mode chrooted into the /mnt/sysimage. Specifically, once in chroot, cd
to /boot and move the current initrd file out of the way and then
mkinitrd -v -f initrd-KERNEL-VERSION KERNEL-VERSION. Substitute your
kernel version in the last command. I rebooted and the system came up
without error. So far it seems to be ok.
Regards,
Gerry Reno
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/