2.6 kernel upgrade fail...
From: Joe Szilagyi (lists_at_szilagyi.us)
Date: 12/29/03
- Previous message: Sites, Brad: "RE: How to recover root password"
- Next in thread: Sean Estabrooks: "Re: 2.6 kernel upgrade fail..."
- Reply: Sean Estabrooks: "Re: 2.6 kernel upgrade fail..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: <redhat-list@redhat.com> Date: Mon, 29 Dec 2003 10:59:46 -0500
Hello, I tried to upgrade my RH 9 box's kernel to 2.6, and upon reboot it
failed to come back. When I rebooted again and went to terminal grub only
offered the original 2.4 kernel, not the new one. On top of it, the box
won't read my keyboard as far as I can tell now. Once the countdown
finishes it boots, but then dies loading the kernel with this error:
mount: error 19 mounting ext3
pivotroot: pivot_root (/sysroot,/sysroot/initrd) failed: 2
mount: /initrd/proc failed: 2
seeing unused kernel memory: 232k found
kernel panic: No init found. Try passing init= option to kernel
Any easy fix for this?
Regards,
Joe
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
- Previous message: Sites, Brad: "RE: How to recover root password"
- Next in thread: Sean Estabrooks: "Re: 2.6 kernel upgrade fail..."
- Reply: Sean Estabrooks: "Re: 2.6 kernel upgrade fail..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re:SOLVVED vinum crashes the Box... WRONG POSTING
... vinum crashes the Box by using more then ten disks on ... > With this configuration
vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger
now... ... >> while devfs rules works for those, but they vanish on reboot. ...
(freebsd-stable) - [SLE] bad: scheduling while atomic! (Re: [SLE] Upgrade to Kernel 2.6.5.7-108-default causes looping
... I've upgraded to Kernel 2.6.5.7-108-default through Yast on SuSE 9.1 which causes the
following messages when rebooting: ... Upgrading to Kernel 2.6.5.7-108-default through Yast
causes an endless looping message when I reboot my system after the install. ... Any suggestions
on how to proceed, or am I missing something with the Kernel 2.6.5.7-108 upgrade? ... (SuSE) - SUMMARY: device database locked by cluster member
... A reboot did clear up the problem. ... kernel, probably one of the interactions
between the ... and get a crash dump (or how to force a panic, ... > Cluster
shared component has no entry in the cluster database. ... (Tru64-UNIX-Managers) - Re: [SLE] Upgrade to Kernel 2.6.5.7-108-default causes looping error message
... > upgrade that caused the problems... ... >The repeating message scrolls
to fast for me to read the message. ... I am not able to locate it in a log after the next reboot
or when rebooting with a rescue disk. ... >Any suggestions on how to proceed, or am I missing
something with the Kernel 2.6.5.7-108 upgrade? ... (SuSE) - instant reboot when trying to load recent RELENG_5 kernel
... but it still happens on a kernel compiled with CPUTYPE ... instantly reboot
with ACPI enabled. ... port ... can't assign resources ... (freebsd-current)