Bug 1008697
Summary: | dracut-network not installed, although SAN is used for root | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dwayne McGarty <mcgartyd> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 19 | CC: | amulhern, anaconda-maint-list, dracut-maint, dshea, g.kaviyarasu, harald, jonathan, mkolman, rvykydal, sbueno, vanmeeuwen+fedora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-10-22 11:25:28 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: | |||||||||
Attachments: |
|
Description
Dwayne McGarty
2013-09-16 21:40:23 UTC
Can you attach the output of: # dracut --debug -f before doing step 4? Created attachment 798869 [details]
Output of dracut --debug -f
As requested, the output of dracut --debug -f. This command was issued after copying firmware files to /mnt/sysimage/usr/lib/firmware and doing a chroot /mnt/sysimage. This appears to include the missing firmware files properly in the resulting initramfs file so my work around is unnecessarily complex.
So, what is the bug again? If I just install the operating system as normal to a SAN disk and do the initial, fedora starts to boot, gets somewhere in the area of "Reached target Basic System" and falls to the dracut prompt. At the dracut prompt I looked at the logs and it looked as though the system could not see any of the volumes on the SAN storage. Running lvm commands returns nothingness. I also see in the logs that there were messages about firmware files ctfw and ct2fw not being found. If I do an lsinitrd | grep firmware, I don't see the firmware files being included in the initramfs. If I install the operating system and go through the steps 1-8 I provided above to include the missing firmware files, the system boots fine. The firmware files required for the Brocade CNA 1007 HBAs I have are missing after installation in a nutshell. Created attachment 800512 [details]
Ouput of three commands directly after installation complete. No manual firmware copy.
I am attaching a tar ball containing three files for comparison. These are all output of lsinitrd and dracut -f --debug taken directly after the install is completed but before the initial reboot. In this case, no manual copy of firmware files ctfw*, ct2fw* or cbfw* has taken place. ie directly after step 1 in my previous work-around steps.
1. lsinitrd-output-after-install-complete.txt. This file contains the output of lsinitrd taken after the install is complete. As you can see, the firmware files ctfw*, ct2fw* and cbfw* that will be need to boot from SAN are missing.
2. dracut-debug-output.log. This file is the output of dracut -f --debug that was run after I did the lsinitrd.
3. lsinitrd-output-after-manual-dracut. Again the output of lsinitrd taken after running dracut -f --debug.
Is dracut-network installed? I did a chroot /mnt/sysimage followed by rpm -qa | grep dracut. I don't see dracut-network installed. (In reply to Dwayne McGarty from comment #7) > I did a chroot /mnt/sysimage followed by rpm -qa | grep dracut. I don't see > dracut-network installed. well, it has to be for a SAN I've checked that in F20 Alpha the dracut-network is installed, I'll do some more testing as boot from SAN does not seem to work for me. I can confirm that install with boot on iSCSI works for me with F20Alpha so I am closing the BZ. If you hit the issue with F20 feel free to reopen the bug. |