Re: RFI: How to debug a particular problem with grub-install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dag Wieers wrote:
Hi,

I have a particular problem, only verified with RHEL4AS U4, where Anaconda happily installs and reboots but there does not seem a bootloader installed (or it is installed at the wrong location).

This happens on a HP Proliant DL580 G2 with the cciss driver. If I install the bootloader with grub-install myself (using a rescue cd and mount/chroot) then the grub device.map lists /dev/cciss/c0d0 as hd4 and sda as hd0.

Not sure if that is the problem, but manually overwriting the device.map and making /dev/cciss/c0d0 hd0 works as expected.


See this, from grub.info:
3.3 Installing GRUB using grub-install
======================================

*Caution:* This procedure is definitely less safe, because there are
several ways in which your computer can become unbootable. For example,
most operating systems don't tell GRUB how to map BIOS drives to OS
devices correctly--GRUB merely "guesses" the mapping. This will succeed
in most cases, but not always. Therefore, GRUB provides you with a map
file called the "device map", which you must fix if it is wrong. *Note
Device map::, for more details.


Grub has some difficuly detecting which drive you really use to boot from. I've not tried to do so, but I expect I could reproduct your problem at will by setting my BIOS to boot from any drive other than the first.







--

Cheers
John

-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxx
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/

Please do not reply off-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux