Fitzcarraldo
Member
Hi.
Having used EasyBCD 2.0.2 successfully a couple of years ago to set up my laptop to dual boot between Windows 7 and Gentoo Linux, I am now having a problem and am not sure if the cause is Gentoo, GRUB 2 or EasyBCD.
The laptop has the following partitions:
sda1 Windows factory restore partition
sda2 Windows C: drive
sda3 /boot
sda4 Extended partition containing:
sda5 swap
sda6 /
sda7 /home
Originally I was using GRUB 2 version 1.99-r2, and had GRUB 2 code installed in the boot sector of sda3 and GRUB 2 files installed in /boot/grub/ directory. Everything worked fine. The Windows 7 bootloader menu was displayed, I would select Linux from the menu, that would chainload the GRUB 2 menu, and on that I would select Gentoo Linux.
Just a few days ago I decided to upgrade GRUB 2 to version 2.00_beta6. Now, note that the Gentoo developers decided that GRUB 2 would use /boot/grub2/ rather than /boot/grub/. This is similar to the situation with Fedora and a number of other Linux distributions. Similarly, the GRUB 2 installation script is named grub2-install rather than grub-install, the GRUB 2 script that creates the file grub.cfg is called grub2-mkconfig rather than grub-mkconfig, and so on.
Anyway, I used the Gentoo package manager to install version 2.00_beta6 of GRUB 2 and it appeared to have installed OK. I then used the GRUB 2 installer script grub2-install to install GRUB 2 to the boot sector of sda3 and to /boot/grub2/, and that appeared to have worked correctly too. And then I used the GRUB 2 script grub2-mkconfig to generate the new /boot/grub2/grub.cfg file, and that looks fine too.
But in fact GRUB 2 version 1.99 is still being booted instead of 2.00_beta6. GRUB 2 is still using the files in /boot/grub/ rather than the files in /boot/grub2/. If I move /boot/grub/ then the laptop will not boot correctly. If I change the contents of /boot/grub/grub.cfg then the changed file is used. So the contents of /boot/grub/ are definitely being used instead of the contents of /boot/grub2/.
I have documented the problem in detail, including console outputs and contents of the MBR and partitions' boot sectors, in the following Gentoo Linux forums thread:
Gentoo Forums :: View topic - GRUB 2 wrongly using /boot/grub/ instead of /boot/grub2/
In that thread you will see that I have checked that the Gentoo GRUB 2 installation script grub2-install does actually write to the boot sector of the sda3 partition.
I also installed the latest version of Easy BCD (2.1.2) and used it, in case the BCD in Windows refers to the location of the GRUB 2 files directory in the Linux installation (although I doubt it*), but that made no difference.
* Am I correct in thinking that the BCD simply points to the boot sector of the boot partition, and only the GRUB 2 code in there points to the Linux directory which contains the GRUB 2 files, or does the BCD have information about the location of GRUB 2's core.img file too?
Anyway, I am at a loss to explain why this is happening. I just wanted to check here in case EasyBCD does control where the GRUB 2 code in the partition's boot sector looks for the GRUB 2 core.img file and other GRUB 2 files. If so, how can I make EasyBCD point to /boot/grub2/ instead of /boot/grub/?
Many thanks in advance for any help you can give.
Having used EasyBCD 2.0.2 successfully a couple of years ago to set up my laptop to dual boot between Windows 7 and Gentoo Linux, I am now having a problem and am not sure if the cause is Gentoo, GRUB 2 or EasyBCD.
The laptop has the following partitions:
sda1 Windows factory restore partition
sda2 Windows C: drive
sda3 /boot
sda4 Extended partition containing:
sda5 swap
sda6 /
sda7 /home
Originally I was using GRUB 2 version 1.99-r2, and had GRUB 2 code installed in the boot sector of sda3 and GRUB 2 files installed in /boot/grub/ directory. Everything worked fine. The Windows 7 bootloader menu was displayed, I would select Linux from the menu, that would chainload the GRUB 2 menu, and on that I would select Gentoo Linux.
Just a few days ago I decided to upgrade GRUB 2 to version 2.00_beta6. Now, note that the Gentoo developers decided that GRUB 2 would use /boot/grub2/ rather than /boot/grub/. This is similar to the situation with Fedora and a number of other Linux distributions. Similarly, the GRUB 2 installation script is named grub2-install rather than grub-install, the GRUB 2 script that creates the file grub.cfg is called grub2-mkconfig rather than grub-mkconfig, and so on.
Anyway, I used the Gentoo package manager to install version 2.00_beta6 of GRUB 2 and it appeared to have installed OK. I then used the GRUB 2 installer script grub2-install to install GRUB 2 to the boot sector of sda3 and to /boot/grub2/, and that appeared to have worked correctly too. And then I used the GRUB 2 script grub2-mkconfig to generate the new /boot/grub2/grub.cfg file, and that looks fine too.
But in fact GRUB 2 version 1.99 is still being booted instead of 2.00_beta6. GRUB 2 is still using the files in /boot/grub/ rather than the files in /boot/grub2/. If I move /boot/grub/ then the laptop will not boot correctly. If I change the contents of /boot/grub/grub.cfg then the changed file is used. So the contents of /boot/grub/ are definitely being used instead of the contents of /boot/grub2/.
I have documented the problem in detail, including console outputs and contents of the MBR and partitions' boot sectors, in the following Gentoo Linux forums thread:
Gentoo Forums :: View topic - GRUB 2 wrongly using /boot/grub/ instead of /boot/grub2/
In that thread you will see that I have checked that the Gentoo GRUB 2 installation script grub2-install does actually write to the boot sector of the sda3 partition.
I also installed the latest version of Easy BCD (2.1.2) and used it, in case the BCD in Windows refers to the location of the GRUB 2 files directory in the Linux installation (although I doubt it*), but that made no difference.
* Am I correct in thinking that the BCD simply points to the boot sector of the boot partition, and only the GRUB 2 code in there points to the Linux directory which contains the GRUB 2 files, or does the BCD have information about the location of GRUB 2's core.img file too?
Anyway, I am at a loss to explain why this is happening. I just wanted to check here in case EasyBCD does control where the GRUB 2 code in the partition's boot sector looks for the GRUB 2 core.img file and other GRUB 2 files. If so, how can I make EasyBCD point to /boot/grub2/ instead of /boot/grub/?
Many thanks in advance for any help you can give.
Last edited: