Dual Boot option is not working.

d0tc0mguy · 08-02-2005, 12:25 AM

try giving
rootnoverify (hdc,5)
chainloader +1
in the grub.conf

lowrida · 08-02-2005, 01:01 AM

Here's the result of fdisk -l /dev/hdc:

Code:

Disk /dev/hdc: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1          13      104391   83  Linux
/dev/hdc2            3917       24791   167678437+   f  W95 Ext'd (LBA)
/dev/hdc3              14        3916    31350847+  8e  Linux LVM
/dev/hdc5            3917       24791   167678406    7  HPFS/NTFS

Partition table entries are not in disk order

Quote:

Originally posted by d0tc0mguy
try giving
rootnoverify (hdc,5)
chainloader +1
in the grub.conf

Error 23: Error while pasrsing number.

volvogga · 08-02-2005, 01:25 AM

OK.....
I, for one, was not able to get as much insite into your problem with the output of that command as I was hoping for. Sorry about that. The reason I wanted to see that is that from your previous posts it almost looked as if your windows OS was on a extended partition's logical dive. Before going any further, I am afraid I will have to ask a few questions of my own.

1. Did windows boot before installing fedora core 4?
2. Is the windows partition a copy of a partition from another drive?
3. How many hard drives are in your computer?
4. When installing your hard drive, did you accedently put it on the secondary IDE channel?
5. Is the drive IDE, SATA, or SCSI?

I kind of need a clear idea of your hard drive and partition setup, and what I have seen so far from your posts is very confusing to me. Sorry about this.

lowrida · 08-02-2005, 01:32 AM

It's alright, it's probably my fault since I have very basic knowledge about Linux.

1. Yes, Windows (XP Professional) worked fine.
2. No, the hard drive is a 200GB Maxtor I got to replace my measily 17GB stock one. When I first installed Windows XP I made a 30GB partition for Linux.
3. Just the Maxtor.
4. I'm not sure what you mean, are you asking if I used the SLAVE connection? If so then no.
5. It is Ultra ATA/133.

Please, ask as many questions as you want. The more you know the better the chance of identifying the problem.

volvogga · 08-02-2005, 01:54 AM

ATA/133 is an IDE standard, so thats good. What I ment with question 4 is that there are two IDE channels. Primary and Secondary. Each of these can connect two IDE drives, master and slave drives respectivly. Typically, the primary channel handles hard disks, and the secondary channel handles Optical drives (CD/DVD-ROMS); although, I suppose you could have 4 hard drives if you wanted.

In Linux, the way I understand it, hda is the primary channel's master drive, hdb is the primary channel's slave drive, hdc is the secondary channel's master drive, and hdd is the secondary channel's slave drive. So when you hard disk identifies itself as hdc, I was wondering if it was on the secondary channel. It would have been a easy mistake to make. All that would have to be done is that you plugged the cable into the wrong part of the mobo. So I thought that I'd ask.

Windows is very picky about where it is installed (accually, it wants to be the only thing on your hard disk), whereas Linux doesn't really care. For example, you arn't supposed to be able to install windows on the slave drive. It has to be on primary master drive. Sense it ran for you before, I wouldn't think that it is a problem (but if your not sure, check it out).

Anyway, lesson over.

One of your posts was:

Hard Drives
*/dev/hdc
/dev/hdc1
/dev/hdc3
*/dev/hdc2
/dev/hdc5

This makes me wonder if for some reason, GRUB thinks that you have two HDs installed. So you may want to try making the windows call (hd1,0) or (hd1,4) or (hd1,1)..... you get the idea.

Also, try d0tc0mguy's idea again but make it (hdc,4) instead. That is if you haven't tried it yet.

Worth a shot anyway.

*EDIT*
Oh man. I may have found something else. I was looking at a bunch of sample GRUB configurations, and I noticed that most of them have the command 'makeactive' after the part that identifies the partition. So maybe try this as well:

title Other
rootnoverify (hd0,4)
makeactive
chainloader +1

or change the chainloader and makeactive commands around if that doesn't work.

lowrida · 08-02-2005, 02:49 AM

Tried both and got "Error 12: Invalid Device Requested".

Also, I realized when I was shutting down that NFS Locking is FAILED instead of OK, is that bad?

Navyblue · 08-02-2005, 03:15 AM

GRUB does not recognise hda (pri master), hdb (pri slave) or hdc (sec master), it only recognises hd0 (first harddisk in the IDE order) hd1 (the next harddisk) and so on. So It seems that you should put (hd0,3) if I counted it right, if not try (hd0,2).

volvogga · 08-02-2005, 02:19 PM

lowrida,

Sorry, but I have no idea if NFS failing to shutdown is a major problem. I'll try to look it up later.

If you didn't notice the edit of my last post, please look at it and try that method, as I think that may be the solution. I wasn't sure from your last post if you saw it or not.

Back in a few hours. Post if you fix the problem.

Also, thanks for that info Navyblue. I didn't know that.

lowrida · 08-02-2005, 03:21 PM

Quote:

Tried both and got "Error 12: Invalid Device Requested".

Both as in makeactive, chainloader +1 and chainloader +1, makeactive.

volvogga · 08-02-2005, 04:58 PM

Well.... maybe this will work. Doubt it, but I'm running out of ideas.

title Windows XP
unhide (hd0,4)
hide (hd0,0)
hide (hd0,1)
hide (hd0,2)
rootnoverify (hd0,4)
makeactive
chainloader +1

and this...

title Windows XP
unhide (hd0,3)
hide (hd0,0)
hide (hd0,1)
hide (hd0,2)
rootnoverify (hd0,3)
makeactive
chainloader +1

See if thoes work.