Red Hat Bugzilla – Bug 485331
No initrd create when using local /boot and iscsi /
Last modified: 2009-02-13 10:12:49 EST
Description of problem: No initrd create when using local /boot and iscsi /
Version-Release number of selected component (if applicable):
rawhide (Fedora 11 Alpha)
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
No initrd created, not able to boot using iscsi /
successful boot with iscsi /
I mounted the iscsi tgt from another box and retrieved the anaconda logs. Will attach.
Created attachment 331770 [details]
Created attachment 331771 [details]
Created attachment 331772 [details]
Created attachment 331773 [details]
Created attachment 331774 [details]
Created attachment 331776 [details]
serial console output of the boot failure
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.
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.
Created attachment 331833 [details]
Created attachment 331834 [details]
Chris, I'm sorry but ...
From the new anaconda.log: 126.96.36.199
The one in rawhide on the iscsi testday was: 188.8.131.52, which contains a fix for not getting any initrd at all when using iscsi, see:
The changes in backend.py in that commit fix this, closing again.