Red HatThis forum is for the discussion of Red Hat Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Did you change anything? Anything at all? It sounds like your lilo.conf (or grub.conf) is pointing to the wrong directory for windows. In lilo.conf or grub.conf all drive assignments are realative to hd0,0. If you used partition magic to make a new partition or delete an old one, this sort of trouble can come up.
If windows is on your first partition, try rootnoverify(hd0,0) chainloader +1
I did not change anything at all. And I tried changing grub.conf to rootnoverify(hd0,0) and again instead of giving the error as rootnoverify(hd0,4) it gave the error rootnoverify(hd0,0) and i did not use partition magic either.
I've got a similar problem - the annoying thing being that dual-booting *was* working on this machine until I changed distros. I have WinXP on one HD (hdb) and Linux on the other (hda). I did have Mandrake 10CE loaded, which used Lilo and worked fine. Then I decided to install SuSE 9.1, and while Linux boots okay, I get the message:
Filesystem type unknown, partition type 0x7
fdisk confirms that Windows is on hdb2 (there seems to be a Dell partition on hdb1 which I didn't know about before).
I tried changing to Lilo - no joy (hangs after saying 'Loading Windows'). I changed back to Grub and tried changing the seeting to 'rootnoverify', but that didn't help either. Alas, I need Windows on this machine, so I might be foreced back to Mandrake...
This has been one common problems among the Users who try to dual boot their system.
There has been many versions to this problem:
1. First Installed Linux - then installed Windows - Windows' own bootloader overwrites, the linux boot loader (Lilo or Grub).
(a). Try to boot into Linux with a boot floppy(if U have one, always better to have one).
Reinstall the boot loader.
(b). Use a third party bootloader program like Boot Magic.
2. The case reported by Raj Verma.
Raj, Have u changed the IDE slot. i.e., have changed the Data Cable from One slot to another in the Mother Board. Then the Name of the harddisk might have changed.
Grub is a multiboot load agent. It will try to boot OSes that support Multiboot directly.
But OSes which doesnt, it gives control to the respective boot loaders ( Eg. Windows). This is called Chain Loading.
Note: If U run the windows recovery CD U still might loose Linux.
In this case correcting the grub.conf file should suffice.
It wud be helpful for me raj, if U could give us the output of.
I recommend to those who wish to run more than one OS on a single hard drive, the following:
>>Visit www.vmware.com and purchase the VMware Workstation, either for Linux or Windows, depending on which OS is your primary
>>This allows you to run mulitple instances of various OSs on one disk without ever having to reboot (usually)
The price is a little steep if you aren't a developer or avid user of multiple operating systems, but they do offer academic pricing. IMO, it's well worth it. Give it a try folks, and do share comments.