| Summary: | kernel-PAE-3.1.2-1.fc16 fails to boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | pnelsonsr <wa-01> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-PAE-3.1.5-1.fc16.i686 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-15 18:34:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Just tried the newest kernel package kernel-PAE-3.1.4-1.fc16.i686 and this result in the same problem at the exact same spot.
I have 2 other fedora systems that I upgraded in the same way that are not having this problem, all of them are RAID1 but different hardware.
When I do the following:
yum remove kernel-PAE-3.1.4-1.fc16
yum update
as I watch the process I noticed that after the kernel installs there is a message:
grubby fatal error: unable to find a suitable template
not sure what that means to my problem but it's there nonetheless.
(In reply to comment #1) > grubby fatal error: unable to find a suitable template > > not sure what that means to my problem but it's there nonetheless. That is supposed to be fixed by the latest update to the 'grubby' package. Are you sure yours is up-to-date? yum update hasn't presented one. The version of grubby is: grubby-8.3-1.fc16.i686 But could this be associated to my kernel problem? When you boot the old kernel, does the status of the RAID1 device show that it's rebuilding after you log in? (check the file /proc/mdstat) To Comment #4 -> No it works fine boots without any problems or checking or fixing. Here is the output of cat /proc/mdstat: <---snip---> Personalities : [raid1] md127 : active raid1 sda[1] sdb[0] 244195328 blocks super external:/md0/0 [2/2] [UU] md0 : inactive sdb[1](S) sda[0](S) 6306 blocks super external:imsm unused devices: <none> <---snip---> I fixed the grubby problem as to eliminate it from a possibility. As this was an upgrade of F15 to F16 which changed from grub to grub2, there was a problem when a /boot/grub/grub.conf file existed and was zero file size or, as was in my case, had a kernel listed that was no longer installed. I simply move the file to grub.conf.old and then removed and re-installed kernel-PAE-3.1.4-1.fc16 and sure enough the grubby error was no longer there. I also reinstalled bash with ‘yum reinstall bash’ as it was reported that fedora install messed something up with /etc/shells creation and that this might cause strange problems. I was hopeful but when I tried to boot into the kernel-PAE-3.1.4-1.fc16 I had the system hang at the exact same spot mentioned in the original post. I had installed a new kernel package (kernel-PAE-3.1.5-1.fc16.i686) and tried to boot it and it was successful! I then did a yum update and there was an even newer kernel package (kernel-PAE-3.1.5-2.fc16.i686) so I installed that and tried to boot and it also was successful. So what ever was causing my boot issue on this system seems to have been fixed. The kernels I had problems with were (at least): kernel-PAE-3.1.2-1.fc16.i686 kernel-PAE-3.1.4-1.fc16.i686 Issue can be closed. |
Version-Release number of selected component (if applicable): kernel-PAE-3.1.2-1.fc16 fails kernel-PAE-3.1.0-7.fc16 works How reproducible: completely Steps to Reproduce: 1. upgrade fedora15 to fedora16 2. to put things in text boot mode: vi /etc/default/grub -> remove rhgb text grub2-mkconfig -o > /boot/grub2/grub.cfg ln -sf /lib/systemd/system/runlevel3.target /etc/systemd/system/default 3. update packages: yum update 4. reboot the system and watch Actual results: system hangs Expected results: system boots Additional info: This is a RAID1 system doing mirroring. The fedora15 system was a fresh install. The fedora16 system was an upgrade from said fedora15 system. Let fedora15 install set the size of partitions and logical volumes. Encrypted the file systems during fedora15 install. Went to text boot to try and figure out where it was hanging at. When I select the 3.1.2-1 kernel it boots up just past the ramdisk and then asks for the encrypted filesystem password. I enter that and the cursor goes to the next line and blinks. The HD light on the front of the computer turns on and stays on. I've waited for 30 minutes (thinking that maybe the RAID1 had to resync). Rebooting and selecting the working 3.1.0-7 kernel, I enter the password and it starts to boot normally immediately.