Once wrote a "dual hard drive three system installation and guidance" aspects of the article, the article mentioned Grub Guide Win7 problem, the result was yesterday again encountered this problem.
The day before yesterday I reinstall Win7, the system is installed, the day is running well, reboot after the use of grub boot is also normal. But yesterday suddenly went out of the blue, using grub boot can not enter Win7, prompted BOOTMBR is missing! Only the order of the hard disk in the BIOS can be modified, and the disk in the Win7 is set as the first boot disk to enter the system.
At first, I really thought it was missing the system files for startup, but after modifying the boot sequence in the BIOS, I found that I could enter Win7, which is not the result of missing system files.
Take a closer look at the Grub's boot menu and compare it to the Win7 in the BIOS, and discover the problem: the order of the hard disks in the BIOS is inconsistent with the order of the hard drives mapped by the map command in the GRUB boot menu!
Modify, solve the problem!
This creates an interesting phenomenon: the last time you install the three systems, the final installation is openSUSE, after the installation, with Grub boot Win7 encountered in the Grub menu Map command mapped the hard drive sequence problem, this reload system encountered this problem.
Are the Windows hard drive mappings for map commands in the Grub boot menu problematic when installing or reloading a system (Linux or Windows) after the installation of Linux and Windows dual systems is complete? Do you want to change the order of the map command mapped Windows hard disk every time?