Jaroslaw Swierczynski <[EMAIL PROTECTED]>: >Today I installed Arch from the 0.7.1-pre1 ISO and ran into troubles >with GRUB. The machine had a CD drive as hda and a harddisk as hdc. >The installer converted hdc into (hd2) and the root partition hdc3 to >(hd2,2). GRUB refused to install saying something like "no such >device". I figured out that GRUB recognized hdc as (hd0). Apparently >for GRUB it doesn\'t matter where a harddisk is but how many disks are >installed. So (hd0) doesn\'t mean hda, it means the first detected disk >(even if it\'s hdd). In my opinion it\'s a serious bug in the Arch >installer. What do you people think?
Maybe it's not a bug in the installer but a "feature" of grub ? When I was moving one of my systems to a new hard disk I found this: http://www.gnu.org/software/grub/manual/html_node/Installing-GRUB-using-grub_002dinstall.html#Installing-GRUB-using-grub_002dinstall "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." and from: http://www.gnu.org/software/grub/manual/html_node/Device-map.html#Device-map "The reason why the grub shell gives you the device map file is that it cannot guess the map between BIOS drives and OS devices correctly in some environments. For example, if you exchange the boot sequence between IDE and SCSI in your BIOS, it gets the order wrong. Thus, edit the file if the grub shell makes a mistake. " Is this the case? -- Rafal Szczepaniak (Lanrat) _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
