Red Hat Bugzilla – Bug 599582
Kernel not installed during upgrade with /boot on separate partition
Last modified: 2010-06-03 13:31:00 EDT
Description of problem:
The 'kernel' package wasn't installed correctly into my /boot partition when I used preupgrade to upgrade from F12 to F13.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Put /boot on separate partition (set the 'noauto' option in /etc/fstab)
2. Run `preupgrade`
Kernel installed into root partition (the one it identified for the upgrade) and erased all old /lib/modules/* directories belonging to Fedora-installed kernels. After the install, the old kernels still on the /boot partition couldn't find and modules it needed.
New kernel installed into /boot (or at least prompted to mount it). Old kernels not wiped out.
Keeping around the old kernel module directories would have let me boot up successfully at least so I could fix it myself. Admittedly this is something a casual user probably wouldn't do, so I'm not suggesting a real clever fix.
(In reply to comment #0)
> ... (set the 'noauto' option in /etc/fstab)
Why did you do this?
(In reply to comment #1)
> (In reply to comment #0)
> > ... (set the 'noauto' option in /etc/fstab)
> Why did you do this?
I don't want my /boot partition mounted automatically. If you're asking why I don't want it mounted all the time, I guess I don't want to accidentally clobber my kernel or grub configuration. It doesn't really need to be mounted except when there's a kernel to update.
(In reply to comment #2)
> It doesn't really need to be mounted except when there's a kernel to update.
So how does yum mount /boot when you install a kernel update?
(In reply to comment #3)
> So how does yum mount /boot when you install a kernel update?
It doesn't. I see a kernel update and mount /boot before performing the update.
(In reply to comment #4)
> It doesn't. I see a kernel update and mount /boot before performing the
Then you need to do the same with preupgrade. Sorry, closing.
(In reply to comment #5)
> Then you need to do the same with preupgrade.
How exactly is one supposed to do that in anaconda? Did I need to search the Fedora wiki for boot parameters to make a console available? There was no console available after the reboot; anaconda just started updating all the installed packages.