[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Fedora Core 2 upgrade FAILURE
- From: dhollis davehollis com
- To: Development discussions related to Fedora Core <fedora-devel-list redhat com>, Luciano Miguel Ferreira Rocha <strange nsk no-ip org>
- Cc: Development discussions related to Fedora Core <fedora-devel-list redhat com>
- Subject: Re: Fedora Core 2 upgrade FAILURE
- Date: Thu, 3 Jun 2004 17:57:04 -0400
Quoting Luciano Miguel Ferreira Rocha <strange nsk no-ip org>:
> On Thu, Jun 03, 2004 at 10:44:44AM -0700, Richard Emberson wrote:
> > root (hd0,0)
> > kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/
> > initrd /initrd-2.6.5-1.358.img
> > boot
>
> Try without initrd and with root pointing to a device file
> root (hd0,0)
> kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2
> boot
> (or wherever is your root partition)
>
>
use:
kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2 single
(note the addition of single to go into single user mode)
That should get you booted and to a command prompt. Apparently, the kernel was
upgraded, but the postinstall failed to do it's bit and add itself to grub,
create the initrd etc. If you can get to the command prompt, run this:
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --mkinitrd --depmod
--install 2.6.5-1.358
[ -x /usr/sbin/hardlink ] && /usr/sbin/hardlink -c /lib/modules/2.6.* || :
That's taken straight from the RPM. It should add an entry to grub, create the
initrd, and you should be in good shape.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]