Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I have had Linux running on my computer for some time now, and I have finally decided to install windows for audio/video editing. Fortunately, before installing Linux, I partitioned the harddrive expecting this. Here is my setup: (fdisk -l)
Device Boot Start End Blocks Id System
/dev/hda1 * 1 40635 20480008+ 7 HPFS/NTFS
/dev/hda2 40636 40700 32760 83 Linux
/dev/hda3 40701 232581 96708024 5 Extended
/dev/hda5 40701 44698 2014960+ 83 Linux
/dev/hda6 44699 85333 20480008+ 83 Linux
/dev/hda7 85334 232581 74212960+ c W95 FAT32 (LBA)
hda1=windows, hda2=/boot, hda5=swap, hda6=root, and hda7 is a shared data partition.
I tried to install windows on hda1 and of course it put the windows loader on my MBR. I figued I'll stick with it, and install grub when the installation is over. But, during the first installation reboot, after the bios, it said that the operating system couldn't be found. Humm... So I edited my grub.conf and reinstalled grub thinking that maybe I just needed to boot with grub. My grub.conf looks like this:
# For booting GNU/Linux
title Gentoo Linux
kernel /kernel-2.6 root=/dev/hda6 vga=795
# For booting Windows NT
title Windows XP Pro
After selecting Windows XP, the screen cleared and then sat there, just displaying the grub boot options. So, I tried to reinstall Windows XP to no avail. Then I installed Windows 2k pro, and the same thing happened. What can cause this to happen? I know I have LBA support because I have been booting off of hda2 for a while and it is well past cyl 1024.
I honestly have no idea why this could be happening. Maybe I need to set a flag on one of the partitions? Or maybe there is something wrong with my partitioning scheme. I've run XP on this machine before, so I know it isn't a simple compatablity issue.
No, that didn't help at all, and I don't see why it would. I only have one harddrive so why would I even want to reference hd1? And besides, shouldn't this have worked when Windows installed its own bootloader into the mbr? Any other suggestions?
I have tried something derived from your last post like:
title Windows XP Pro
and that doesn't work either, so I changed it back to how it was. Then I booted with the Windows cd to get into the recovery console. I tried fixboot c: and that didnt work. So I tried fixboot c: AND fixmbr. Of course grub was overwritten, but windows still didn't boot. So I reinstalled grub and now I am still where I was when I started the thread. I did notice something I thought was bizarre inside of Windows recovery's MAP command. Here is the output:
I notice that there are two Partition0's. I do not know why the first partition0 is there. I do know that the 2nd one is my extended partition. Is this normal behavior? or should C: be Partition0, \boot be Partition1, and extended be Partition2 ? I'm unsure because I have never used the MAP utility before.
Last edited by AngryLlama; 12-02-2004 at 01:40 PM.
Well, if you're sure your BIOS is using LBA for the HDD, then my second guess would be the HDD is configured as "cable select" instead of master. 90% of the time when this happens to me it's one of those two problems. Manually specifying LBA and master, rather than letting the BIOS auto-configure the settings, usually resolves it.
If those suggestions don't fix the prob, I'd try formatting hda1 as FAT32 (using a 98 or ME boot disk) and let Windows setup convert it to NTFS later.
great suggestion crito. I actually had another harddrive on this bus a while ago. So the drive is probably set to Master or CS and I should try setting it to Single. I will try this once I get into my computer.
My drive didn't have any jumpers set (which means that it was set as factory single) but I changed it to another "single" mode and that didn't work, neither did setting it to cable select. I currently have it in single. It's starting to look like my problem is inexplainable. I still wonder why partition0 shows up twice when calling MAP from the Windows Recovery Console. I posted the output on my third post. What do you mean about setting it up with win98 first? Are you saying do a full install of win98 then overwrite it with a winxp setup? won't that require reformatting to ntfs and I will be where I am now. I tried select FAT for my partition type in the WinXP or Win2K setup already (I forget which one it was). But I will gladly try your suggestion if you clarify what I need to do.
Last edited by AngryLlama; 12-04-2004 at 03:25 PM.
It seems that when I setup my partition table I used parted. Parted wrote incorrect disk geometry to the disk (it used a head count of 16 instead of 255) Linux apparently reads the information from the BIOS while Windows reads it from the disk. simply changing the head count to 255 (with sfdisk) fixed the problem.
Thanks, I hope this helps other people out too. What a weird problem.
I have noticed a problem though. Whenever I boot into Windows it changes all my 0x83 (Linux) partitions to 0x93 (Amoeba). This causes GRUB and Linux to quit functioning since they are housed on those partitions. GRUB throws an Error 17 I think. I don't know if this is because of Windows or because of me changing the geometry on my drive. In order to fix the problem I have to boot with a live CD, when attempting to run cfdisk I get the following error:
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Is there anyway to realign my partitions? or is this not a problem. How can I keep Windows from changing the partition type?