[Panic] Grub fail to dual boot win XP/Fedora Core 3 on Dell Laptop Latitude D610
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.
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.
[Panic] Grub fail to dual boot win XP/Fedora Core 3 on Dell Laptop Latitude D610
Hello all,
I have installed FC3 on my dell latitdue D610 laptop with only 1 hard disk, and with windows XP installed.
Problem:
When I reboot the laptop after FC 3 installation, all I see is just "GRUB" with a flashing _ then nothing happens and I cant access any OS's.
I guess some info might be helpful:
1. RH9 was previously installed at an extended partition. So in this installation, I use Fedora partitioning utility to choose this partition as mount point, and format as ext3.
2. GRUB is chose to install at "first boot partition", not MBR. (hope I didnt mistaken...)
3. Windows is picked to boot first.
I have tried to search for some solutions on the Internet, can't seems to have a perfectly match scenario and solutions to this problem. But i do found some info that worry me, such as
"Dell has some type of recovery data that came with the machine on /dev/hda1"
--> since i chose to install GRUB at "first boot partition", will it destroy these info?? What's the consequence?
I have managed to get my grub.conf via linux rescue
# grub.conf generated by anaconda
# Notice: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd1,5)
# kernel /boot/vmlinuz-version ro root=/dev/sda6
# initrd /boot/initrd-version.img
#boot=/dev/sda6
default=1
timeout=5
splashimage=(hd1,5)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora Core 3
root (hd1,5)
kernel /boot/vmlinuz-2.6.9-1.667 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.9-1.667.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1
Now, based on this info
1) has GRUB installed at first boot partition?
2) To install GRUB at MBR,
grub> root (hd ? , ?) <-- what should i type?
grub> setup (hd ?) <-- what should i type?
GRUB is chose to install at "first boot partition", not MBR.
How your computer boots: BIOS initializes the hardware and last thing it does is to execute MBR (Master Boot Record) from your first HDD. Now, if you had GRUB there it would present you with a menu and continue executing bootup files of your OS of choice. You installed GRUB to first bootable partition. In other words, there is still Windows code on the MBR which does nothing about multi-boot and tries to boot Windows - but finds GRUB instead. GRUB in turn does not know what to do because it's installed to wrong partition ...
You are not first one with such a problem, search these forums, it is handled here many (many-many) times.
Something is wrong here. You have only one HDD so it cannot be "root (hd1,5)". I would start with fdisk -l to see how HDD is connected and partitioned, then mount your Linux root partition and look at GRUB device.map file to see if GRUB has mapped your HDD correctly. Finally, edit your grub.conf file to make entries reflect the real setup and run 'grub-install /dev/hda'.
Disk /dev/sda: 40.0GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 Dell Utility
/dev/sda2 * HPFS/NTFS
/dev/sda3 W95 Ent's (LBA)
/dev/sda5 HPFS/NTFS
/dev/sda6 Linux
/dev/sda7 Linux swap
Disk /dev/hda: 515MB, 515375104 bytes
...
Device Boot Start End Blocks Id System
/dev/hda1 * FAT16
1. nothing to change in /boot/grub/grub.conf before 'grub-install /dev/hda'?
2. In this case, should I type 'grub-install /dev/hda' , or 'grub-install /dev/sda'?? Since /dev/sda is the hard disk...
> grub-install /dev/sda
Output: The file /boot/grub/stage2 not read correctly.
Notice at #4,
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd1,5)/boot/grub/stage2 /boot/grub/grub.conf
I redo the following, and found out
grub> find /boot/grub/stage1
(hd1,5)
grub> root (hd1,5)
Filesystem type is ext2fs, partition type 0x83
grub> root (hd0,5)
Error 22: No such partition
Also, since hda is CDROM drive, if I remove it from device.map, possibly the CDROM will not be able to boot from CD anymore for the next hard reboot(i just guess), so in device.map, I change
You do not need CD drive in device.map. CD is booted by BIOS, not GRUB. You need probably to chroot to make grub-install work correctly. Or use --root-directory=/path_to_mounted_Fedora_root, see 'man grub'.
Curious to ask,
1) Why installing GRUB to first boot partition will lead to invalid device.map configuration?
2) Why the hard disk label is /dev/sda, but not /dev/hda ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.