Bug 884859 - missing initramfs post-upgrade makes system unbootable
Summary: missing initramfs post-upgrade makes system unbootable
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup-dracut
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 21:11 UTC by Gal Leibovici
Modified: 2013-09-30 23:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-06 23:10:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
FedUp log (1.60 MB, text/plain)
2012-12-06 21:11 UTC, Gal Leibovici
no flags Details

Description Gal Leibovici 2012-12-06 21:11:51 UTC
Created attachment 659033 [details]
FedUp log

Description of problem:
After running FedUp, I couldn't boot to fedora 18.
The grub entry was missing an initrd line, and when I inspected /boot/ there was no initramfs file for fedora 18 kernel. I had to build it with dracut, and add it to the grub entry.
Also, there was no upgrade.log on /var/log/

I had the nouveau modules blacklisted on older kernel lines, and it was also blacklisted on the new entry, as expected(?).
I had installed the nvidia modules, which I removed prior to creating the initramfs image.

The command I used to run fedup:
sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/fedora/linux/releases/test/18-Beta/Fedora/x86_64/os

Comment 1 Tim Flink 2012-12-06 21:20:08 UTC
Just to clarify some of the points here (Gal, correct me if I'm wrong on any of this):

 - Started with a F17 system which was using the propriatary nvidia drivers,  
   installed via rpmfusions akmod-nvidia package

 - Ran fedup-cli once, cancelled it due to a slow mirror and restarted

 - Rebooted and went through the 'System Upgrade'. No errors were noticed during 
   the upgrade

At this point, there was a F18 entry in grub which was booted by default but it led to a kernel panic very early in the boot process which was later found to be caused by the missing initrd line in grub2.cfg (there was no initramfs file for the f18 kernel, either)

Since the f17 entries were still bootable, Gal removed the nvidia packages, built an initramfs for the f18 kernel installed during upgrade and added it to the f18 boot entry in grub.

After going through this, the system is booting and seems to be working fine.

Comment 2 Tim Flink 2012-12-06 23:10:01 UTC
After much debugging of the post-upgrade system, it turns out that there was a power outage during the upgrade - very unfortunate timing.

Since this was external to the system, it's not a bug in fedup or fedup-dracut and I'm closing as NOTABUG.


Note You need to log in before you can comment on or make changes to this bug.