Bug 109289 - Anaconda incorrectly installs MBR on Compaq's connected to external storage
Anaconda incorrectly installs MBR on Compaq's connected to external storage
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-11-06 11:15 EST by Nick Strugnell
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-06 11:20:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nick Strugnell 2003-11-06 11:15:59 EST
Description of problem: 
When installing on a Compaq that uses the cciss driver, anaconda 
will install grub to the first external disk, rather than the 
internal disk - the result is that the machine will not boot. 
This is because anaconda thinks that sda (the first LUN on the SAN 
or external disk pack) contains the MBR. Anaconda should realise 
that on machines that use the cciss driver, the MBR is actually 
located on cciss/c0d0. 
Version-Release number of selected component (if applicable): 
all versions on all versions of RHL and RHEL 
How reproducible: 
Steps to Reproduce: 
1. Install on a Compaq that uses the cciss driver (e.g. DL380) and 
that is connected to a SAN or some other form of external storage. 
2. Choose MBR for location of bootloader. 
Actual results: 
Machine will not boot 
Expected results: 
Additional info: 
Workaround - disconnect SAN during installation.
Comment 1 Jeremy Katz 2003-11-06 11:20:06 EST
This is not generally true.  There is no way to reliably determine
boot order on x86 hardware.  This is why the advanced boot loader
options screen allows you to reorder the drives to match what your set
up is.

Note You need to log in before you can comment on or make changes to this bug.