Bug 114218
Summary: | FC1 test install fails after pxeboot+hard disk install | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Dalgaard <p.dalgaard> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | 64bit_fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-15 04:48:08 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: |
Description
Peter Dalgaard
2004-01-24 14:55:34 UTC
The images must match exactly. It sounds like you're just seeing mirror lag (ie boot image bits get to the mirror before netstg2.img etc) Notice that this also applies to HARD DISK installs where hdstg2 is sitting inside the .iso files. The actual PXE boot files (vmlinuz, initrd.img) does not appear to differ between source and mirror. Besides: all of these files and directories have dates at least one week old. How is one supposed to know if things have gotten out of step? (Preferably before hauling 2GB over the 'net!) And shouldn't there be a way of bypassing the check? Or are you telling me that there is a correct kernel and initrd image sitting inside the .iso files, differing from the extracted tree? Oops, thought this was devel, not test1. *sigh* Justin -- do you know of any problems with hard drive installs? Things should all match up. And the check is very intentionally not bypassable. If your images don't match, then you very likely don't have the same kernel version and will then be missing all of the kernel modules in the second stage which means no ext3 and numerous other problems. I have not seen this issue with hard disk installs from iso images. Is it possible the pxeboot environment was not sending the disk1 pxeboot files? Confirmed: The pxeboot and isolinux dirs inside the yarrow*disc1.iso both contain an initrd.img that is different from the one in the FTP/HTTP dir on download.fedora.redhat.com linux:~ # md5sum /mnt2/images/pxeboot/* f5528650defdc14e2d06ac9d104b6b87 /mnt2/images/pxeboot/TRANS.TBL 762e2ee5d1760daa9cafe5f3efb79af7 /mnt2/images/pxeboot/initrd.img cd1194ff4e6beb5918a007291f337768 /mnt2/images/pxeboot/vmlinuz linux:~ # logout Connection to 192.168.1.10 closed. [root@butterfly tftpboot]# md5sum initrd.img vmlinuz bf1603e992f8ea3624843ea9c6635a83 initrd.img cd1194ff4e6beb5918a007291f337768 vmlinuz And the obvious workaround works! This is fine with the final release AFAIK. |