Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 20
My only drive has a separate primary boot partition with GRUB on sda1. I've got Fedora 7 and openSUSE 10.2 as LVM volumes (see partitioning below). Fedora boots without a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    May 2007
    Location
    Germany/Netherlands
    Posts
    39

    How to boot the second distro?


    My only drive has a separate primary boot partition with GRUB on sda1. I've got Fedora 7 and openSUSE 10.2 as LVM volumes (see partitioning below).

    Fedora boots without a problem. I can boot SuSE too, but only from the SuSE installation disk. Of course, I want to boot SuSE using GRUB, too.

    QUESTION: how do I configure GRUB for dual boot?

    Below:

    1. partitions
    2. grub.conf on sda1


    1. partitions

    LVM Volume Groups
    . . . susys 29996 MB
    . . . . . srv ext3 4 GB
    . . . . . usr ext3 4 GB
    . . . . . root ext3 21 GB
    . . . fedsys 29996 MB
    . . . . . home ext3 4096 MB
    . . . . . root ext3 17794 MB
    . . . . . usr ext3 4096 MB
    . . . . . var ext3 4096 MB
    . . . debsys 39996 MB
    . . . ubusys 29996 MB

    /dev/sda
    Hard drives
    . . . /dev/sda1 ext3 102 MB /boot
    . . . /dev/sda2 ext3 4095 MB /data
    . . . /dev/sda3 swap 2047 MB swap
    . . . /dev/sda4 Extended 146381 MB
    . . . . . /dev/sda5 debsys LVM PV 39998 MB
    . . . . . /dev/sda6 ubusys LVM PV 29996 MB
    . . . . . /dev/sda7 susys LVM PV 29996 MB
    . . . . . /dev/sda8 fedsys LVM PV 29996 MB
    . . . FREE Free space 16394 MB

    2. 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,0)
    # kernel /vmlinuz-version ro root=/dev/fedsys/root
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.20-2925.11.fc7xen)
    . . . root (hd0,0)
    . . . kernel /xen.gz-2.6.20-2925.11.fc7
    . . . module /vmlinuz-2.6.20-2925.11.fc7xen ro root=/dev/fedsys/root rhgb quiet
    . . . module /initrd-2.6.20-2925.11.fc7xen.img
    title Fedora (2.6.21-1.3228.fc7)
    . . . root (hd0,0)
    . . . kernel /vmlinuz-2.6.21-1.3228.fc7 ro root=/dev/fedsys/root rhgb quiet
    . . . initrd /initrd-2.6.21-1.3228.fc7.img
    title Fedora (2.6.20-2925.9.fc7xen)
    . . . root (hd0,0)
    . . . kernel /xen.gz-2.6.20-2925.9.fc7
    . . . module /vmlinuz-2.6.20-2925.9.fc7xen ro root=/dev/fedsys/root rhgb quiet
    . . . module /initrd-2.6.20-2925.9.fc7xen.img
    title Fedora-base (2.6.21-1.3194.fc7)
    . . . root (hd0,0)
    . . . kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/fedsys/root rhgb quiet
    . . . initrd /initrd-2.6.21-1.3194.fc7.img

  2. #2
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,242
    Boot into your Suse partition, as root do
    Code:
    grub-install /dev/sda7
    then boot into FC, add this to your grub.conf
    Code:
    title Suse
    root (hd0,6)
    chainloader +1
    Then you should be able to select the entry from grub.
    How to know if you are a geek.
    when you respond to "get a life!" with "what's the URL?"
    - Birger

    New users read The FAQ

  3. #3
    Just Joined!
    Join Date
    May 2007
    Location
    Germany/Netherlands
    Posts
    39

    Alas! No boot yet!

    Thank you for your quick reply, budman7

    At first, I did it wrong; instead of booting into my SuSE partition, I did (1) from Terminal inside Fedora:

    (1) grub-install /dev/sda7 (after this, I checked the device.map and the lines were correct).

    (2) Then I added these lines to the grub.conf file:

    title SuSE
    root (hd0,6)
    chainloader +1

    Then when rebooting, I chose the option SuSe. Unfortunately, instead of SuSE, Fedora booted again.

    When this didn't work and I started looking for mistakes, I realized you told me to boot into SuSE first, so that's what I did then.

    As root, I tried: grub-install /dev/sda7
    SuSE replied:
    /dev/sda7: Not found or not a block device.

    Any more suggestions?

    = - = - = - = - = - = - =

    In case this might be of interest, this is what fdisk -l said:

    #fdisk -l

    Disk /dev/sda: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 535 4192965 83 Linux
    /dev/sda3 536 796 2096482+ 82 Linux swap / Solaris
    /dev/sda4 797 19457 149894482+ 5 Extended
    /dev/sda5 797 5895 40957686 8e Linux LVM
    /dev/sda6 5896 9719 30716248+ 8e Linux LVM
    /dev/sda7 9720 13543 30716248+ 8e Linux LVM
    /dev/sda8 13544 17367 30716248+ 8e Linux LVM

    Disk /dev/dm-4: 4294 MB, 4294967296 bytes
    255 heads, 63 sectors/track, 522 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

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

    Disk /dev/dm-5: 4294 MB, 4294967296 bytes
    255 heads, 63 sectors/track, 522 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

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

    Disk /dev/dm-6: 22.7 GB, 22766682112 bytes
    255 heads, 63 sectors/track, 2767 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

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

  4. #4
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    copy first title block ( title, root, kernel and initrd lines ) block from SuSe's menu.lst file and paste in Fedora's grub.conf file.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  5. #5
    Just Joined!
    Join Date
    May 2007
    Location
    Germany/Netherlands
    Posts
    39

    nope

    Nope, I did what you suggested, but when I tried to boot SuSe, this is what the white message on the black screen said:

    Booting 'openSUSE 10.2'

    root (hd0,0)
    Filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz-2.6.18.2-34-default root=/dev/susys/root vga=0x314 resume=/dev/hda2 splash=silent showopts

    Error 15: File not found

    Press any key to continue...

    Any more suggestions?

  6. #6
    Linux User netstrider's Avatar
    Join Date
    Jul 2005
    Location
    South Africa
    Posts
    478
    Try replacing root (hd0,0) with (hd0,6). I would try booting into SuSE, doing grub-install /dev/sda. Then mount your Fedora Partition (if it is not already mounted) or copy it's grub.conf entry from it's own grub.conf and add it to Suse's grub.conf. Save and reboot.

    Good luck

  7. #7
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    try root(hd0,6) as suggested by netstrider.
    are you sure that its roo(hd0,0) in SuSe's menu.lst file? sda1 is Fedora's /boot partition. are you sharing /boot partition in both distros?
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  8. #8
    Just Joined!
    Join Date
    May 2007
    Location
    Germany/Netherlands
    Posts
    39

    Finally

    Finally I've found something that worked.

    1. I copied the first title block from SuSE's menu.lst into F7's grub.conf according to devils_casper's suggestion, so it's still root (hd0,0).

    2. I copied all files from SuSE's previously saved boot directory into F7's boot directory (note: I added all files, but not the grub directory itself, because you want to preserve F7's grub directory, and the original F7 files were also preserved, so it's gotten pretty crowded inside F7's boot directory).

    Now dual booting works.

    Actually, I'd be much more interested in having things arranged as described in Cool Solutions: Install Linux Frequently, Without the Hassle but I didn't get this far yet. Did anyone out there get this done and would you help other interested people to get it done too?

    Thanks for your help and suggestions.

  9. #9
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    that method is a bit complicated imho.
    * install GRUB of first distro in MBR and do not create /boot partition. installer will create /boot folder in root partition. install next distro and install GRUB in boot sector of root partition of new distro.
    boot up first distro and add this code in menu.lst/grub.conf file
    Code:
    title <new_distro>
    roonoverify(hdx,x)
    chainloader +1
    replace x and x with correct disk and partition number respectively.
    thats all ! install as many distros as you want and keep adding chainloading code in menu.lst/grub.conf file of first distro.

    * i dont prefer sharing Home Partition.

    User-specific configuration items are stored in "dotfiles" (filenames starting with '.') in each user's home directory. these files are often not backward compatible between versions of applications.
    let say, both distros have KDE. the preference files in $HOME/.kde/ for KDE 3.4 are probably not compatible with KDE 3.5. this is even more true for Desktop preference files between different Linux distributions.

    i have repeated above lines several times here in LinuxForums.

    you can create a separate partition to share data between distros.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  10. #10
    Just Joined!
    Join Date
    May 2007
    Location
    Germany/Netherlands
    Posts
    39

    Logical problem

    I've tried this before, but it didn't work. If I don't make a boot partition and choose to create an individual boot partition instead, SuSE starts screaming this cannot be done on LVM.

    My partitioning is:
    primary /boot
    primary /swap
    primary /data (for sharing among distro's)
    extended
    LVM Fedora 7
    LVM openSUSE 10.2
    and more LVM distros planned.

    All my distro's are on separate volume groups in the extended partition.

    Since Linux only allows four primary partitions, I wonder how to solve the boot sector problem for each distro if you want to have, say, five distros. If you cannot have a boot sector in the LVM root partition of every distro, what do you do then?

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •