Bug 480213

Summary: pungi initrd anaconda failed to boot
Product: [Fedora] Fedora Reporter: xxartemisxx
Component: pungiAssignee: Dave Cantrell <dcantrell>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 9CC: dcantrell, dsd
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-03-16 10:10:37 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:
Attachments:
Description Flags
kickstart
none
pungi log
none
kernel
none
initrd.img none

Description xxartemisxx 2009-01-15 18:27:05 UTC
Created attachment 329121 [details]
kickstart

Description of problem:

Hi,
I'm creating a DVD with pungi.
This DVD doesn't boot.


failed to execute /init
kernel panic - not syncing : no init found. try passing init= option to kernel.




pungi command:
pungi -c /dir/conf.ks --destdir=/dir/test --name=test --vers=1 --nosource --nosplitmedia --force

I try with a different initrd.img in isolinux and anaconda run. The problem look like coming from isolinux/initrd.img from buildinstall of anaconda.

any idea ?
thanks 

Version-Release number of selected component (if applicable):
on fedora 9 : 2.6.27.9-73.fc9.i686
pungi: 1.2.18.1
anaconda: 11.4.0.83-1.i386

How reproducible:
always


Steps to Reproduce:
1.
create a small kickstart

2.
______________________________________________________________________
pungi -c /dir/conf.ks --destdir=/dir/test --name=test --vers=1 --nosource --nosplitmedia --force
______________________________________________________________________
3.
  boot the dvd
Actual results:
failed to execute /init
kernel panic - not syncing : no init found. try passing init= option to kernel.


Expected results:
DVD boot

Additional info:
was working before update.

Comment 1 Jesse Keating 2009-01-16 00:19:21 UTC
Can you attach the log file from this compose?  It shoudl be in /d/r/test/logs/

Comment 2 xxartemisxx 2009-01-16 07:52:33 UTC
Created attachment 329168 [details]
pungi log

Comment 3 xxartemisxx 2009-01-16 07:58:26 UTC
I was running this kickstart in september and it run perfectly.
Now i need to update the iso.
So i create a server from scratch with:
"yum update -y && yum install pungi && reboot"

And now the created iso with the same kickstart doesn't boot ....

did i miss something ?

thanks,

Comment 4 Jesse Keating 2009-01-21 00:16:40 UTC
Hrm, I don't see anything relevant in the logs.  Can you attach the kernel and initrd.img that were generated?

Comment 5 xxartemisxx 2009-01-21 07:19:28 UTC
Created attachment 329557 [details]
kernel

Comment 6 xxartemisxx 2009-01-21 07:27:10 UTC
Created attachment 329558 [details]
initrd.img

Comment 7 xxartemisxx 2009-01-21 07:34:27 UTC
I change the initrd.img with my old initrd.img from the dvd i did in september and it didn't kernel panic. The install stop with an incorrect installer.

Is this initrd.img malformed ? How do you check the initrd ?

thks,

Comment 8 xxartemisxx 2009-02-03 14:11:12 UTC
any news ?

Comment 9 Jesse Keating 2009-03-10 03:36:06 UTC
Hrm, I can't see anything causing problems.  See if there is anything installed if you do "yum install @buildsys-build" and if so, try your compose after that.

Comment 10 xxartemisxx 2009-03-16 10:10:37 UTC
hi,

Thanks it's working now. After the command sed was downloaded. maybe there is a missing dependency with "yum install pungi" ?


bye

Comment 11 Jesse Keating 2009-03-16 18:01:50 UTC
What was the error?  It could be one of the anaconda packages needs sed listed.

Comment 12 Daniel Drake 2012-02-06 19:49:39 UTC
The problem in the above initramfs is that /sbin/init is not marked executable.


I also ran into something very similar (unbootable initramfs - can't execute init) respining CentOS 6.2 using pungi from F13. Just in case it helps anyone else: I ran into a different problem, where most important libraries (e.g. libc) were not included.

This is because /usr/lib/anaconda-runtime/mk-images uses file in instbin():
    iself="$(file $ROOT/$BIN | grep ELF)"

and file is not listed as a dependency of anaconda in F13. Installing it and rebuilding solves the issue.

I tried to check if current (F17) anaconda would suffer the same issue, but things seem to have moved around a lot, and grepping for 'file' is not that easy.