OSDev.org

I was seeing the light and decided to install Linux... it wanted to install GRUB into the MBR, no problems...

Now Linux won't boot and Windows crashes (stop: c000021a fatal system error)...

This is what I get for deciding to go with the best OS around?

The windows error is caused by WinLogin failing. here.

Can't help you on the Linux: Unless you explain of course.

I'm solving it by overwriting the Linux installation with a new Windows installation, then fixing it from the parallel installation. Dr Watson didn't help at all because I couldn't get to a command line apart from the Recovery Console, and that didn't work either.

Insufficient input. Redo from start.

Ready.
{blinking cursor}


I know this isn't what you want to hear, but if you had trouble after parallel-installing Linux and setting up GRUB, you did it wrong. Really. However, without even knowing which Linux and which installation procedure you used, we can't tell what you did wrong.

GRUB works. Yes, it also works with WinXP / NTFS.

I was installing Ubuntu (the only Linux distro I have).

Installation procedure was the default, including installing grub to hard drive 0 (Windows drive) - which shouldn't have caused this.

I was also using SystemWorks (GoBack etc...) and this may be where the problem is.

OK, I think I've figured out at least why I can't access my drive from any other Windows install - I think I accidentally overwrote the MBR (fixmbr) and that must have wrecked something.

Any ideas as to how to get the MBR restored WITHOUT a reinstall of Windows?

Overwriting the MBR is expected behaviour when you install GRUB, because that is where GRUB stage 1 is located. If need be, you can restore the Windows MBR with fdisk /mbr (e.g. from a boot disk or a rescue shell).

If you mean the partition table... nope, unless I'm mistaken that one is gone forever if you overwrite it. If you know your settings exactly, you could use the Ranish Partition Manager or a similar tool to set them. I'm not sure about more "modern" tools (like Linux fdisk) being able to set partition table values as precisely as Ranish does.

Hi,

pcmattman wrote:I was also using SystemWorks (GoBack etc...) and this may be where the problem is.

I think you're right - see this web page...


Cheers,

Brendan

OK, I've fixed it!

I downloaded PTEDIT and loaded it up and found that my drive's type was '44' (hex) - which is a serious problem since that is not in any direct correlation to a drive type. A simple switch to '07' switched it back to NTFS and allowed my PC to boot. Next time, I'll just use Linux through Bochs .

I really don't suggest using bochs to run any operating system for actual use.

Don't give up on Linux though! It's not like it really wanted to hurt your system. It was just a misfortune that something bad happened. Try a different distro. (Although, I would avoid Suse. I'm currently using it, and the packaging system sucks bad. Real bad.) A note, though before any more attempts: Make sure you have all of your data backed up.

Good luck!

If you just want to play around, I suggest cygwin over bochs.

But I agree with Alboin: Don't give up. My first dodgy installs left me without anything. I learned very quickly how to make backups. I now use a dual-boot setup of XP Home / Kubuntu 6.10, using GRUB. It works extremely well.

If you're after a more stable, permanent system, I can reccommend Debian, Kubuntu/Ubuntu/Xubuntu (take your pick). I don't reccommend Fedora Core.

I make sure that I backup regularly, and I have a whole host of tools that I can use to recover from a problem.

It'd be safe to install Linux and whatever else onto another HDD and not use GRUB, then modify the boot.ini to allow me to also boot them? Otherwise, GRUB tries to write over my Windows partition's bootsector which I don't really want.

pcmattman wrote:It'd be safe to install Linux and whatever else onto another HDD and not use GRUB, then modify the boot.ini to allow me to also boot them? Otherwise, GRUB tries to write over my Windows partition's bootsector which I don't really want.

It is possible to boot Linux from NTLDR, however not directly, you'll still need GRUB or LILO which you can then chainload from within NTLDR. It's pretty complicated though unless you feel at home with linux' commandline tools. And when Ubuntu's setup doesn't offer any alternative to installing GRUB into your MBR, it's getting even more complicated (you'd have to install GRUB manually then).

You'll find more information on this on google, if not just ask.

cheers
Joe

Well, I'm currently posting this message from within Linux, so I guess you can tell I got it working... In the end I just bit the bullet and installed GRUB onto the MBR as well - now I'm successfully dual booting Windows and Linux.

Thankyou all for your help! I'd installed it once but the hard drive died and I since have a new one - please don't think I'm an OS noob!

pcmattman wrote:Thankyou all for your help! I'd installed it once but the hard drive died and I since have a new one - please don't think I'm an OS noob!

Installing Linux is like trying to find your garden gnome in the middle of the night. Even the most seasoned pro might find it impossible to install Linux on one platform or another.

For example, Suse 10.0. It works on my 32bit P3. Yet, when I try to install it on my AMD64, it dies miserably. However, when I try to install Suse 10.2 on the P3, it dies miserably, but on the AMD64 it works fine.(Surprisingly, Ubuntu doesn't work on any of them.)

I think it has something to do with the hard drives. Previously, to install Suse 9.3 on the AMD64 I had to pass several hard drive options to the kernel to get it to work. (eg. no dma, etc.)

I should look into this.... .......... Doubtful.