Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
I want to dual-boot Windows XP and FC3 64-bit using the Windows boot loader. XP is on a 2-drive SATA RAID 0 configuration, Linux is on an IDE HD set as primary master.
The problem with installing GRUB on the MBR is that LInux does not recognize my RAID configuration; it sees two SCSI drives (no idea why) instead of the 2 SATA drives in RAID. I've already ruined one XP installation with GRUB on the MBR so I'd prefer not to do that again.
I currently have GRUB installed on the first block of the /boot partition. If I bring up the boot menu during BIOS startup and select the hard disk that Linux is installed on, it boots just fine. However, if I attempt to create a bootsect.lnx file and use the Windows bootloader, I get the following:
GRUB _ (underscore blinks)
It doesn't respond to anything except CTRL+ALT+DELETE, which reboots the system.
I used the following command to create bootsect.lnx:
dd if=/dev/hda1 of=/bootsect.lnx bs=512 count=1
This creates the file in the root partition; from there I copy it to a floppy disk, then move into the C:\ directory and modify the boot.ini file accordingly.
This is how I have the drive partitioned:
/boot = /dev/hda1
swap = /dev/hda2
/ = /dev/hda3
I've ran a couple other distros of Linux but mostly for experimentation so I don't know enough to tell whether there's something wrong with the installation or whether I goofed somewhere.
Any ideas?
Last edited by Tarkan2467; 11-29-2004 at 10:01 PM.
3) comments on grub installed...I prefer you use my terminal way to check that the images are TRULY embedded?
4) sata is neither IDE or scsi but its more scsi like from a linux kernel point of view
5) ideally a raid should be seen as one drive as raid attempts to copy data in case of hardware failure. It is NOT a backup solution. If you are using raid because of XP once you are happy with linux use that spare drive for data or images like I use for www.partimage.org
Originally posted by aus9 ...I am just a simple aussie...
Your tutorial proves you wrong! Yes, the configurations are the same. Windows reacts to the bootloader the same way, regardless of the version. Probably this is because the bootloader is actually on the first track of the partition, thus needing the chainloader (FreeBSD requires a chainload boot too).
There's more: another tidbit you may wanna squeeze in there, which may appy to many folks and they don't know what's going on --> what happens if you're stuck at the GRUB commands when booting into Windows XP? Do you try to reinstall Windows' bootloader in the MBR with recovery console and then chroot into your Linux and replace with GRUB? Not likely, as you'll probably find the Win install cd doesn't want to work. If this is the case, use KohlyKohl's suggestion of making sure that the drive is in LBA mode in the BIOS. I've had this happen recently. I don't know what made the BIOS change, but it was set to "auto" which made it default to CHS instead of LBA, making the drive unreadable by the boot cd. Change it back and you might be good to go.
My situation is similar in that I am dual booting between an xp installation on two mirrored raid discs and a 64bit ubuntu installation on a good old IDE disc.
I have seen the problem with the 'GRUB _' (flashing underscore) in quite a few places around the net. I have still to find an explanation as to what is wrong and how to work around the problem. I was happy to see tarkan's post as it describes my situation so accurately.
If anybody has any ideas, I too would be grateful of any hints as I am not exactly a *nix wiz.
Maybe I should add that I copied the boot image off my boot floppy made during the ubuntu installation. Ubuntu boots just fine off the floppy, but stops dead when the same image is loaded from C:\bootsect.lnx (holding the same data). What I should probably do is to install 32 bit ubuntu and see if the problem persists, but by now I have fought this problem for so long that I don't really have the energy for yet another couple of re-installations.
/Lars Ole
Last edited by larsolesimonsen; 03-29-2006 at 01:13 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.