Description of problem: the latest kernel I can boot is kernel-2.6.22.7-57.fc6. all the others (incuding kernel-2.6.24.5-85.fc8) fail. Version-Release number of selected component (if applicable): kernel-2.6.22.7-57.fc6 -- works kernel-2.6.24.5-85.fc8 -- does NOT How reproducible: always Steps to Reproduce: 1.reboot 2.select 2.6.24 3.see it fail with messages about disk problems. Actual results: boot failure Expected results: boot success Additional info: I appended "options libata ignore_hpa=1" to /etc/modprobe.conf as per http://fedoraproject.org/wiki/Bugs/F8Common but it did not help. I am not sure what information could be useful, so I am attaching the dmesg output from a successful boot. I don't know how to get to the messages from a failed boot (especially since I think the boot fails because of disk problems, so it probably does not write anything).
Created attachment 305322 [details] dmesg output
Can you attach a null modem cable to the system in question and add this: console=ttyS0,19200n8 or simmilarly configured serial console directive to your kernel command line? Then you could attach an extra pc and monintor the boot process (as well as record it via a serial log in kermit/minicom/etc) on that system. Thanks!
I don't know what a "null modem cable" is, and I don't have another linux PC.
I can take a picture of the frozen screen though :-) sorry...
Created attachment 305570 [details] screenshots of the failed boot: last
Created attachment 305571 [details] screenshots of the failed boot: last -1
Created attachment 305572 [details] screenshots of the failed boot: last -2
Created attachment 305573 [details] screenshots of the failed boot: last -3
Created attachment 305575 [details] screenshots of the failed boot: last -4
Created attachment 305576 [details] screenshots of the failed boot: last -5
Created attachment 305577 [details] screenshots of the failed boot: last -5
Created attachment 305580 [details] screenshots of the failed boot: last -6
Created attachment 305581 [details] screenshots of the failed boot: last -7
Created attachment 305583 [details] screenshots of the failed boot: last -8
Created attachment 305584 [details] screenshots of the failed boot: last -9
Created attachment 305585 [details] screenshots of the failed boot: last -10
Created attachment 305586 [details] screenshots of the failed boot: last -11
Created attachment 305588 [details] screenshots of the failed boot: last -12
Created attachment 305589 [details] screenshots of the failed boot: last -13
Created attachment 305590 [details] screenshots of the failed boot: last -14
Created attachment 305592 [details] screenshots of the failed boot: last -15
Created attachment 305594 [details] screenshots of the failed boot: last -16
Created attachment 305595 [details] screenshots of the failed boot: last -17
Created attachment 305597 [details] screenshots of the failed boot: last -18
Created attachment 305598 [details] screenshots of the failed boot: last -19
Created attachment 305599 [details] screenshots of the failed boot: last -20
Created attachment 305600 [details] screenshots of the failed boot: last -21
Created attachment 305602 [details] screenshots of the failed boot: last -22
Created attachment 305603 [details] screenshots of the failed boot: last -23
Created attachment 305604 [details] screenshots of the failed boot: last -24
the attachments go in the reverse chronological order with approx. half screen overlap - I did a shift-pagedown between shots. so, the first attachment (names "last") contains the "boot failed message". the next on ("last -1") is half screen up from it.
Umm, are you trying to boot F8 kernels on FC6?
the system is fc9. I upgraded from rh9 to fc1 to fc2->3->4->5->6->7->8->9 by downloading the fedora-release rpm by ftp, doing "rpm -U fedora-release", and then "yum -y upgrade" overnight. it worked like a charm until some time in fc6 a regular "yum update" brought in a kernel that wouldn't boot. Let me repeat: the problem first surfaced NOT after an upgrade from fc6 to fc7, but during a regular update of fc6. neither fc7 nor fc8 nor fc9 (3 days ago) helped.
It looks like your grub configuration has references to /dev/hda3, etc. which won't exist in newer Fedora kernels since libata is being used. These should really be changed to refer to the disk labels instead of specific device nodes.
indeed, /boot/grub/grub.conf says: title Fedora (2.6.25.10-86.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.10-86.fc9.i686 ro root=/dev/hda2 rhgb initrd /initrd-2.6.25.10-86.fc9.i686.img title Fedora Core (2.6.22.7-57.fc6) root (hd0,0) kernel /vmlinuz-2.6.22.7-57.fc6 ro root=/dev/hda2 rhgb initrd /initrd-2.6.22.7-57.fc6.img what should I replace /dev/hda2 with? I also have /dev/hd* in fstab: /dev/hda2 / ext3 defaults 1 1 /dev/hda1 /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 /dev/hda5 /home ext3 defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda6 /usr/local ext3 defaults 1 2 /dev/hda3 swap swap defaults 0 0 /dev/hdb1 /extra ext3 defaults,ro 0 0 do I need to replace these too? thanks!
You really need to label the filesystems and then change /dev/whatever to LABEL=whatever in fstab. You might also have to make your own initrd because the mkinitrd in FC6 may not work with newer kernels.
my fstab now looks like this: ==================================================================== #/dev/hda2 / ext3 defaults 1 1 LABEL=/ / ext3 defaults 1 1 #/dev/hda1 /boot ext3 defaults 1 2 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 #/dev/hda5 /home ext3 defaults 1 2 LABEL=/home /home ext3 defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 #/dev/hda6 /usr/local ext3 defaults 1 2 LABEL=/usr/local /usr/local ext3 defaults 1 2 /dev/hda3 swap swap defaults 0 0 ==================================================================== how do I modify the "kernel" line? kernel /vmlinuz-2.6.25.10-86.fc9.i686 ro root=/ rhgb ???
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
upgrading to fc10 fixed the problem.