Red Hat Bugzilla – Bug 197870
Kernel Panic after FC2 -> FC5 upgrade
Last modified: 2008-01-19 23:41:36 EST
I had an installed FC2 and I upgraded to FC5 via DVD.
The process went realy fine then at the first reboot I got the following error:
Red Hat nash version 5.0.32 starting
Kernel Panic - not syncing: Attempted to kill init!
I have two SATA disks with the partitions below:
sda1 - boot
sda2 - swap
sda3 - /export/home for user data
sdb1 - /
Can you help how to resolve?
I made the following chnaged in /etc/fstab
< /dev/sdb1 / ext3 defaults 1 1
< /dev/sda1 /boot ext3 defaults 1 2
>LABEL=/ / ext3 defaults 1 1
>LABEL=/boot /boot ext3 defaults 1 1
And in the grub.conf:
< kernel /vmlinuz-220.127.116.11-2054_FC5smp ro root=/dev/sdb1 rhgb quiet
> kernel /vmlinuz-18.104.22.168-2054_FC5smp ro root=LABEL=/ rhgb quiet
< kernel /vmlinuz-22.214.171.124-2054_FC5 ro root=/dev/sdb1 rhgb quiet
> kernel /vmlinuz-126.96.36.199-2054_FC5 ro root=LABEL=/ rhgb quiet
still NO success.
Check if this solves your problem:
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen