Red Hat Bugzilla – Bug 247303
BUG: biosdisk installs broken in some scenarios when unique disk signature dont exist
Last modified: 2009-06-19 19:31:42 EDT
Description of problem:
biosdisks install broken when we have 3 disks (bios disk 80,81,82) we want to
install to disk 80 from the hard disk we have ks=bd:80p1:/ks.cfg in command line
and in the ks.cfg we have the line
harddrive --biospart=80p1 --dir=/
and only disk80 has a valid signature. the other 2 disks have zero signatures
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. on a system with 3 disks, write a signature on the first disk (that will be
disk80) then dd the mbr of the other disks with zero.
2. begin a ks install from hard disk with the lines in ks.cfg targetting disk80
we get a message cannot find biosdisk 80 and the install aborts.
The install should continue because we a match signature match for the disk80
I have attached a probable patch to fix this issue. It is a back port from rhel 5.
Created attachment 158694 [details]
backport from rhel5 to fix this issue.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Dell can test this fix when the RHEL4.6 code is available.
Adding devel-ack based on patch in comment #1.
Per Dell call on 8/30, they will test. Setting OtherQA.
reply to comment #6
Larry, which version of anaconda will have this patch?
anaconda version 10.1.1.69 does not have this patch.
This issue is not fixed. The patch hasn't seemed to have made it for RHEL 4.6
anaconda ( 10.1.1.69).
The patch for this fix is in anaconda-10.1.1.70 and later, which should make it
in to the next snapshot.
Hi, has this issue been solved with the latest 4.6 snapshot?
Yes this issue has been solved with the latest 4.6 snapshot.
ok, thanks for the feedback ... :)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.