2 drives, dual boot configure with Suse,Fedora

[mjmesserly]

I have looked at a number of the threads about this and there are some gaps that I could use some help with. Currently have a Suse 10.3 A x64 working on sda. I installed a second identical drive. Installed the Fedora Core 6 x64 on sdb. I checked the Fedora install to put grub on the MBR sda and figured I'd have to edit/configure grub to 'see' both options. The Suse boots as before, no other options listed in grub.

I am at the point where I am unsure how to 'access' or 'mount' sdb in order to look at the config in order to get info to edit/configure grub, or other manual command line boot options to get the dual syatem to appear/work.

I noticed that the fstab in my original Suse system lists only sda.

/dev/sda1 swap swap defaults 0 0
/dev/sda2 / reiserfs acl,user_xattr 1 1
/dev/sda3 /home reiserfs acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0

What I was wondering is what are the two numbers at the end of the lines /dev/sda... if I edit this to include the sdb info would I be able to mount it or otherwise 'see' the Fedora install?

New to linux, thanks for your patience.

Other suggestions/ steps welcome. Thank you.

[devils casper]

What I was wondering is what are the two numbers at the end of the lines /dev/sda... if I edit this to include the sdb info would I be able to mount it or otherwise 'see' the Fedora install?

first digit is dump option. dump uses the number to decide if a filesystem should be backed up. if it's zero, dump will ignore that filesystem. its zero in most cases.
second digit is fsck option. fsck uses this number to determine in which order the filesystems should be checked. If it's zero, fsck won't check the filesystem.
no need to add enrty of sdb in fstab file for dual boot setup.

boot up SuSe. log in as root and execute this

fdisk -l
less /boot/grub/device.map

post output here.

[mjmesserly]

Thanks for your time. The fdisk -l produces:

Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 * 263 2873 20972857+ 83 Linux
/dev/sda3 2874 18241 123443460 83 Linux

Disk /dev/sdb: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 18241 146416410 8e Linux LVM

Disk /dev/dm-0: 147.8 GB, 147840827392 bytes
255 heads, 63 sectors/track, 17973 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 2046 MB, 2046820352 bytes
255 heads, 63 sectors/track, 248 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table


and the less /boot/grub/device.map contains only

(hd0) /dev/sda


Thanks for looking. MM

[devils casper]

log in as root and execute this

mkdir /media/Fedora
mount -t ext3 /dev/sdb1 /media/Fedora
less /media/Fedora/boot/grub/grub.conf

post contents of grub.conf file.

[mjmesserly]

Thank you again. The path for the grub.conf was slightly different: /media/Fedora/grub/grub.conf

The less grub.conf command generated


# 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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6)
root (hd1,0)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb qu
iet
initrd /initrd-2.6.18-1.2798.fc6.img


Your generosity with your time and knowledge is appreciated.

[devils casper]

boot up SuSe, log in as root and open /boot/grub/menu.lst file.
add this code at the end of file.

title Fedora Core (2.6.18-1.2798.fc6)
root (hd1,0)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.18-1.2798.fc6.img

save file and reboot.

[mjmesserly]

Your knowledge and willingness to share time is appreciated. I saw this process in another post, I was having trouble applying it in this case. Your guidance was right on the mark.

Thank you.

[devils casper]

i am glad i could help you.

[CapnGimp]

I googled this, it is near identical to my situation, about to try it.
I installed Fedora 7 and updated/set it up how I wanted it on second drive. Downloaded, burned, installed SUSE 10.3 to sda1..... noticed as I was installing that I didn't get asked where to install grub/bootloader, got to worrying
BAM, no Fedora, lol.
I have been bouncing back and forth between my user and root accounts to follow your instructions. Emailed this page to yahoo and it wasn't there... just my luck,,, so I'm registered and hope to mark this thread to find it on the root side.> big grin <
I'll post my results, Thanks a million for your help. BTW, this is going to be a PURE Linux computer from now on. Been fiddling with Linux since 97 and it is time.

[CapnGimp]

forgot to return and post SUCESS!
Thanks a million!