Mike wrote:
Bear with me on this one... I have 3 hard drives, hda is a ntfs drive
for extra space on windows, hdb is supposed to be a debian etch drive...
And the kicker, sda is the windows drive with the master boot record.
When I install debian testing it see's windows on sda but installs the
mbr on hda. (the extra ntfs drive that is nothing more than extra
space). I figure, no big deal, it should still be able to call sda for
windows and hdb for linux even if its there. Nope, it won't boot the
SATA windows drive (sda) but it boots hdb (debian) just fine. So I
figure, ok.... grub-install /dev/sda. But instead of working it starts
up giving me this
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB.... (to infinity, it just
keeps going forever)
So of course now windows doesn't boot anymore so I boot to the xp cd and
fixmbr... which also stuffs it on hda with the RETARDED F6 YOU HAVE TO
GO TO A MUSEUM TO GET A 1.44 MB FLOPPY DRIVE TO LOAD SATA DRIVERS FOR
WINDOWS AT BOOT TIME. (yes, i think that was ill thought out for
something written from 2000-2003). So whatever... I unhook all of the
other drives and fixmbr again to fix the problem.
Now that is fine and all, but now i'm right back where i began....
except with ntloader on hda instead of grub because windows wanted it on
with a rescue disk to fix that one too.
So if no matter what I do, its always going to install the MBR on hda if
it has a choice with both SATA and ATA drives in the same system. How do
I get around something like this? I just want the mbr on sda so grub can
boot both drives. Or am I going about this all wrong
/dev/hda (ntfs windows extra space)
/dev/hdb (ex3 linux)
/dev/sda (ntfs windows drive with MBR)
Any suggestions?
You can put grub anywhere, for my Thinkpad-t42 I have it on hda4:
grub
root (hd0,3)
setup (hd0)
quit (or exit?)
on my USB-hd on same PC, not normally attached, on sda4:
grub
root (hd1,3)
setup (hd1)
If I ran this while a HD was in cdrom/dvd bay then instead of hd1 it
would be hd2 (the hdc would be hd1),
Meanwhile on the debian auto install, you may need simply only change
the /boot/grub/menu.lst to point to the correct disk for WinJunk, see
GRUB-doc.
By the way, my "3" points to hda4 and sda4, each has my /boot/grub/stuff
with a mini-linux (RIP).
====================== this boots partitions on hda and hdc from hda4
# grub.conf: grub : root (hd0,3) : setup (hd0) GRUB_PARTION=hda4/BKUP
#
timeout 8
color black/cyan yellow/cyan
default 3
fallback 1
# hd0,1 = hda2 = extended
# hd0,2 = hda3 = VFAT
# hd0,4 = hda5 = swap
# hd0,6 = hda7 = DATA
title [0] WinXT (PARTITION 1)
rootnoverify (hd0,0)
chainloader +1
title [1] FIX-RIP on BKUP (PART4) RecoveryIsPossible
Locus_of_GRUB-BOOT-file
kernel (hd0,3)/boot/kernel root=/dev/hda4 vga=2 acpi=off
title [2] Debian-Linux-Sid(PART6) Failsafe/DebSid-copy
kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 vga=791 selinux=0 noresume
initrd (hd0,5)/boot/initrd.img
title [3] Debian-Linux-Sid(PART8) NORMAL
kernel (hd0,7)/vmlinuz root=/dev/hda8 vga=791 selinux=0 resume=/dev/hda5
initrd (hd0,7)/initrd.img
title [4] SUSE-Linux-10 (PART9) NORMAL
kernel (hd0,8)/boot/vmlinuz root=/dev/hda9 vga=791 selinux=0
splash=silent resume=/dev/hda5 showpts
initrd (hd0,8)/boot/initrd
title [5] SUSE-Linux-10 (PART9) Failsafe
kernel (hd0,8)/boot/vmlinuz root=/dev/hda9 showopts ide=nodma
acpi=off vga=2 noresume selinux=0 barrier=off nosmp noapic
initrd (hd0,8)/boot/initrd
title [6] Debian-Linux (DISK2-in-cdrom-bay-PART2)
kernel (hd1,1)/vmlinuz root=/dev/hdc2 vga=791 noresume
initrd (hd1,1)/initrd.img
title [7] SUSE-Linux (DISK2-in-cdrom-bay-PART6)
kernel (hd1,5)/boot/vmlinuz root=/dev/hdc6 vga=791 selinux=0
splash=silent resume=/dev/hda5 showpts
initrd (hd1,5)/boot/initrd
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
