[CALUG] Newbie questions
rmain at polaris.umuc.edu
Mon Sep 26 08:04:00 CDT 2005
I'll post the contents of grub.conf and the output of fdisk -l as soon as
I possibley can. As funny as it may sound, it may take me a few days to
get back to you folks because of work and school.
Thanks again for all the help.
On Sun, 25 Sep 2005, Rajiv Gunja wrote:
> It would have greatly helped if you had attached your grub.conf and the
> output of "fdisk -l" command.
> However, from your explanation, I am interested to know what really your
> grub.conf has.
> One small explanation for Windows 98 not booting could be that Windows 2003
> might have over written its boot code to enable dual boot between 2003 and
> 98, but since we have RH9 on the MBR, that could have been lost.
> Next time you login to RH9, type grub as root and at the prompt.
> grub> root (hd0,<tab>
> grub> root (hd1,<tab>
> Paste that output, so we can really give u the right solution.
> If you want to read about grub, there is a 3 page text in "Linux in a
> If infact Windows 98 boot code is lost, you might have to "rescue" windows
> 98 and fix the boot with the rescue floppies and then install grub again.
> I know, when you install Windows 98 mbr, grub will be lost. Not to worry,
> you can backup grub.
> Put these lines in a script and run it.
> ### Copy Grub to Floppy ####
> mkfs.ext3 /dev/fd0
> mount /dev/fd0 /mnt/floppy
> cd /mnt/floppy
> mkdir boot
> cd boot
> mkdir grub
> cd /boot/grub
> cp stage1 /mnt/floppy/boot/grub
> cp stage2 /mnt/floppy/boot/grub
> cp menu.lst /mnt/floppy/boot/grub
> cp /etc/grub.conf /mnt/floppy/boot/grub
> grub --batch --device-map=/dev/null <<EOF
> device (fd0) /dev/fd0
> root (fd0)
> setup (fd0)
> #### End of Script ####
> Once that is done and you have installed grub again to the mbr, take a
> backup of your mbr.
> *dd if=/dev/hda of=mbr.bkp.09252005 bs=512 count=1*
> and copy this file to your floopy or other partitions so you have easy
> access to it.*
> *Hope this helps*
> Rajiv G Gunja
> On 9/25/05, Russ <rmain at polaris.umuc.edu> wrote:
> > OK
> > Well, here's what I did. Since I had all three OS's already installed, I
> > reinstalled RH9. Anaconda ran Disk Druid, and I set it to format only the
> > Linux and swap partitions. On the setup screen for GRUB, the only
> > recognized partitons were Linux and DOS?. Linux is hda1, Windoze 98 is
> > hda2, Linux swap is hda3, and Windoze Server 2003 is hdb1. So, I left
> > Linux hda1 as default. Next, I renamed DOS to be Win98, and I added the
> > additional drive/hdb1 as Win Server 2003. So, heres what happens. Linux
> > RH9 boots to GRUB giving me the choices of RH9, 98, or 2003. Choosing 98
> > boots 2003. Choosing 2003 only outputs the text "chainloder +1". Doesnt
> > the command chainloder +1 start a second drive or does it start the second
> > bootable partition. I'n not sure how or why choosing 98 starts Server
> > 2003. The GRUB choice of 98 has the instructions rootnoverify hd0,1
> > folowed by chainloader +1. The Server 2003 has the instructions
> > rootnoverify hd1,0 followed by chainloader +1. Not knowing a whole
> > about these commands they seem correct. However choosing 98 starts 2003
> > and choosing 2003 ends in error. One last note, the 98 version is a HP
> > restore disk install.
> > Thanks very much for the help so far.
> > Russ M
More information about the lug