Description of problem:
latest kernel upgrade will not boot
Version-Release number of selected component (if applicable):
yum -y --skip-broken upgrade
Steps to Reproduce:
1.yum -y --skip-broken upgrade
2.reboot choose new kernel
3.pull your hair out unless you can boot kernel 220.127.116.11-0
system will not reboot have to choose kernel 18.104.22.168-0
error with Dracut stops system from booting
Same problem o myside.
I doing dmesg, I'm gettig an error o /dev/disk/by-uuid/1c51ab44-xxxxxx not found and which is my / (under RAID1)
make sure you have the latest updates for mdadm, device-mapper-libs and dracut installed, then remove and reinstall the kernel update.
Excatly what I've done ... And indeed solved the problem
ok, the requires: were bumped in the spec file ready for the next update so this shouldn't happen again when that comes out.
Same problem as smithbrooklyn88,
Downloaded fedora live cd, made fresh install and updated all packages including kernel. After reboot, cannot boot into new kernel, something like strace program output shows up on my screen. I have to choose 22.214.171.124-26.rc1.fc15.x86_64 kernel to boot properly.
To be more precise, I don't know if the problem is caused by dracut error, since I can't read trace output (too fast). I was wondering if there is a log file with that kind of error messages? If so, I can provide it.
Marcel, the ordering the updates are applied is currently broken. Follow the instructions in comment 2 and see if that fixes it for you.
It seems that it does not work for me. I check yum info for mdadm, device-mapper-libs and dracut and all packages are installed. Then tried yum update with the result, no packages to be updated. Then yum remove kernel-126.96.36.199, then yum update, kernel-188.8.131.52 was then reistalled. Computer restarted and tried to boot info new kernel - failed. (I do not have RAID)
(In reply to comment #8)
> restarted and tried to boot info new kernel - failed. (I do not have RAID)
If you do not have RAID, then you are not hitting this bug, which is entirely about RAID disks not being available during boot.
I'm not sure what kind of trace output you're talking about that's scrolling by too fast to read, can you be more specific?
(In reply to comment #9)
> (In reply to comment #8)
> > restarted and tried to boot info new kernel - failed. (I do not have RAID)
> If you do not have RAID, then you are not hitting this bug, which is entirely
> about RAID disks not being available during boot.
If so, then I'm sorry for misinterpreting the bug description.
> I'm not sure what kind of trace output you're talking about that's scrolling by
> too fast to read, can you be more specific?
after I choose new kernel in grub menu. I will add attachment soon.
Created attachment 524915 [details]
I can see these messages, but not all of them as the output printing is too fast.
Closing this bug out as the original issue was resolved.
Marcel, if you are still having problems on the 2.6.41.x updates for F15, please open a new bug.