Bug 470166
| Summary: | FC9 fails to boot after yum update to 2.6.26.6-79.fc9.x86_64 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Todd Gould <fedora> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 9 | CC: | ardashev, dcantrell, fedora, hdegoede, jimm, katzj, kernel-maint, pjones, quintela, vladimir, wtogami | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | ia64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-07-14 14:24:49 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Todd Gould
2008-11-06 04:09:11 UTC
I'm having a similar problem with both 2.6.26.6-79.fc9.x86_64 and 2.6.27.5-37.fc9.x86 kernels. The only difference is I get the error: Buffer I/O error on dev sda3 logical block 1092467968 (logical block 1092467968?. The box is set up as a raid 0 and works fine with the install kernel (2.6.25-14). something changed during .26 -> .27 which has upset mkinitrd. For some reason it doesn't set up md devices any more. Can you attach the initrd for the new and old kernels? This has nothing to do with drivers becoming built-in. It's not even a 2.6.27 kernel problem... (In reply to comment #4) > This has nothing to do with drivers becoming built-in. It's not even a 2.6.27 > kernel problem... Correct, this appears to be a problem with 2.6.26.6-79.fc9.x86_64 following a yum update from a perfectly functioning 2.6.26.5-45.fc9.x86_64 system as described in my original submission. I will attach initrd-2.6.26.5-45.fc9.x86_64.img and initrd-2.6.26.6-79.fc9.x86_64.img as requested anf will greatly appreciate any and all help in getting this resolved. Created attachment 324265 [details]
Original (pre yum update) initrd file
Original (pre yum update) initrd file
Created attachment 324266 [details]
Post yum update initrd
Post yum update initrd
When booting 2.6.26.5-45.fc9.x86_64 kernel does dmraid segment fault? Mine does--when I stated above that: "The box is set up as a raid 0 and works fine with the install kernel (2.6.25-14)" I lied. This is true only after I do a dmraid -ay. This appears to be due to the fact the ids in /dev/mapper differ on each boot (at least they differ from what's in fstab). (In reply to comment #8) > When booting 2.6.26.5-45.fc9.x86_64 kernel does dmraid segment fault? Mine > does--when I stated above that: "The box is set up as a raid 0 and works fine > with the install kernel (2.6.25-14)" I lied. This is true only after I do a > dmraid -ay. This appears to be due to the fact the ids in /dev/mapper differ > on each boot (at least they differ from what's in fstab). Booting 2.6.26.5-45.fc9.x86_64 works flawlessly for me. I ave problems after a yum update to 2.6.26.6-79.fc9.x86_64.... ok, I have same problem with fake raid on intel dp35dp mobo. read my comments 30 and 32 in bug 313411 https://bugzilla.redhat.com/show_bug.cgi?id=313411 would people stop breaking stuff that works ??? Hello, I was have same the problem. When this will be fixed? Thank you. 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 Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |