On 2014-06-21 18:39, Tony Alfrey wrote:
Carlos E. R. wrote:
You can find out.
Download this script:
<https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript>
and run it. It will extract lots of information about your boot system and partitions, including how and where boot sequence is set up.
Holy S^%&, where did you get this thing?
Look carefully at the url, and you will find someone around with a "similar" email ;-)
It is very impressive! Yes, just as I suspected, the SUSE installer put grub on the Windows disk!
There is probably a backup copy of that MBR somewhere in /boot. Otherwise, you can run in Windows 7: "bootrec.exe /fixmbr" to repair it. Mind, this will immediately break Linux booting, so first reinstall grub in the correct place.
I would certainly like to take that off and return the Windows disk to its previous state and simply put the four lines of code into grub.cfg on the SuSE disk that do the mapping thing that make Windows think it's the first disk.
It is not that trivial to convince the installer not to use the first disk in the system. You have to look carefully at all the options and tabs to make sure. Many people actually disconnect that first disk (that has Windows on it, typically), and later tell the bios to boot directly from the second disk. What I do is: - Tell the installer to put grub on the partition that contains the boot directory - Tell the installer to boot from that partition, and mark it as bootable. - Tell the installer to not write generic code (or anything) to the MBR - unless the disk doesn't contain Windows or is new. If it is not the first or main disk in the bios, make it so, and make sure it has an entry to boot Windows from it. It should be automatic with osprober in grub2. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)