boot error for kernel-2.6.19-1.2288.fc5
Is there any known problem with the latest kernel? Few days ago I upgraded my kernel (like a 100 times before) from kernel-2.6.18-1.2257.fc5 to kernel-2.6.19-1.2288.fc5 via yum. Attempting to boot the latter ends up in a kernel panic. The former still does work when booted via my grub menu (my rescue for the moment!).
Ok, for the 2.6.19-1.2288 I get these messages/errors:
AMD Athlon 64 X2 Dual Core 4600 on a A8N32 SLI Deluxe board
Fedora Core 5 (x86_64)
Any hints, anyone?
Moved: This thread is more suitable in the Fedora forum and has been moved accordingly to help your thread/question get the exposure it deserves.
I had the same problem I just used yumex to remove the new kernel than reinstalled it, worked fine when I rebooted
Thanks for your reply, DCOH!
As there was no reply to my post for quite some time, I assumed it had to be an error specific to my box. So I had actually done the same as you earlier: removing kernel 2.6.19 and reinstalling it again (via yum). And it worked for me too!!!
Though it bothered me that there was no obvious reason for the previous error. So I checked /boot again, and - bingo! One file differs in size (increase from 1192375 to 1983731 bytes). I wonder how that could slip through:
I'm not sure about an integrity check by yum but it does verify the download. When I reinstalled the kernel with yumex the kernel showed update so there my have been a problem with the kernel.
boot error for kernel-2.6.20.xxxx
I have Fedora and had the same problem when updating from 2.6.18.xxxx to 2.6.20.xxxx: I could not boot with the new kernel and got the same messages as below:
Booting the kernel.
Red Hat nash version 5.0.32 starting
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
kernel panic - not syncing: Attempted to kill init!"
But I could boot with the older one. So with "Add/Remove Software" I removed the 2.6.20 kernel and then added it back to my system and this time everything was fine and I could boot with the new kernel! Now I am worried about the other updated files/modules, could other files have been corrupted during the update process? How to know that? Of course not using them or their associated programs will not show anything but what if this happens weeks from now, how to associate potential issues to the upgrade problem?
Question to Linux experts: is a kernel built (compiled/linked/etc.) on the local computer during the update process, or is it just a file that gets downloaded? The former would mean that the build was not correct; the latter would mean that the file was not downloaded properly. In any case are they other files that could have been build erroneously or downloaded without keeping their integrity?
|All times are GMT -5. The time now is 04:39 AM.|