Bug 494867

Summary: Rawhide i386 fails to boot - not syncing: No init found. Try passing init= option to kernel.
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, ffesti, jnovy, jturner, masao-takahashi, pjones, pmatilai, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-13 17:56:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 446452, 494832    
Attachments:
Description Flags
Boot log none

Description James Laska 2009-04-08 13:26:38 UTC
Created attachment 338707 [details]
Boot log

Description of problem:

Unable to boot rawhide/i386.  The boot process fails with:

Failed to execute /init
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

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

anaconda-11.5.0.40-1.i586.rpm  kernel-2.6.29.1-52.fc11.i586.rpm
glibc-2.9.90-12.i586.rpm       rpm-4.7.0-0.beta1.9.fc11.i586.rpm
glibc-2.9.90-12.i686.rpm

How reproducible:


Steps to Reproduce:
1. Attempt to boot the boot.iso or pxeboot images from rawhide
  
Actual results:

See attached dmesg.log for complete boot log

Expected results:

Anaconda stage#1 should start


Additional info:

Comment 1 Panu Matilainen 2009-04-13 12:41:23 UTC
Possibly related to glibc.i586 breakage but unlikely have anything to do with rpm directly. Passing on to anaconda for now...

Comment 2 Chris Lumens 2009-04-13 15:35:06 UTC
Are you still seeing this?  I'm guessing not, since it looks like you're hitting the dbus thing now.

Comment 3 James Laska 2009-04-13 15:38:25 UTC
Thanks, I was going to revisit this once I got a little further into the install.  But you are right, I'm observing systems starting loader so I believe we can close this issue.  

I still have no idea what the root cause was?  Any thoughts?

Comment 4 Chris Lumens 2009-04-13 17:56:23 UTC
This definitely sounds like the glibc problems people were seeing the other day.  I do believe init is dynamically linked now and problems with the version of glibc on the initrd would lead to problems starting init.