Bug 485331

Summary: No initrd create when using local /boot and iscsi /
Product: [Fedora] Fedora Reporter: Chris Williams <cww>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dcantrell, hdegoede, jlaska, katzj, pjones, wtogami
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-13 15:12:49 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
anaconda.log
none
anaconda.syslog
none
anaconda-ks.cfg
none
install.log
none
install.log.syslog
none
serial console output of the boot failure
none
anaconda.log
none
anaconda.syslog none

Description Chris Williams 2009-02-12 22:16:15 UTC
Description of problem: No initrd create when using local /boot and iscsi /


Version-Release number of selected component (if applicable):
rawhide (Fedora 11 Alpha)


How reproducible:
Always


Steps to Reproduce:
1. Using custom partitioning in anaconda, setup a local /boot and swap, and an iscsi /
2. Install completes, but upon reboot you will see: 
VFS: Cannot open root device "sdb1" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

3. Boot into rescue, manually mount /boot. No initrd is present
  
Actual results:
No initrd created, not able to boot using iscsi /

Expected results:
successful boot with iscsi /


Additional info:
I mounted the iscsi tgt from another box and retrieved the anaconda logs. Will attach.

Comment 1 Chris Williams 2009-02-12 22:16:59 UTC
Created attachment 331770 [details]
anaconda.log

Comment 2 Chris Williams 2009-02-12 22:17:19 UTC
Created attachment 331771 [details]
anaconda.syslog

Comment 3 Chris Williams 2009-02-12 22:17:55 UTC
Created attachment 331772 [details]
anaconda-ks.cfg

Comment 4 Chris Williams 2009-02-12 22:18:18 UTC
Created attachment 331773 [details]
install.log

Comment 5 Chris Williams 2009-02-12 22:18:48 UTC
Created attachment 331774 [details]
install.log.syslog

Comment 6 Chris Williams 2009-02-12 22:29:07 UTC
Created attachment 331776 [details]
serial console output of the boot failure

Comment 7 Hans de Goede 2009-02-12 22:51:46 UTC
Chris, thanks for the bug report, but looking at the logs I've noticed you were doing a RHEL-5.3 test install, where this sort of setup is not supported.

The purpose of the testday was to do rawhide iscsi installs, closing.

Comment 8 Chris Williams 2009-02-13 14:49:25 UTC
Hans,

Sorry for the confusion. I had to mount the iscsi / from a different box and must have grabbed a couple of files from the 5.3 system I was using. I was using rawhide for the iscsi / install. I'll clean up and attach the correct files now.

Comment 9 Chris Williams 2009-02-13 14:52:42 UTC
Created attachment 331833 [details]
anaconda.log

Comment 10 Chris Williams 2009-02-13 14:54:19 UTC
Created attachment 331834 [details]
anaconda.syslog

Comment 11 Hans de Goede 2009-02-13 15:12:49 UTC
Chris, I'm sorry but ...

From the new anaconda.log: 11.5.0.12

The one in rawhide on the iscsi testday was: 11.5.0.17, which contains a fix for not getting any initrd at all when using iscsi, see:
http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=78ca394478575bc2dfda5a8e107c90254ee39b11#patch1

The changes in backend.py in that commit fix this, closing again.