Red Hat Bugzilla – Bug 431644
grub switches hd0 and hd1
Last modified: 2008-06-16 21:17:44 EDT
Description of problem:
f9 alpha x86_64 live cd : after install script completes, grub is configured as
anaconda sees the drive, thus hd1 is used instead of hd0 and the system is
unable to boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install fedora to hard disk
system is unable to boot "no such partition"
Did you configure the "which drive to boot your installation from" combo box on
the partitioning screen?
no, it's the first time i've heard about it.
It's on the first partitioning screen and explicitly asks which drive should be
booted from. You can also get even more fine-grained control from the advanced
bootloader configuration screen.
Unfortunately, there is no way on PC hardware to reliably determine the boot
order of the hard drives such that we can always get it right. It's just not
information that the hardware can give us.
then how does the installed fedora always choose another order? also how does
the bios always choose another order than anaconda and this grub?
installing from 6.06.2008 boot.iso (rawhide), during install time, sda and sdb
are switched, and after install, iget this error:
fsck.ext3: No such file ordirectory while trying to open /dev/sdb6
probably because after install, the device names are correct, what was sdb now
is sda everytime i boot. however, i've see no trace of sdb6 anywhere. how can i
i've rebuilded initrd when i get a correct drives name in rescue mode (wich is
not happening every time)
i've replaced uuid with /dev/sda6 in grub.conf. the error is still there.
aargh! uuid was also present in /etc/fstab, after replacing with /dev/sda6, it
booted, wich makes me think that uuid is just an alias of the device name .....