Originally Posted by
AbsurdWalls
Quite! Several times over the past decade I have:
1) Decided it would be cool to dual boot Windows/Linux
2) Had an "interaction" between the desired booting setup of the two
3) Ended up with a PC that won't boot into anything
Having a Windows machine or a Linux machine worked just fine for me. Having something do both has seemed impossible.
I was referring the behaviour of boot-repair. That's what I was unsure of.
The code you suggested gives:
"Booting a command list
Cannot get C/H/S values"
Putting "hd0" in instead gives me the Grub menu again, so I guess that fits with what you say about hd0 always being the boot drive. That doesn't fit with what happened previously when we were booting from the PBR though. There, hd0 was the drive with Windows on it (as '(hd0,msdos2)' booted up into Windows 7).
I believe you have to map the drive before booting off of it. I'm not 100% sure how this works in grub2. Maybe someone can correct me if I'm wrong. Try:
Code:
menuentry "Windows sda (from sdb) Chainboot" {
set root=(hd1)
drivemap -s hd0 hd1
chainloader +1
}
Then run a
Bookmarks