Bug 431644
Summary: | grub switches hd0 and hd1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | cornel panceac <cpanceac> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | amlau |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-08 14:07:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
cornel panceac
2008-02-06 05:11:31 UTC
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 fix that? 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 ..... |