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
Hi Danleff
Ok just to recap on my system I have three hard drives:
160GB SATA holds the Windows XP 64 OS
80GB PATA holds the Fedora Core 4 OS
3GB PATA holds all my data files - docs, pics etc
Under Windows XP these drives are identified as:
160GB - C, E & F
80GB - H
3GB - G
Floppy - A
CD/DVD - D
Under FC4 these drives are identified as:
160GB - sda (sda1, sda5, sda6) or hd2
80GB - hda or hd0
3GB - hdb or hd1
Floppy - fd0
The BIOS boot sequence is:
1st Boot Device - FLOPY DRIVE
2nd Boot Device - CD/DVD
3rd Boot Device - PATA 80GB (FC4)
The Hard Disk boot sequence is :
1 PATA 80GB (FC4)
2 SATA 160GB (Win XP)
3 PATA 3GB (Data)
Note to use Win XP at the moment I have to go into
BIOS and swap 1 & 2 of the Hard disk boot sequence
around but ultimately the boot sequence above is
what I want with the start up menu allowing me to
default to FC4 with the option to select Win XP.
In FC4 starting with the 'Computer' folder I select the following folders to get to grub.conf / menu.lst and the device.map:
Filesystem
boot
grub
The grub.conf file contains 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 partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda1
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 **********************
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,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 Win XP64
rootnoverify (hd1,0)
chainloader +1
The device.map file contains the following:
# this device map was generated by anaconda
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
When I boot up the PC and select FC4 from the menu it loads FC4 ok, if I select Win XP it just hangs.
So that's the current situation. hope that makes things clearer.
If you need any other info let me know.
Cheers
Dave
Ok just to recap on my system I have three hard drives:
160GB SATA holds the Windows XP 64 OS
80GB PATA holds the Fedora Core 4 OS
3GB PATA holds all my data files - docs, pics etc
Under Windows XP these drives are identified as:
160GB - C, E & F
80GB - H
3GB - G
Floppy - A
CD/DVD - D
Under FC4 these drives are identified as:
160GB - sda (sda1, sda5, sda6) or hd2
80GB - hda or hd0
3GB - hdb or hd1
Floppy - fd0
The BIOS boot sequence is:
1st Boot Device - FLOPY DRIVE
2nd Boot Device - CD/DVD
3rd Boot Device - PATA 80GB (FC4)
The Hard Disk boot sequence is :
1 PATA 80GB (FC4)
2 SATA 160GB (Win XP)
3 PATA 3GB (Data)
Note to use Win XP at the moment I have to go into
BIOS and swap 1 & 2 of the Hard disk boot sequence
around but ultimately the boot sequence above is
what I want with the start up menu allowing me to
default to FC4 with the option to select Win XP.
In FC4 starting with the 'Computer' folder I select the following folders to get to grub.conf / menu.lst and the device.map:
Filesystem
boot
grub
The grub.conf file contains 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 partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda1
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 **********************
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,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 Win XP64
rootnoverify (hd1,0)
chainloader +1
The device.map file contains the following:
# this device map was generated by anaconda
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
When I boot up the PC and select FC4 from the menu it loads FC4 ok, if I select Win XP it just hangs.
So that's the current situation. hope that makes things clearer.
If you need any other info let me know.
Cheers
Dave
Interestingly, I just had one of my sata drives go south, so i had to change my setup. This may have shown me a thing or two about the issue. this is why I had a delay in responding to this post.
What happens when you change the Windows entry to;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
or;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
If it still fails, you need to alter your boot,ini file for Windows. To do this, you need to have administrator rights to your Windows installation.
Right click on My Computer, Advanced tab, Startup and Recovery--settings.
under Default OS,==> edit. what is the boot.ini designation for Windows?
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...
Specifically, what is the rdisk value?
What happens when you change the Windows entry to;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
or;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
If it still fails, you need to alter your boot,ini file for Windows. To do this, you need to have administrator rights to your Windows installation.
Right click on My Computer, Advanced tab, Startup and Recovery--settings.
under Default OS,==> edit. what is the boot.ini designation for Windows?
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...
Specifically, what is the rdisk value?
Originally posted by danleff:
Quote:...and what was the solution???? I am interested and others may be as well!Hello,
Well, I changed to this:
Code:
I left the old ones as commented out so you can see what I changed. I Just installed Fedora Core 5 (new install) as I am sure you can tell and it did the same thing. So I had to first boot into resuce mode.
Then I ran the following commands in this order:
Code:
So I will have to do this every time until it's fixed, if it ever is.
Take Care and thanks again for all your help and sorry for such late reply,
Will
Quote:...and what was the solution???? I am interested and others may be as well!Hello,
Well, I changed to this:
Code:
# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You do not have a /boot partition. This means that# all kernel and initrd paths are relative to /, eg.# root (hd2,0)# kernel /boot/vmlinuz-version ro root=/dev/hdf1# initrd /boot/initrd-version.img#boot=/dev/hdf1default=0timeout=5#splashimage=(hd2,0)/boot/grub/splash.xpm.gzsplashimage=(hd0,0)/boot/grub/splash.xpm.gz#hiddenmenutitle Fedora Core (2.6.15-1.2054_FC5) #root (hd2,0) root (hd0,0) kernel /boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quiet initrd /boot/initrd-2.6.15-1.2054_FC5.imgtitle Windows XP rootnoverify (hd1,0) chainloader +1
I left the old ones as commented out so you can see what I changed. I Just installed Fedora Core 5 (new install) as I am sure you can tell and it did the same thing. So I had to first boot into resuce mode.
Then I ran the following commands in this order:
Code:
1.) chroot /mnt/sysimage2.) cd /boot/grub3.) cat grub.conf (just so you can see it in its current form)4.) grub-install --recheck/dev/hdf5.) grub-install /dev/hdf6.) vi grub.conf7.) push a so vi goes into insert (edit) mode8.) Now in the VI editor you change the commented out lines in the code of my grub.conf above so it matchs mine.9.) Now save the new grub.conf by pushing on your keyboard "shift + : ) then hit "w" on the keyboard. Now the new grub.conf file is saved.10.) Reboot computer and everything now works as expected
So I will have to do this every time until it's fixed, if it ever is.
Take Care and thanks again for all your help and sorry for such late reply,
Will
Oh my God! I can't believe that I missed this!
Too many posts from too many folks....
your original grub file;
root (hd0,0)
kernel /vmlinuz-2.6.15-1.1831_FC4 ro root=LABEL=/
initrd /initrd-2.6.15-1.1831_FC4.img
title 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.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
They referenced the same hard drive and partition for Fedora and Windows (red).
Plus, the modular bay apparently changes the sequence of how the drives are detected. So, your root= line for Fedora needed to reference exactly where the root filesystem is, with the modular bay inserted (green).
Nice work!!!
Too many posts from too many folks....
your original grub file;
root (hd0,0)
kernel /vmlinuz-2.6.15-1.1831_FC4 ro root=LABEL=/
initrd /initrd-2.6.15-1.1831_FC4.img
title 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.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
They referenced the same hard drive and partition for Fedora and Windows (red).
Plus, the modular bay apparently changes the sequence of how the drives are detected. So, your root= line for Fedora needed to reference exactly where the root filesystem is, with the modular bay inserted (green).
Nice work!!!
Danleff, You're right too many different things going on now on this topic.
Okay we have finally had success and I can now boot up from the PATA drive with FC4 installed, choose either FC4 or Win XP from the grub menu and run the chosen OS. So thanks for your help.
Just for completeness and future info I have answered your questions below:
You wrote:
What happens when you change the Windows entry to;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
OUTCOME:
I get the following dislayed on the screen:
Booting 'Win XP64'
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
GRUB _ (where _ is a flashing cursor).
You wrote:
or;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
OUTCOME:
This will successfully launch the chosen OS from the grub menu.
You wrote:
If it still fails, you need to alter your boot,ini file for Windows.......... what is the boot.ini designation for Windows?
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...
Specifically, what is the rdisk value?
THE RDISK VALUE IS rdisk(0), the rest of the values are as listed in your question.
Hope that helps. Thanks again for your help and from my point of view this topic has now been resolved and can be closed.
Okay we have finally had success and I can now boot up from the PATA drive with FC4 installed, choose either FC4 or Win XP from the grub menu and run the chosen OS. So thanks for your help.
Just for completeness and future info I have answered your questions below:
You wrote:
What happens when you change the Windows entry to;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
OUTCOME:
I get the following dislayed on the screen:
Booting 'Win XP64'
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
GRUB _ (where _ is a flashing cursor).
You wrote:
or;
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1
OUTCOME:
This will successfully launch the chosen OS from the grub menu.
You wrote:
If it still fails, you need to alter your boot,ini file for Windows.......... what is the boot.ini designation for Windows?
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP...
Specifically, what is the rdisk value?
THE RDISK VALUE IS rdisk(0), the rest of the values are as listed in your question.
Hope that helps. Thanks again for your help and from my point of view this topic has now been resolved and can be closed.
