Do 2 harddrives have to be Master/Slave?

david_ross · 08-07-2003, 10:54 AM

grub.conf is just a text file. Just open it in a text editor:
vi /boot/grub/grub.conf

Then change the valuse you need so that the windows system is referenced properly.

Best to make a backup copy first

:
cp /boot/grub/grub.conf /boot/grub/grub.conf.bak

RAL · 08-07-2003, 05:58 PM

The text editors are both denying me access to grub.conf.

fancypiper · 08-07-2003, 06:24 PM

To change to the root account, open an x terminal and use these commands from your user account. Note the change in the prompt.

Code:

[fancy@tinwhistle fancy]$ su -
Password: 
[root@tinwhistle root]#

Now you will have permission.

RAL · 08-08-2003, 03:55 PM

Thanks, between fancypiper and david_ross I finally got in there.
BUT I must have entered something wrong.
Here is what I have.
-----------------------------------------------------------------
title Red Hat Linux (2.4.18-14)
root (hd0,0)
Kernal /vmlinuz-2.4.18-14 ro root=LABEL=/
initrd /initrd-2.4.18-14.img
title Windows98
rootnoverify (hd1,0)
map (hd1))hd0)
map (hd0)(hd1)
makeactive
chainloader+1
------------------------------------------------
originally after the Linux part there was a Dos loader which I removed.
Linux is on hda, Windows is on hdc
Am I almost there?

fancypiper · 08-08-2003, 06:01 PM

That looks like your /boot/grub/grub.conf file. Use the code tags (button labled #) to post commands, config files, etc.

Installing a bootloader
Multiboot with GRUB Mini-HOWTO

For your reference, here is my partitioning:

Code:

[fancy@tinwhistle fancy]$ su -
Password: 
[root@tinwhistle root]# fdisk -l

Disk /dev/hdc: 255 heads, 63 sectors, 4867 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1   *         1      4867  39094146   83  Linux

Disk /dev/hda: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1      1217   9772056    c  Win95 FAT32 (LBA)
/dev/hda2   *      1217      1229     99855   83  Linux
/dev/hda3          1230      1656   3429877+  83  Linux
/dev/hda4          1657      4865  25776292+   5  Extended
/dev/hda5          1657      1719    506016   82  Linux swap
/dev/hda6          1720      2146   3429846   83  Linux
/dev/hda7          2147      2573   3429846   83  Linux
/dev/hda8          2574      3719   9205213+  83  Linux
/dev/hda9          3720      4865   9205213+  83  Linux
[root@tinwhistle root]#

And here is my /etc/fstab file:

Code:

# Celeron 850 tinwhistle /etc/fstab/file
/dev/hda6	/			ext3		defaults	1 1
/dev/hda2	/boot			ext3		defaults	1 2
none            /dev/pts		devpts		gid=5,mode=620  0 0
/dev/hda8	/home			reiserfs	defaults	1 2
#/dev/hda3	/mnt/gentoo		reiserfs	defaults	1 2
#/dev/hda7	/mnt/mandrake		ext3		defaults	1 2
/dev/hda1	/mnt/winc		vfat		defaults	0 0
none            /proc			proc		defaults	0 0
none            /dev/shm		tmpfs		defaults	0 0
/dev/hdc1	/pub			ext3		defaults	1 2
/dev/hda9	/snd			reiserfs	defaults	1 2
/dev/hda5	swap			swap		defaults	0 0
/dev/cdrom	/mnt/cdrom		iso9660		noauto,owner,ro 0 0
/dev/fd0        /mnt/floppy		auto		noauto,owner    0 0

And here is my /boot/grub/grub.conf file:

Code:

# Celeron Coppermine 850 tinwhistle box /boot/grub/grub.conf file
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Red Hat Linux 7.3
        root (hd0,1)
        kernel /vmlinuz-2.4.18-3 ro root=/dev/hda6
        initrd /initrd-2.4.18-3.img
title Mandrake 9.0
        kernel (hd0,6)/boot/vmlinuz root=/dev/hda7 quiet devfs=mount vga=788
        initrd (hd0,6)/boot/initrd.img
title Gentoo
	root (hd0,1)
        kernel (hd0,1)/boot/bzImage root=/dev/hda3
title Windows 98 Sucky Edition
        rootnoverify (hd0,0)
        chainloader +1

HTH

david_ross · 08-09-2003, 06:48 AM

Your map command has "))" and it should have ")("

RAL · 08-10-2003, 05:39 PM

Thanks again, especially to fancypiper and david_ross.
I finally got through to Win98.
I was leaving out spaces
(hd1) (here) (hd0)
(hd0) (here) (hd1)
chainloader (and here) +1
Thanks again
RAL

whansard · 08-10-2003, 06:32 PM

Quote:

Originally posted by Saraev
Correct me if I'm wrong, but doesn't throwing a CDrom/DVD/burner on the same cable as a hard drive cause the whole cable to run at DMA33 instead of 66/100/133 ? For that reason alone I keep my cd drives on the secondary chain.

nope. but it can definately slow a hard drive down.
if you have a hard drive on the same cable as a cdrom
drive, and put a cdrom in the drive that the drive can't
read, your system will slow to a crawl, because the
cdrom will keep getting that bus locked to try to read
things it can't and will hang up everything. whatever is
sharing a cable, cannot both be transferring data on the
cable at the same time. they take turns.
the master should be at the end of the cable, with the
slave in the middle, but it will usually work both ways
with the old style 40 pin cable.
lots of drives will not work well together at top speed.
i've often had to slow down a drive a dma mode or 2
when it has another drive on the cable with it, to get it
to work right. luckily with most drives it makes little
difference between the top 2 speeds the drive will run
at. some basically run the same speed at udma 66 or
100.
it's also possible to run both drives in cable select mode.
it's called cable select, because the cable is what
decides which drive is the master or slave. you can
buy or alter your own cable for this purpose. in this
situation both drives are set to cable select, and the
special cable with one of the wires to the master cut,
and, the drives get set master or slave by where they
are on the cable. this can be handy for moving drives
around without having to change jumpers. i can't
remember which pin to cut though, but i'm sure you
could find it on the web.

also, lots of cdrom drives will mess each other up
being on the cable with each other. i'll sometimes
go thru a stack of different brands and speeds of
cdrom drives and burners trying to find 2 that will
work together perfectly on a machine, with both in
dma mode. hopefully the new serial drives will
get rid of this madness. ( while probably introducing
a new madness of their own).

i just found some newer information on CS, that
corrects a few errors on my part. it's good info.

http://www.pcguide.com/ref/hdd/if/ide/confCS-c.html