Fedora Core 4, Windows XP and Grub
Hi, I'm a Linux newbie and having looked through the various threads relating to my problem I still don't have a solution so would appreciate some pointers. First of all my setup is an Asrock 939 Dual Sata2 mobo, with AMD Athlon 64 3200 cpu, 1GB of RAM, 160GB SATA HD, 80GB PATA HD and 3GB PATA HD, Asus DVD/CD R/W a ...
Hi, I'm a Linux newbie and having looked through the various threads relating to my problem I still don't have a solution so would appreciate some pointers.
First of all my setup is an Asrock 939 Dual Sata2 mobo, with AMD Athlon 64 3200 cpu, 1GB of RAM, 160GB SATA HD, 80GB PATA HD and 3GB PATA HD, Asus DVD/CD R/W and of course a floppy drive.
The 160GB HD has Windows XP Pro 64-bit installed and the drive is split into 3 partions, 100GB for windows os and windows programmes, 40GB & 20GB for user files.
The 3GB HD is also used for user files with the intention of these being accessible to windows and linux.
The 80GB HD has Fedora Core 4 (64-bit version) installed.
The windows installation was done first and was working ok.
I then installed FC4. During the installation process it said that it was going to load GRUB in the MBR on /dev/sda which is the 160GB SATA drive.
The installation process identified that 'sda' was the 160GB SATA drive which it split into sda1 and sda2 (which appeared to be further split into sda5 and sda6 which matched the 40GB/20Gb split), 'hda' was the 80GB HD and 'hdb' was the 3GB HD.
During installation the 80GB HD (hda) was split in to:
1 /boot ext3 102MB
2 VolGroup00 LVM PV 78058MB
The VolGroup00 was then split in to:
LogVol00 / ext3 78016MB
LogVol01 swap 1984MB
LogVol02 /home ext3 17152MB
LogVol03 /tmp ext3 1056MB
LogVol04 /usr ext3 17152MB
After installation and on reboot the pc restarted and went straight into windows.
Then I looked on the web for pointers on what might be the problem. Restarting the pc with the 1st FC4 disk and selecting linux rescue I tried 'grub-install --recheck /dev/sda' with the following result:
(fd0) /dev/fd0
(hd0) /dev/hda 80GB HD
(hd1) /dev/hdb 3GB HD
(hd2) /dev/sda 160GB HD SATA
I then rebooted the pc and this time got a blank screen with
GRUB_ in the top left hand corner.
I then went back into linux rescue and tried 'grub-install /dev/sda' and 'grub-install /dev/hda' but got the same results.
So I can't even get into windows at the moment.
I then took a look at the grub.conf file and got the following:
# grub.conf generated by anaconda
#
#Note that you do not have to rerun grub after making changes to this file
#NOTICE: You have a /boot partion. This means that
# all kernel and initrd paths are relative to /boot/, eg
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 .................... (random letters/numbers here)
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Window XP
rootnoverify (hd0,0)
chainloader +1
The first thing that I notice is that the hd references in the grub.conf do not match with the hd references from the grub-install --recheck operation e.g in grub.conf it refers to Fedora Core root hd1 and Windows XP hd0 where as Fedora Core is actually on hd0 and Windows XP is actually on hd2 in the --recheck list.
Apologies for the long listing but hopefully there is enough info to allow you to point me in the right direction rather than you having to ask more questions first.
Thanks for your help.
Dave.
First of all my setup is an Asrock 939 Dual Sata2 mobo, with AMD Athlon 64 3200 cpu, 1GB of RAM, 160GB SATA HD, 80GB PATA HD and 3GB PATA HD, Asus DVD/CD R/W and of course a floppy drive.
The 160GB HD has Windows XP Pro 64-bit installed and the drive is split into 3 partions, 100GB for windows os and windows programmes, 40GB & 20GB for user files.
The 3GB HD is also used for user files with the intention of these being accessible to windows and linux.
The 80GB HD has Fedora Core 4 (64-bit version) installed.
The windows installation was done first and was working ok.
I then installed FC4. During the installation process it said that it was going to load GRUB in the MBR on /dev/sda which is the 160GB SATA drive.
The installation process identified that 'sda' was the 160GB SATA drive which it split into sda1 and sda2 (which appeared to be further split into sda5 and sda6 which matched the 40GB/20Gb split), 'hda' was the 80GB HD and 'hdb' was the 3GB HD.
During installation the 80GB HD (hda) was split in to:
1 /boot ext3 102MB
2 VolGroup00 LVM PV 78058MB
The VolGroup00 was then split in to:
LogVol00 / ext3 78016MB
LogVol01 swap 1984MB
LogVol02 /home ext3 17152MB
LogVol03 /tmp ext3 1056MB
LogVol04 /usr ext3 17152MB
After installation and on reboot the pc restarted and went straight into windows.
Then I looked on the web for pointers on what might be the problem. Restarting the pc with the 1st FC4 disk and selecting linux rescue I tried 'grub-install --recheck /dev/sda' with the following result:
(fd0) /dev/fd0
(hd0) /dev/hda 80GB HD
(hd1) /dev/hdb 3GB HD
(hd2) /dev/sda 160GB HD SATA
I then rebooted the pc and this time got a blank screen with
GRUB_ in the top left hand corner.
I then went back into linux rescue and tried 'grub-install /dev/sda' and 'grub-install /dev/hda' but got the same results.
So I can't even get into windows at the moment.
I then took a look at the grub.conf file and got the following:
# grub.conf generated by anaconda
#
#Note that you do not have to rerun grub after making changes to this file
#NOTICE: You have a /boot partion. This means that
# all kernel and initrd paths are relative to /boot/, eg
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 .................... (random letters/numbers here)
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Window XP
rootnoverify (hd0,0)
chainloader +1
The first thing that I notice is that the hd references in the grub.conf do not match with the hd references from the grub-install --recheck operation e.g in grub.conf it refers to Fedora Core root hd1 and Windows XP hd0 where as Fedora Core is actually on hd0 and Windows XP is actually on hd2 in the --recheck list.
Apologies for the long listing but hopefully there is enough info to allow you to point me in the right direction rather than you having to ask more questions first.
Thanks for your help.
Dave.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Are you using the raid controller as a raid array, or just as an ide channel?
Is the raid controller onboard, or a raid pci card?
Is the bios set to recognize raid first (not the boot order)? If you post the make and model of motherboard that you have, this would help.
You do not have a /boot partition. It looks like from your grub file, that you installed grub to the MBR of the Fedora drive, not the MBR of your primary master drive. Otherwise, you would see grub when you boot from this drive.
You do not have a seperate boot parition on the Fedora drive, rather, a /boot directory within the root filesystem of Fedora? At least, that is what the Grub.conf file seems to indicate.
If you have a boot partition on the Fedora drive, then you would see that when you do fdisk -l, say;
hdf1....... /boot
hdf2......./
When the bios is set to boot from the primary master, you have the Windows bootloader on the MBR of that drive.
When you change the bios boot order of the drive to the Fedora drive, you are booting from Grub, which is on the MBR of the second drive.
A common mistake, I am seeing from several recent posts, is to change the boot order in the bios, before installing Linux. The drive designations are always relative to what the boot order in the bios is set for.
Is the raid controller onboard, or a raid pci card?
Is the bios set to recognize raid first (not the boot order)? If you post the make and model of motherboard that you have, this would help.
You do not have a /boot partition. It looks like from your grub file, that you installed grub to the MBR of the Fedora drive, not the MBR of your primary master drive. Otherwise, you would see grub when you boot from this drive.
You do not have a seperate boot parition on the Fedora drive, rather, a /boot directory within the root filesystem of Fedora? At least, that is what the Grub.conf file seems to indicate.
If you have a boot partition on the Fedora drive, then you would see that when you do fdisk -l, say;
hdf1....... /boot
hdf2......./
When the bios is set to boot from the primary master, you have the Windows bootloader on the MBR of that drive.
When you change the bios boot order of the drive to the Fedora drive, you are booting from Grub, which is on the MBR of the second drive.
A common mistake, I am seeing from several recent posts, is to change the boot order in the bios, before installing Linux. The drive designations are always relative to what the boot order in the bios is set for.
I'm just using the raid controller as an ide channel.
It's the SYBA SD-ATA133R PCI IDE Controller Card RAID 0/1/0+1 :
http://www.newegg.com/Product/Product.asp?Item=N82E16815124001
I have the Asus A7V8X-X mother board.
There is no option in the bios for raid. There is only the boot order.
Yes I understand now. I thought it just meant the /boot directory.
And yes I installed it to the MRB of hdf which is where Fedora is installed.
So yes the /boot directory is within the root filesystem of Fedora.
Well I have to change the boot order in the bios before installing Linux. I have to set it to not boot any hard disk at all and cd only. I have to. Only way to boot of a cd.
I've just never had this problem before. Then again all distros I have tired do not use Grub but LILO instead.
So how would I go about fixing this issue? You said "the drive designations are always relative to what the boot order in the bios is set for" ; so do that mean when I set it to boot off the second disk.
I guess that's what I do not understand seeing as in the grub config it's 2,0 which I would think mean the second hard disk and the first partition. So since I have to change the boot order it becomes 1, 0 no? I tired 1,0 and get some result BTW.
Well thanks for your help,
Will
It's the SYBA SD-ATA133R PCI IDE Controller Card RAID 0/1/0+1 :
http://www.newegg.com/Product/Product.asp?Item=N82E16815124001
I have the Asus A7V8X-X mother board.
There is no option in the bios for raid. There is only the boot order.
Yes I understand now. I thought it just meant the /boot directory.
And yes I installed it to the MRB of hdf which is where Fedora is installed.
So yes the /boot directory is within the root filesystem of Fedora.
Well I have to change the boot order in the bios before installing Linux. I have to set it to not boot any hard disk at all and cd only. I have to. Only way to boot of a cd.
I've just never had this problem before. Then again all distros I have tired do not use Grub but LILO instead.
So how would I go about fixing this issue? You said "the drive designations are always relative to what the boot order in the bios is set for" ; so do that mean when I set it to boot off the second disk.
I guess that's what I do not understand seeing as in the grub config it's 2,0 which I would think mean the second hard disk and the first partition. So since I have to change the boot order it becomes 1, 0 no? I tired 1,0 and get some result BTW.
Well thanks for your help,
Will
Quote:Well I have to change the boot order in the bios before installing Linux. I have to set it to not boot any hard disk at all and cd only. I have to. Only way to boot of a cd.
No, do not change the boot order of the hard drives! If you do this, then you change the primary hard drive boot disk order, which is not what you want to do.
If the cdrom is the first boot device, what is the second?
Setting the cdrom to boot first, just allows the system to boot from the cdrom first, then the (hopefully) primary master drive, which should be hdd0. If no bootable cdrom is found, the system boots off the next drive in the boot order.
There should be a setting in the bios to choose what type of system you are booting, scsi vs. ide.
Is there a setting right now that has this order;
scsi (or raid), ide....
or;
ide, scsi (raid)....
No, do not change the boot order of the hard drives! If you do this, then you change the primary hard drive boot disk order, which is not what you want to do.
If the cdrom is the first boot device, what is the second?
Setting the cdrom to boot first, just allows the system to boot from the cdrom first, then the (hopefully) primary master drive, which should be hdd0. If no bootable cdrom is found, the system boots off the next drive in the boot order.
There should be a setting in the bios to choose what type of system you are booting, scsi vs. ide.
Is there a setting right now that has this order;
scsi (or raid), ide....
or;
ide, scsi (raid)....
Originally posted by danleff:
Quote:No, do not change the boot order of the hard drives! If you do this, then you change the primary hard drive boot disk order, which is not what you want to do.
If the cdrom is the first boot device, what is the second?
Setting the cdrom to boot first, just allows the system to boot from the cdrom first, then the (hopefully) primary master drive, which should be hdd0. If no bootable cdrom is found, the system boots off the next drive in the boot order.
There should be a setting in the bios to choose what type of system you are booting, scsi vs. ide.
Is there a setting right now that has this order;
scsi (or raid), ide....
or;
ide, scsi (raid)....
Hey,
I think I understand what your getting at. About to see if I'm correct. Be back in a bit.
Take Care,
Will
Update:
OK well making progress. I can not get into grub and it lists fedora core but it fails to boot with:
Filesystem type unknown partition type 0x7
Error 17: cannot mount selected partition
press any key to continue
Stumped atm.
So I am not touch boot order now. It goes floppy, cdrom, hard disk. And for hard disk I pick the second one which is where fedora core is install and choose fedora core from grub menu and get the error above but hey at least I can not get into grub so thanks a lot. Now just to get it botting now.
[Edited by war59312 on 2006-02-08 14:06:27]
Quote:No, do not change the boot order of the hard drives! If you do this, then you change the primary hard drive boot disk order, which is not what you want to do.
If the cdrom is the first boot device, what is the second?
Setting the cdrom to boot first, just allows the system to boot from the cdrom first, then the (hopefully) primary master drive, which should be hdd0. If no bootable cdrom is found, the system boots off the next drive in the boot order.
There should be a setting in the bios to choose what type of system you are booting, scsi vs. ide.
Is there a setting right now that has this order;
scsi (or raid), ide....
or;
ide, scsi (raid)....
Hey,
I think I understand what your getting at. About to see if I'm correct. Be back in a bit.
Take Care,
Will
Update:
OK well making progress. I can not get into grub and it lists fedora core but it fails to boot with:
Filesystem type unknown partition type 0x7
Error 17: cannot mount selected partition
press any key to continue
Stumped atm.
So I am not touch boot order now. It goes floppy, cdrom, hard disk. And for hard disk I pick the second one which is where fedora core is install and choose fedora core from grub menu and get the error above but hey at least I can not get into grub so thanks a lot. Now just to get it botting now.
[Edited by war59312 on 2006-02-08 14:06:27]
Hey,
I finally got F4 booting.
Even manged to update the kernal and updated gnome to 2.12.1.
Now the only problem is getting winows xp to boot from gurb.
At the moment when slecting windows xp in grub it just opens grub as if I just typed in grub. Where you can only use grub commands. Know what I mean?
Well here is my grub config:
Code:
I finally got F4 booting.
Even manged to update the kernal and updated gnome to 2.12.1.
Now the only problem is getting winows xp to boot from gurb.
At the moment when slecting windows xp in grub it just opens grub as if I just typed in grub. Where you can only use grub commands. Know what I mean?
Well here is my grub config:
Code:
# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You have a /boot partition. This means that# all kernel and initrd paths are relative to /boot/, eg.# root (hd2,0)# kernel /vmlinuz-version ro root=/dev/hdf4# initrd /initrd-version.img#boot=/dev/hdf1default=2timeout=5splashimage=(hd2,0)/grub/splash.xpm.gz#hiddenmenutitle Fedora Core (2.6.15-1.1831_FC4) #root (hd2,0) root (hd0,0) kernel /vmlinuz-2.6.15-1.1831_FC4 ro root=LABEL=/ initrd /initrd-2.6.15-1.1831_FC4.imgtitle Fedora Core - Old (2.6.11-1.1369_FC4) #root (hd2,0) root (hd0,0) #kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/hdf4 initrd /initrd-2.6.11-1.1369_FC4.imgtitle Windows XP rootnoverify (hd0,0) chainloader +1
Dear friends,
I have two hard drives in my computer and installed
Windows XP with FAT format on the first hard drives (hda)
and installed FC4 on the second hard drives and installed
GRUB on MBR of the hda. The default OS is set to XP.
When the system was rebooted, the GRUB menu showed up and
tried to run XP, but it did not run XP and came back
to the GRUB menu. But if FC4 is picked, FC4 runs ok.
What wrong is it?
Thank you in advance for any help.
I have two hard drives in my computer and installed
Windows XP with FAT format on the first hard drives (hda)
and installed FC4 on the second hard drives and installed
GRUB on MBR of the hda. The default OS is set to XP.
When the system was rebooted, the GRUB menu showed up and
tried to run XP, but it did not run XP and came back
to the GRUB menu. But if FC4 is picked, FC4 runs ok.
What wrong is it?
Thank you in advance for any help.
Oopps! I meant to say;
You have a pci raid controller card, not an onboard raid controller, correct?
Notice that your hard drive designations are different than expecetd, due to the raid card.
(fd0) /dev/fd0
(hd0) /dev/hdb
(hd1) /dev/hde
(hd2) /dev/hdf
Where, in a totally ide system w/o a raid card, it would be something like;
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdb
(hd2) /dev/hdc
The drive orders are also interesting in Grub. The difference is based on how the raid card affects the drive order.
Can you post the output of;
fdisk -l
Do this as root user in a console screen.
In Fedora, you may need to do;
/sbin/fdisk -l
Remember, this is the letter L (small case), not the number 1 after fdisk.
This will tell us where the Windows installation is, as seen by Fedora.
You have a pci raid controller card, not an onboard raid controller, correct?
Notice that your hard drive designations are different than expecetd, due to the raid card.
(fd0) /dev/fd0
(hd0) /dev/hdb
(hd1) /dev/hde
(hd2) /dev/hdf
Where, in a totally ide system w/o a raid card, it would be something like;
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdb
(hd2) /dev/hdc
The drive orders are also interesting in Grub. The difference is based on how the raid card affects the drive order.
Can you post the output of;
fdisk -l
Do this as root user in a console screen.
In Fedora, you may need to do;
/sbin/fdisk -l
Remember, this is the letter L (small case), not the number 1 after fdisk.
This will tell us where the Windows installation is, as seen by Fedora.
dan7
I assume that you have the drives jumpered correctly, are using ide drives (not sata or raid) and that the installation was set up to boot your hda drive (HDD0 in the bios) first when you did the installation of Fedora?
Can you post the /boot/grub/menu.lst and /boot/grub/device.map file contents by any chance?
What motherboard is this, or the make and model of the system?
I assume that you have the drives jumpered correctly, are using ide drives (not sata or raid) and that the installation was set up to boot your hda drive (HDD0 in the bios) first when you did the installation of Fedora?
Can you post the /boot/grub/menu.lst and /boot/grub/device.map file contents by any chance?
What motherboard is this, or the make and model of the system?
Hey,
Yes it's a pci raid controller card.
Here is fdisk -l output as requested:
Code:
Thanks again,
Will
Yes it's a pci raid controller card.
Here is fdisk -l output as requested:
Code:
Disk /dev/hdb: 61.4 GB, 61471162368 bytes255 heads, 63 sectors/track, 7473 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hdb1 * 1 7473 60026841 7 HPFS/NTFSDisk /dev/hde: 80.0 GB, 80026361856 bytes255 heads, 63 sectors/track, 9729 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hde1 * 1 8414 67585423+ 7 HPFS/NTFS/dev/hde2 8415 9728 10554705 f W95 Ext'd (LBA)/dev/hde5 8415 9728 10554673+ 7 HPFS/NTFSDisk /dev/hdf: 120.0 GB, 120034123776 bytes255 heads, 63 sectors/track, 14593 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hdf1 * 1 13 104391 83 Linux/dev/hdf2 1276 1393 947835 82 Linux swap / Solaris/dev/hdf3 1394 14593 106029000 f W95 Ext'd (LBA)/dev/hdf4 14 1275 10137015 83 Linux/dev/hdf5 1394 14593 106028968+ 7 HPFS/NTFSPartition table entries are not in disk order
Thanks again,
Will
Hi danleff,
Thank you for your reply.
I am using a DELL Latitude C800 notebook with two ide HDs.
The primary HD had Windows 2000 and the second HD is in
a modular bay and FC4 was installed. It worked perfectly.
Few days ago, I upgraded the BIOS and put Windows XP
(got rid of Windows 2000) on the primary HD. When
the system rebooted, the GRUB menu was gone. And then
I re-installed FC4 on the second HD and get back the
GRUB menu. Now I can have two options - first one
runs FC4 and second is to go to Windows XP (this is
default). However, when the system try to XP, it just
quickly display
Booting 'Windows XP'
rootnoverify (hd0,0)
chainloader +1
GRUB Loading stage2...
and returns to the GRUB meun.
the device.map file contains:
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdc (I do not know why not hdb)
the menu.lst (grub.config) file contains:
#boot=/dev/hda
default=1
timeout=5
splashimage(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
hda is the primary drive and has XP.
hdc is the second drive and has FC4.
I can't see anything wrong here.
The other thing could be the new BIOS version,
otherwise, I do not know what is going on here.
Thanks for your help.
Thank you for your reply.
I am using a DELL Latitude C800 notebook with two ide HDs.
The primary HD had Windows 2000 and the second HD is in
a modular bay and FC4 was installed. It worked perfectly.
Few days ago, I upgraded the BIOS and put Windows XP
(got rid of Windows 2000) on the primary HD. When
the system rebooted, the GRUB menu was gone. And then
I re-installed FC4 on the second HD and get back the
GRUB menu. Now I can have two options - first one
runs FC4 and second is to go to Windows XP (this is
default). However, when the system try to XP, it just
quickly display
Booting 'Windows XP'
rootnoverify (hd0,0)
chainloader +1
GRUB Loading stage2...
and returns to the GRUB meun.
the device.map file contains:
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdc (I do not know why not hdb)
the menu.lst (grub.config) file contains:
#boot=/dev/hda
default=1
timeout=5
splashimage(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
hda is the primary drive and has XP.
hdc is the second drive and has FC4.
I can't see anything wrong here.
The other thing could be the new BIOS version,
otherwise, I do not know what is going on here.
Thanks for your help.
Will;
Do you know how to edit Grub from the boot splash screen? I really need to write a web page on this to refer to!
I have not played with my system with a raid card in it for a while. I think that I need to try this again myself.
Linux is seeing the drives, I believe, in reverse order. This is not unusual. The raid card causes this.
If you can edit at the splash screen, you can make temp. changes to grub there, without making them final yet (writing to the menu.lst file).
At the splash screen, hit the "e" key on your keyboard. Bear with me, I have a Suse grub splash screen and Fedora may be different!
When you hit the "e" key, you should get a text based screen.
Loook at the bottom command options. Add two lines after the;
title Windows XP
So that it looks like the following;
title Windows XP
map (hd0) (hd2)
map (hd2) (hd0)
rootnoverify (hd0,0)
chainloader +1
note: As you edit each line, just hit the enter key to make the changes take.
If that does not work, try;
title Windows XP
map (hd0) (hd2)
map (hd2) (hd0)
makeactive
chainloader (hd0,0)+1
When you are finished, and are back to the text screen that outlines the total Windows XP lines, hit the "b" key on the keyboard. This will attempt a boot. Let us know what happens.
If this works, you can modify you actual menu.lst file later on in Fedora.
If you maker a mistake, don't worry. Hitting the esc key gets you out.
Do you know how to edit Grub from the boot splash screen? I really need to write a web page on this to refer to!
I have not played with my system with a raid card in it for a while. I think that I need to try this again myself.
Linux is seeing the drives, I believe, in reverse order. This is not unusual. The raid card causes this.
If you can edit at the splash screen, you can make temp. changes to grub there, without making them final yet (writing to the menu.lst file).
At the splash screen, hit the "e" key on your keyboard. Bear with me, I have a Suse grub splash screen and Fedora may be different!
When you hit the "e" key, you should get a text based screen.
Loook at the bottom command options. Add two lines after the;
title Windows XP
So that it looks like the following;
title Windows XP
map (hd0) (hd2)
map (hd2) (hd0)
rootnoverify (hd0,0)
chainloader +1
note: As you edit each line, just hit the enter key to make the changes take.
If that does not work, try;
title Windows XP
map (hd0) (hd2)
map (hd2) (hd0)
makeactive
chainloader (hd0,0)+1
When you are finished, and are back to the text screen that outlines the total Windows XP lines, hit the "b" key on the keyboard. This will attempt a boot. Let us know what happens.
If this works, you can modify you actual menu.lst file later on in Fedora.
If you maker a mistake, don't worry. Hitting the esc key gets you out.
dan7
The modular bay does not make you swap out the cdrom drive, does it?
Is the boot order in the bios the same, since you updated the bios, as the old one?
If you don't need to swap out the cdrom drive, than hdb is the cdrom drive. Remember, this is seen as an ide drive by the bios and linux. The designation is usually;
hd0 = primary master drive
hd1 = primary slave drive
hd2 - secondary master drive
hd3 = secondary slave drive
Quote:Few days ago, I upgraded the BIOS and put Windows XP (got rid of Windows 2000) on the primary HD. When
the system rebooted, the GRUB menu was gone.
Yes, when you install any version of Windows, it overwrites the master boot record where grub resided.
When you installed Windows XP, did you reformat the hard drive and install Windows XP on the exact partition that Windows 2000 was on?
The modular bay does not make you swap out the cdrom drive, does it?
Is the boot order in the bios the same, since you updated the bios, as the old one?
If you don't need to swap out the cdrom drive, than hdb is the cdrom drive. Remember, this is seen as an ide drive by the bios and linux. The designation is usually;
hd0 = primary master drive
hd1 = primary slave drive
hd2 - secondary master drive
hd3 = secondary slave drive
Quote:Few days ago, I upgraded the BIOS and put Windows XP (got rid of Windows 2000) on the primary HD. When
the system rebooted, the GRUB menu was gone.
Yes, when you install any version of Windows, it overwrites the master boot record where grub resided.
When you installed Windows XP, did you reformat the hard drive and install Windows XP on the exact partition that Windows 2000 was on?
danleff
> The modular bay does not make you swap out the cdrom drive,
> does it?
No. I take out the floppy disk drive as I don't need it
and use the modular bay for the second HD.
> Is the boot order in the bios the same, since you
> updated the bios, as the old one?
The boot order is now:
1. Diskette Drive
2. CDROM Drive
3. Internal HD
4. Modular Bay HD
> If you don't need to swap out the cdrom drive,
> than hdb is the cdrom drive.
Thanks.
> Yes, when you install any version of Windows,
> it overwrites the master boot record where grub resided.
GRUB has been installed on MBR of hda when FC4 is re-installed.
I don't know why it now doesn't work.
> When you installed Windows XP, did you reformat
> the hard drive and install Windows XP on the exact
> partition that Windows 2000 was on?
Yes, I did use quick format as FAT (not NTFS) and
install XP on the exact partition.
It seems to me that the system runs GRUB on MBR stored
on hda, but GRUB can not find the hda1, which is XP on.
Thanks for your replies.
> The modular bay does not make you swap out the cdrom drive,
> does it?
No. I take out the floppy disk drive as I don't need it
and use the modular bay for the second HD.
> Is the boot order in the bios the same, since you
> updated the bios, as the old one?
The boot order is now:
1. Diskette Drive
2. CDROM Drive
3. Internal HD
4. Modular Bay HD
> If you don't need to swap out the cdrom drive,
> than hdb is the cdrom drive.
Thanks.
> Yes, when you install any version of Windows,
> it overwrites the master boot record where grub resided.
GRUB has been installed on MBR of hda when FC4 is re-installed.
I don't know why it now doesn't work.
> When you installed Windows XP, did you reformat
> the hard drive and install Windows XP on the exact
> partition that Windows 2000 was on?
Yes, I did use quick format as FAT (not NTFS) and
install XP on the exact partition.
It seems to me that the system runs GRUB on MBR stored
on hda, but GRUB can not find the hda1, which is XP on.
Thanks for your replies.
Danleff
Not had much time this year so far to try and resolve my dual boot problems.
You sent the following message on this thread:
2006-01-04 10:59:12
g0kth, I just switched my system over to sata only. If you are still having the problem, I may be able to resolve it, as I have my drives set up close to yours.
Following this message I gave you an update on what I had tried, still to no avail.
Can you give me details of your SATA setup to see if this will help solve my problems.
Cheers
Dave.
Not had much time this year so far to try and resolve my dual boot problems.
You sent the following message on this thread:
2006-01-04 10:59:12
g0kth, I just switched my system over to sata only. If you are still having the problem, I may be able to resolve it, as I have my drives set up close to yours.
Following this message I gave you an update on what I had tried, still to no avail.
Can you give me details of your SATA setup to see if this will help solve my problems.
Cheers
Dave.
This is a test message to see if text formating works correctly;
map (hd0) (hd1)
map (hd2) (hd1)
Ok, there is an issue. I may have overlooked an important point.
g0kth,
Please post the following, as this is getting too difficult to follow. Let's recap.
1. What is your current boot order, pata or sata? In the bios, the order of disk detection, is it;
scsi, ide...
or;
ide, scsi...?
2. Post your current menu.lst or grub.conf file.
3. Post your device.map file.
map (hd0) (hd1)
map (hd2) (hd1)
Ok, there is an issue. I may have overlooked an important point.
g0kth,
Please post the following, as this is getting too difficult to follow. Let's recap.
1. What is your current boot order, pata or sata? In the bios, the order of disk detection, is it;
scsi, ide...
or;
ide, scsi...?
2. Post your current menu.lst or grub.conf file.
3. Post your device.map file.
