Red Hat Bugzilla – Bug 74732
Wrong boot disk selected for grub
Last modified: 2007-04-18 12:46:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20020812
Description of problem:
One of my systems has mainly SCSI disks but also one IDE disk. The BIOS allows
to select which device is the boot device according to the controller (the SCSI
controller, IDE disk, IDE CDROM, ...). Before the upgrade to RHL8 the default
was the SCSI controller.
After successfully installing RHL8 booting failed. Nothing at all worked. The
reason is that anaconda automatically chose to use /dev/hda (the IDE disk) for
the boot block. As mentioned, this wasn't my book disk.
There is no way I could overwrite this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Get system with SCSI and IDE disks
2.make booting from SCSI default
3.normal installation, use grub
Actual Results: Does not boot.
Expected Results: Booting from BIOS device after anaconda selected it for the
Anaconda (and/or the kernel) should look at the BIOS setting for the boot device.
In addition, there should be the possibility to overwrite the boot device in the
grub setup in anaconda.
Did you use the advanced option in the bootloader config to redefine the boot
order of your system?
> Did you use the advanced option in the bootloader config to redefine the boot
> order of your system?
I didn't do anything special since I assumed Anaconda wouldn't try to interfere
with the system setup. This was a plain installation without any tweaks.
We have no reliable way to detect the boot order that BIOS is configured for
unfortunately, so the user has to tell us. Its not obvious, but your
configuration is not particularly common in my experience so it takes a little
more effort to get it working.
By ignoring all bugs as you seem to do it the product isn't going to get better.
There is support for to access the BIOS available in the kernel. Some Dell guys
recently even updated it or at least sent patches. And the situation isn't
guaranteed to be uncommon. Everybody who has both SCSI and IDE is affected.
Maybe even those which have more than one IDE or SCSI controller. If a system
simply doesn't work after the upgrade it's 100% the installers fault since the
information is available on the system.