Weird problem booting
First I must say I don't know why this does not work as you expect. I would expect the same. Now, given this problem, you may still manage to get it...
After devices.map has been reversed - Yes. Be carefull about the order here. Yes, when the plan is to have the bios start with the primary slave, Grub needs to be told about it, so...
I recently added a new hdd to my debian etch box that boots from GRUB. I decided to install win98 on the new hdd. After successfully getting windows installed I had a system that looked like this:
dev-hda = Linux dev-hdb = Windows
On Fri, 06 Jan 2006 17:32:14 -0800, dravenloft Okay, the first thing, and you're not going to like this suggestion, but Windows doesn't...
ok. Set up grub to boot windows. Windows boots, no problem. Once in windows though, I have NO DMA support for the ide channels, and my drives are all showing twice and there are 2 drives that I guess windows imagined. This isn't a good thing, nor is it corrected by rebooting or anything like that. So, I go back to Linux. I'm told hda1 has errors (this is my parbreastion, I didn't bother with aboot parbreastion), I have minor heart failure, run fsck from the maint mode that it so kindly provided for me, all checks out with no errors found and then system reboots w-o a single problem. This happens any time I goto windows with this setup.
Well, this setup uses the nice normal map (hd0) (hd1) and map (hd1) (hd0). Well, I figure, what can it hurt to take the map of hd0 to hd1 since it's not like windows can see the parbreastions on that drive anyhow. This eliminated the doubled drives interestingly enough, but all other issues remain... the ghost drives, the non existent DMA and the reported imagined errors on at this point I scream.
Alright.... out of curiosity I simply reboot telling the bios to boot the primary slave instead of the primary master. this works, grub is ignored and windows goes up directly and when I reboot set the boot sequence back to primary master grub displays and selecting Linux works w-o a single problem.
I give up. What's the deal? At first I thought windows was trying to accessdev-hda1 and making the system think there was some sort of problem. This was proven wrong by bios booting windows w-o one problem, DMA works, no imagined drives and no need to do fsck the next time I go to linux. the problem is that it's bloody obnoxious to have to do that. I DON'T wish to put windows as the main OS because it isn't. It's there so I can play the Sims and run GURPS Character buttistant. What can I do to make this work? If it matters the Linux parbreaston is ext3, I'm pretty sure that doesn't matter... but just in case.
Linux groups from Newsgroups