Help with grub setup for dual-boot system
in [Setup]
|
Prev: Totem movie player
Next: IPTABLES
From: anoneds on 9 Nov 2005 08:30 I used grub-install after Win98SE overwrote the master boot record removing grub. Now, grub will not boot Win98. I've tried modifying grub.conf, uncommenting boot=/dev/hda as well, now getting error 18. If I leave it commented out now (since I have a /boot) it still gives error 18, but I know the /boot partition is near the front of the drive. Here is my grub.conf: # 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,1) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=15 splashimage=(hd0,1)/grub/splash.xpm.gz title Fedora Core (2.6.5-1.358) root (hd0,1) kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ hdd=ide-scsi rhgb initrd /initrd-2.6.5-1.358.img title DOS rootnoverify (hd0,0) chainloader +1 I've looked at the grub info and tried adding "makeactive" as it states both before and after the "chainloader" with no effect. When I tried booting off of Win98SE cd, and used fdisk, it asked if I wanted to enable large disk support (thought I'd done this already). I escaped, and looked at the partition table, looked good. rewrote the mbr (fdisk /mbr), which just froze the boot with "grub" in the upper left corner, so I had to boot off fedora core 2 in rescue mode and rerun grub-install to get back to where I am now. My device map is: # this device map was generated by anaconda (fd0) /dev/fd0 (hd0) /dev/hda And grub is better than lilo how? Any suggestions?
From: Nico Kadel-Garcia on 9 Nov 2005 08:50 <anoneds(a)netscape.net> wrote in message news:1131543054.679470.146690(a)g14g2000cwa.googlegroups.com... >I used grub-install after Win98SE overwrote the master boot record > removing grub. > Now, grub will not boot Win98. Ouch. Win98 is no longer supported by M$ at all, so you might want to think about updating that. Leaving details of your post out, did you do anything else at the time, like repartitioning your Windows disk to install Linux as well on it? And when you installed grub, I assume you did a "grub-install /dev/hda" to actually install that little bit of grub to the /dev/hda that you needed? And did you by any chance fail rebooting 3 times in a row, which resets your BIOS to its defaults and may cause other interesting issues if your BIOS needs special settings to boot Win98 successfully? > And grub is better than lilo how? > Any suggestions? Hey, friend, no guarantee that lilo would work in this situation until you actually try it and figure out what the problem is. grub is better than lilo because it allows a lot more flexibility, it doesn't force you to re-write the MBR and imperil your previously working kernel setup to install a new one, and it avoids a lot of the limitations of /boot having to be on a partition entirely contained within the first 1023 cylinders of the disk (which is less of a limit now, but it was a real pain of lilo when grub first came out).
From: anoneds on 9 Nov 2005 14:08 Nico Kadel-Garcia wrote: > <anoneds(a)netscape.net> wrote in message > news:1131543054.679470.146690(a)g14g2000cwa.googlegroups.com... > >I used grub-install after Win98SE overwrote the master boot record > > removing grub. > > Now, grub will not boot Win98. > > Ouch. Win98 is no longer supported by M$ at all, so you might want to think > about updating that. Leaving details of your post out, did you do anything > else at the time, like repartitioning your Windows disk to install Linux as > well on it? And when you installed grub, I assume you did a "grub-install > /dev/hda" to actually install that little bit of grub to the /dev/hda that > you needed? And did you by any chance fail rebooting 3 times in a row, which > resets your BIOS to its defaults and may cause other interesting issues if > your BIOS needs special settings to boot Win98 successfully? No, I did no repartitioning. I'd tried debugging a Lan card and Win98 deleted ALL the drivers under control-panel - network, and something got corrupted, I'm guessing the tcp/ip stack between the apps (IE 6.0/Firefox) and DUN. Because of this (and other issues), I decided to re-install Windows over itself. It nicely overwrote the mbr, removing grub, and didn't fix any issues (seeing the files already there, I guess). So, I booted off of FC 2 in rescue mode, used grub-install to replace grub in the mbr. Thought the issue was solved, until I tried booting into Windows the next time. I did "grub-install hd0" and "grub-install /dev/hda". And my bios didn't reset because of failing to boot. But I'm pretty sure when I installed Windows on this disk a couple years back (I had a hard drive failure requiring a reformat) I chose large disk support. When I booted off of the Windows CD, it asked if I wanted to enable that. So, I chose not too (not wanting to really screw things up further). Thought of booting up and using "sys c:" as an earlier poster to this group used, a little afraid I'd wind up with nothing. And now I get the "ERROR 18" which appears to tell me that my "/boot" has to be within the first section of the drive, which it most certainly is.
From: Chaz Ginger on 9 Nov 2005 14:30 It's been a while since I played around with Windows and setup a dual-boot system (now I use VMWare..I get to run Windows under Linux at the same time! So much nicer!). I think the problem is that grub needs the windows boot loader to chain to. The way I would do this is as follows: 1) Under windows from Fdisk /mbr 2) Boot up a Linux environment from CD and re-install GRUB. This will create the chain loader that grub needs. You should be all set. The other way to do it is create the Windows Chain loader directly, using dd. As I said I haven't done this in a few years and my brain cells are a bit rusty. Peace, Chance anoneds(a)netscape.net wrote: > Nico Kadel-Garcia wrote: > >><anoneds(a)netscape.net> wrote in message >>news:1131543054.679470.146690(a)g14g2000cwa.googlegroups.com... >> >>>I used grub-install after Win98SE overwrote the master boot record >>>removing grub. >>>Now, grub will not boot Win98. >> >>Ouch. Win98 is no longer supported by M$ at all, so you might want to think >>about updating that. Leaving details of your post out, did you do anything >>else at the time, like repartitioning your Windows disk to install Linux as >>well on it? And when you installed grub, I assume you did a "grub-install >>/dev/hda" to actually install that little bit of grub to the /dev/hda that >>you needed? And did you by any chance fail rebooting 3 times in a row, which >>resets your BIOS to its defaults and may cause other interesting issues if >>your BIOS needs special settings to boot Win98 successfully? > > > No, I did no repartitioning. I'd tried debugging a Lan card and Win98 > deleted ALL the drivers under control-panel - network, and something > got corrupted, I'm guessing the tcp/ip stack between the apps (IE > 6.0/Firefox) and DUN. Because of this (and other issues), I decided to > re-install Windows over itself. It nicely overwrote the mbr, removing > grub, and didn't fix any issues (seeing the files already there, I > guess). > > So, I booted off of FC 2 in rescue mode, used grub-install to replace > grub in the mbr. Thought the issue was solved, until I tried booting > into Windows the next time. I did "grub-install hd0" and "grub-install > /dev/hda". And my bios didn't reset because of failing to boot. But I'm > pretty sure when I installed Windows on this disk a couple years back > (I had a hard drive failure requiring a reformat) I chose large disk > support. When I booted off of the Windows CD, it asked if I wanted to > enable that. So, I chose not too (not wanting to really screw things up > further). > > Thought of booting up and using "sys c:" as an earlier poster to this > group used, a little afraid I'd wind up with nothing. > > And now I get the "ERROR 18" which appears to tell me that my "/boot" > has to be within the first section of the drive, which it most > certainly is. >
From: anoneds on 9 Nov 2005 23:08
Chaz Ginger wrote: > It's been a while since I played around with Windows and setup a > dual-boot system (now I use VMWare..I get to run Windows under Linux at > the same time! So much nicer!). > > I think the problem is that grub needs the windows boot loader to chain > to. The way I would do this is as follows: > > 1) Under windows from Fdisk /mbr > 2) Boot up a Linux environment from CD and re-install GRUB. > > This will create the chain loader that grub needs. You should be all > set. The other way to do it is create the Windows Chain loader directly, > using dd. > > As I said I haven't done this in a few years and my brain cells are a > bit rusty. That's what I thought. I've already tried "fdisk /mbr" from the Windows CD. Question is: does it make a difference whether it is done from the OS the CD loads vs. the OS on the disk itself? You see, I have no access to a startup disk anymore, as my motherboard stopped working with 3.5" floppies some time back. Yes, it is time for some new hardware. Maybe a new OS, but I really don't care to put anymore money in Micro$oft's pockets. Just keep what I have. Convert it as necessary. As for using dd to create it directly? I didn't know this was an option... |