FedoraThis forum is for the discussion of the Fedora Project.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello
I just installed Fedora15 on my laptop. When the installation completed, the system rebooted and gave me a Grub Error 17. I logged in the rescue mode and got the following output from
Code:
fdisk -ls
Code:
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0d8b0d8a
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 488394751 244093952 7 HPFS/NTFS/exFAT
Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ea52b
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 1026047 512000 83 Linux
/dev/sdb2 1026048 488396799 243685376 8e Linux LVM
Disk /dev/sdc: 8011 MB, 8011120640 bytes
41 heads, 41 sectors/track, 9307 cylinders, total 15646720 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18
Device Boot Start End Blocks Id System
/dev/sdc1 * 8064 15646719 7819328 7 HPFS/NTFS/exFAT
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home: 190.6 GB, 190555619328 bytes
255 heads, 63 sectors/track, 23167 cylinders, total 372178944 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 5268 MB, 5268045824 bytes
255 heads, 63 sectors/track, 640 cylinders, total 10289152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
and grub.conf
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 (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sdb
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.38.6-26.rc1.fc15.i686.PAE)
root (hd0,0)
kernel /vmlinuz-2.6.38.6-26.rc1.fc15.i686.PAE ro root=/dev/mapper/VolGroup-lv_root rd_LVM_LV=VolGroup/lv_root rd_LVM_LV=VolGroup/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.38.6-26.rc1.fc15.i686.PAE.img
title Other
rootnoverify (hd1,0)
chainloader +1
Is sdb listed first in your boot priority in BIOS?
It should be.
If it is, you may have to make your windows entry look like this
Code:
title Windows
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
To trick windows into thinking that it is on the first drive.
hi andrewthomas and thanks for replying
I think that the first drive that my laptop's BIOS recognize is the Windows one. There is no info about that in the BIOS but I checked my disks before I install FC15 with the Sisoftware Sandra tool and the first one given was the windows. Also, when I was configuring the installation of FC15, after the step where I chose to "Remove all Linux systems" only, I tried both of the given disks because their description was the same and it let me move to the next step only when I chose the second drive because it was the disk with my previous Linux distro. It would be nice if there is a way to find the order of the disks in the BIOS through the command line.
I change my grub.conf as you suggested but it still gives me the same error.... I had this problem since FC14 and because of that I had to use Opensuse which had no problem whatsoever.
Do you get the above error when you select Fedora from the Grub boot menu? The error indicates Grub sees the partition but doesn't recognize the filesystem. This usually means a windows filesystem.
If so, reverse the grub.conf entries for Fedora and windows:
Fedora root (hd1,0), windows rootnoverify (hd0,0)
I expect you have installed Grub to the mbr of sda. If this is the problem, I'm not sure why it would have happened if you had both drives attached during the installation?
You can find out how Grub sees your drives with the geometry command to verify this. Boot into rescue mode, log in as root, enter grub at the prompt and you will see a grub prompt: grub> From here just enter: geometry (hd0), geometry (hd1) and geometry (hd2). You need to hit the Enter key after each command to get output. You should then be able to compare this output to the fdisk output as each drive has different partition types.
If you have now changed the grub entry for windows, then just switch the order of the drives in BIOS and see if it works.
how can I do that? In the BIOS there is no such option (my laptop: hp pavillion dv7-1199ev). Should I try and change the numbers in the grub.conf file?
how can I do that? In the BIOS there is no such option (my laptop: hp pavillion dv7-1199ev). Should I try and change the numbers in the grub.conf file?
If you can't switch the order in BIOS, do as yancek suggested and switch the drives in grub and remove the modification that I gave you for the windows drive
Do you get the above error when you select Fedora from the Grub boot menu? The error indicates Grub sees the partition but doesn't recognize the filesystem. This usually means a windows filesystem.
If so, reverse the grub.conf entries for Fedora and windows:
Fedora root (hd1,0), windows rootnoverify (hd0,0)
I expect you have installed Grub to the mbr of sda. If this is the problem, I'm not sure why it would have happened if you had both drives attached during the installation?
You can find out how Grub sees your drives with the geometry command to verify this. Boot into rescue mode, log in as root, enter grub at the prompt and you will see a grub prompt: grub> From here just enter: geometry (hd0), geometry (hd1) and geometry (hd2). You need to hit the Enter key after each command to get output. You should then be able to compare this output to the fdisk output as each drive has different partition types.
hi yancek
I get the error just after BIOS initialization - I don't see any grub GUI or text, just the error.
I just tried reversing the entries for FC15 and win7 in the grub.conf with and without the 'map' entries and it didn't work. Why is it so difficult to configure grub?? I don't get it..
If you can't switch the order in BIOS, do as yancek suggested and switch the drives in grub and remove the modification that I gave you for the windows drive
on which drive should the splashimage be directed if I reverse the order of the disks in the grub.conf? or it doesn't matter? do I have to change anything else that points to the disks or just the two number for linux and windows hd?
on which drive should the splashimage be directed if I reverse the order of the disks in the grub.conf? or it doesn't matter? do I have to change anything else that points to the disks or just the two number for linux and windows hd?
I just managed to make the boot screen appear. After numerous tries and guidance from people in this forum and fedoraforum. Thank you.
So, what I did was to boot in the update mode with the help of the dvd and reinstalled the bootloader with the following options:
1) Install bootloader on /dev/sda
1.1) Master Boot Record (MBR) - /dev/sda
2) Boot loader operating system list = Fedora /dev/mapper/VolGroup-lv_root
This is the new grub.conf file
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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.38.6-26.rc1.fc15.i686.PAE)
root (hd1,0)
kernel /vmlinuz-2.6.38.6-26.rc1.fc15.i686.PAE ro root=/dev/mapper/VolGroup-lv_root rd_LVM_LV=VolGroup/lv_root rd_LVM_LV=VolGroup/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.38.6-26.rc1.fc15.i686.PAE.img
title Other
rootnoverify (hd0,0)
chainloader +1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
