Bug 851733

Summary:	Fedora 16->17 upgrade left /boot empty
Product:	[Fedora] Fedora	Reporter:	Roland Roberts <roland>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-24 22:02:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roland Roberts 2012-08-24 21:44:58 UTC

Description of problem:
System was a fully up-to-date Fedora 16 system. 
After the upgrade, reboot fell into a dracut shell immediately after mounting the root filesystem. The last messages before getting a dracut prompt are:

 cannot find init!
 please check to make sure you specified a valid root filesystem!

At that point, the root file system IS mounted, but /boot is empty. Running "lvm vgscan -ay" to insure all volumes are activated is not helpful as exiting dracut still results in a kernel panic.

Version-Release number of selected component (if applicable):


How reproducible:

Don't know what triggered empty /boot. 

Steps to Reproduce:
1. "Normal" upgrade from F16->F17 via preupgrade
2.
3.
  
Actual results:


Expected results:


Additional info:

I have booted using live media and am trying to figure out a recovery strategy that doesn't involve copying my data to a new drive and installing clean :-(

parted shows the drive as having three partitions, bios_grub, boot, and lvm.

Comment 1 Roland Roberts 2012-08-24 21:48:31 UTC

Okay, it's not that /boot is empty, it's not being mounted at that point. It is present in the EFI partition and I can mount it. My misunderstanding.

Comment 2 Roland Roberts 2012-08-24 22:02:31 UTC

Okay, after continuing to browse, I realized this is actually a duplicate of 804913. The same solution works, adding rd.lvm.lv=vg_xyzzy/usr as I also have /usr as a separate partition.

*** This bug has been marked as a duplicate of bug 804913 ***