Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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 can't figure out how to add a Windows XP entry to the GRUB bootloader. I know there's been a million threads on this already, but none of them seem to help me. It think the problem might be that I have a lot of drives and partitions.
I added the following to /boot/grub/menu.lst:
title Windows Xp
rootnoverify (hd0,0)
makeactive
chainloader +1
But when I select it during boot, it says some executable is not in the right format, or something like that. I tried hd1 and hd2, but that gave me errors about unknown partition type. Can anyone help me fix this?
as homey says, fdisk -l - that's a little L, not a one,
is the best way to start.
ok- an explanation of the problem:
grub reads the grub entry to find out what it needs to do. at the line where you call
Code:
rootnoverify (hd0,0)
you are telling grub to look at the first harddrive, and the first partition. (because grub starts counting at zero, not one.)
Ok. So if we look at your partition diagram, which we shouldn't rely on, go for the fdisk -l but if we have a look, it is pointing to the one that just says sdb. Try changing it to hd2 (for the third drive) and 1 for the second partion. so it would be
Code:
rootnoverify (hd2,1)
This is just guesswork of course- we will be able to concrete it with the output of the fdisk command.
Thank you, it's good to be here.
I did read a few threads about this, but nobody else seemed to have as many partitions as I do, so those solutions didn't work.
Here's the fdisk output:
Quote:
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 892 7164958+ 7 HPFS/NTFS
/dev/sda2 893 24321 188193442+ f W95 Ext'd (LBA)
/dev/sda5 893 24321 188193411 7 HPFS/NTFS
Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 2040 16386268+ 83 Linux
/dev/sdb2 2041 14592 100823940 f W95 Ext'd (LBA)
/dev/sdb5 2041 3736 13623088+ 7 HPFS/NTFS
/dev/sdb6 3737 3865 1036161 82 Linux swap / Solaris
/dev/sdb7 3866 4845 7871818+ 83 Linux
/dev/sdb8 4846 14592 78292746 7 HPFS/NTFS
Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 14593 117218241 7 HPFS/NTFS
The partition with windows on it is sda1. So should I try rootnoverify with (hd1,0) and (hd2,0), or should I also try higher partitions?
this link might have some info in regards to your situation.
I think, that it might be worth an day's work to back up your stuff, and then do a complete reformat and repartition- in a way that makes sense.
- but you should be able to fix it without that- of course with less hair
this link might have some info in regards to your situation.
I think, that it might be worth an day's work to back up your stuff, and then do a complete reformat and repartition- in a way that makes sense.
- but you should be able to fix it without that- of course with less hair
titanium_geek
I'll try all those things, sounds promising.
Ideally I would repartition everything, but there's a few hundred gig of stuff on these drives, it would take a bit of work to pull off.
I haven't been able to get any hd#,# combination to work, and I think I know why. I installed Windows on that partition while I already had Windows installed on another partition. There is thus no boot.ini on the partition I'm trying to boot to. What should I put in the boot.ini?
EDIT: If I need to reinstall Windows, can I do it without clobbering GRUB? Could I maybe unplug all hard drives except for the Windows drive, install Windows, then plug everything back in?
one: windows loves to be the first partition on the first drive. It will scream if you don't let it.
two: it WILL clobber grub- if it can find it.
I know of people on this forum who have unplugged all but the windows drive, then reinstalled windows with out it killing grub. Of course, you could put grub on a floppy disk, then windows can't touch it. A linux boot floppy is a very useful tool in situations like this, as well.
Oh- and have you thought in investing in an external hardrive to backup your data?
I now have things working nicely. Here's a rundown:
1. Unplugged all drives except the one I want windows on.
2. Installed windows on it.
3. Linux drive is SATA1, windows drive is SATA3, but I changed the boot order in BIOS so that SATA3 was the first one. Could have just plugged them in the other way I know, but whatever.
4. Installed Kubuntu with GRUB onto the linux drive. It detected Windows during installation and added to the boot menu:
Quote:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1
So Windows is on hd0, even though it's actually on SATA3. I guess the boot order of the drives is important.
Anyone want to make any observations about this setup?
Try changing the boot order of the hard drives through bios, or just switch the cables around. That's what worked for me. It seemed that when my linux drive was the first boot hard drive, there was no "hd#,#" combination which would boot windows, but when I put the windows drive as the first boot device, it worked fine.
It's possible that you'll have to install GRUB on the windows drive if it's to be the first boot drive, because it's probably not on there at the moment.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.