Quad boot with 2 ide hard drives - help needed


Page 1 of 2 12 LastLast
Results 1 to 15 of 20

Thread: Quad boot with 2 ide hard drives - help needed

  1. #1
    Join Date
    Apr 2003
    Posts
    220

    Quad boot with 2 ide hard drives - help needed

    Firstly, there is probably a better way to do this than the way I am attempting. However, this is where I am right now.

    One hard drive (I'll call it hard drive 1 for the sake of this post) has windows xp and ubuntu on it. It dual boots fine and Grub is installed in the MBR.

    I physically removed that hard drive and installed a higher capacity hard drive (I'll call it hard drive 2). This hard drive (hard drive 2) is a dual boot (win xp and linux mint) and Grub is installed in the MBR. It works fine.

    Here's what I want to do:

    1. Make hard drive 1 the master drive, and hard drive 2 the slave drive. I know how to do this (hd pin settings, master drive on the end of the ide chain, etc).

    2. Have a grub menu that allows me to boot any of the OS's from any of the hard drives. As such this grub menu should have 4 entries.

    What I think I need to do is add two entries to hard drive one's Grub; 1 for window xp (on the slave drive) and one for linux mint (also on the slave drive). How do I do that?

    However, I wonder if there is a way to tell hard drive 1's grub to link to the grub on hard drive two - i.e. to make an entry show up that when selected would show hard drive 2's grub menu options. Is this possible?

    Thanks in advance for your help.

    Edit: The system is using grub1.
    Last edited by Chess007; 07-24-2011 at 12:41 AM.
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  2. #2
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    Yes. All your wishes will be granted.

    What version of Grub are you using? (Edited I now see you confirm it is Grub1 but I supply commands for Grub2 also just in case)

    My suggestion is to hook up the two hdd exactly as you are intended and

    (1) Add one entry to the Grub in hdd1 for booting to hdd2. In so doing you swap the disk order on the fly and boot up hdd2.

    (2) I assume your Xp in hdd2 works only if hdd1 is absent so effectively it was installed as the 1st disk.

    For Grub1, versions 0.9x, the Grub entry is simple.
    Code:
    title Justlinux dude suggestion to boot hdd2 on the fly
    root (hd1)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    For Grub2, versions 1.9x, the Grub entry is simple.
    Code:
    menuentry 'Justlinux dude suggestion to boot hdd2 on the fly'{
    root (hd1)
    drivemap (hd0) (hd1)
    drivemap (hd1) (hd0)
    chainloader +1
    }
    The idea is in booting up the specified second hard disk (hd1) the "map" or "drivemap" commands will swap the address of (hd0) with (hd1) in the memory temporarily. Nothing is changed to the Bios and on a reboot the disk order reverts back to the hardware setting. It is a lot easier to control the quad boot with one Grub. If you want the harder way please let us know.

    Having booted to the hdd2 and you want to go back to hdd1 (only possible before activating a OS to boot) you can add the same entry to the menu.lst of the Grub1 controlling the hdd2. The only change needed is to change the "root" statement
    Code:
    root (hd0)
    This should allow you jump freely between the two disks.
    Last edited by saikee; 07-24-2011 at 04:52 AM.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  3. #3
    Join Date
    Apr 2003
    Posts
    220
    Thanks. I have 2 more questions. Is it okay to add

    Code:
    title Justlinux dude suggestion to boot hdd2 on the fly
    root (hd1)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    before I hook in the second hard drive (the slave drive)?

    Here is my current menu.lst file:

    Code:
    # menu.lst - See: grub(8), info grub, update-grub(8)
    #            grub-install(8), grub-floppy(8),
    #            grub-md5-crypt, /usr/share/doc/grub
    #            and /usr/share/doc/grub-doc/.
    
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default		0
    
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout		60
    
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu
    
    # Pretty colours
    #color cyan/blue white/blue
    
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line)  and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    #      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    
    #
    # examples
    #
    # title		Windows 95/98/NT/2000
    # root		(hd0,0)
    # makeactive
    # chainloader	+1
    #
    # title		Linux
    # root		(hd0,1)
    # kernel	/vmlinuz root=/dev/hda2 ro
    #
    
    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ##      kopt_2_6_8=root=/dev/hdc1 ro
    ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ##      alternative=false
    # alternative=true
    
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ##      lockalternative=false
    # lockalternative=false
    
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ##      lockold=true
    # lockold=false
    
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ##      altoptions=(recovery) single
    # altoptions=(recovery mode) single
    
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ##      howmany=7
    # howmany=all
    
    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ##      indomU=true
    ##      indomU=false
    # indomU=detect
    
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ##      memtest86=false
    # memtest86=true
    
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    
    ## ## End Default Options ##
    
    title		Ubuntu 9.04, kernel 2.6.28-19-generic
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-19-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro quiet splash 
    initrd		/boot/initrd.img-2.6.28-19-generic
    quiet
    
    title		Ubuntu 9.04, kernel 2.6.28-19-generic (recovery mode)
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-19-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro  single
    initrd		/boot/initrd.img-2.6.28-19-generic
    
    title		Ubuntu 9.04, kernel 2.6.28-11-generic
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro quiet splash 
    initrd		/boot/initrd.img-2.6.28-11-generic
    quiet
    
    title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro  single
    initrd		/boot/initrd.img-2.6.28-11-generic
    
    title		Ubuntu 9.04, memtest86+
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title		Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Microsoft Windows XP Professional
    rootnoverify	(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    Should I add the new code so that the last section of the file looks like this:

    Code:
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Microsoft Windows XP Professional
    rootnoverify	(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    
    title Justlinux dude suggestion to boot hdd2 on the fly
    root (hd1)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    Just want to be sure I put the new entry in the correct place in the file. Thanks again for your help.
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  4. #4
    Join Date
    Jul 2003
    Location
    Spokane, Washington
    Posts
    580
    Wherever you place the block to chainload to the second drive (within the list of 'title' blocks) will determine the position of the entry at boot time. It is perfectly fine to place it at the bottom like that, the choice to switch to the second drive will be at the bottom of the list on boot. If you want the choice higher, just move that whole block higher in the list in the configuration file. All title blocks should be after the header configuration items (color scheme, background image, ...)

  5. #5
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    I second Pafnoutios reply.

    With Grub you can put in the entries before the installing the system or the hard disk. It just wouldn't boot. That is all but no damage is done.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  6. #6
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    Chess007,

    Did you managed to get the two hard disks working as we advised?

    Today I had the same thing. Been running a single 2TB hard disk for a few years and it has about 45 operating systems inside all installed as sda.

    This evening I add a 128Gb SSD hard disk and installed a Ubuntu on it as sda (by temporary removing the 2TB disk). On completion I put the 2TB back and the Bios picks it up as sdb.

    Therefore I did exactly as this thread and can boot to either disk using each as the 1st disk by Grub2.

    Grub2 is slightly different to Grub1 but using the same sort of commands. Here is the part of my Grub2 configuration doing the switching
    Code:
    menuentry 'Booting the second harddisk' {
    	set root='(hd1)'
    	drivemap (hd0) (hd1)
    	drivemap (hd1) (hd0)
    	chainloader +1
    }
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  7. #7
    Join Date
    Apr 2003
    Posts
    220

    Ide pin hell... :)

    No. I haven't got it to work yet. Here's what happened so far. I have been trying various pin settings but even when the bios recognizes both drives, and Grub does boot, when I select the

    "title Justlinux dude suggestion to boot hdd2 on the fly"

    option I get the following text:

    "Starting up.
    Grub loading, please wait"

    then the screen goes black and my original grub menu (the grub menu on the master hd that has xp and Ubuntu on it) is there again.

    My thoughts are:

    a) that perhaps the pin settings are still wrong
    What should the pin settings be?
    The main drive (the one I want to be master) has "cable select" and "master without a slave" pin options.
    b) perhaps Ubuntu 9 does use grub 2 ?

    I read that some ide cables can automatically assign master and slave status to hard drives so I remove the pins (jumpers) from both hard drives and put them in the correct positions on the ide cable; that resulted in the bios not seeing any hard drives.

    Still trying to figure this out.

    P.s. Ubuntu and the Windows xp on the ubuntu hard drive both still boot fine.

    Here is my current grub menu.lst file:

    Code:
    # menu.lst - See: grub(8), info grub, update-grub(8)
    #            grub-install(8), grub-floppy(8),
    #            grub-md5-crypt, /usr/share/doc/grub
    #            and /usr/share/doc/grub-doc/.
    
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default		0
    
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout		60
    
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu
    
    # Pretty colours
    #color cyan/blue white/blue
    
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line)  and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    #      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    
    #
    # examples
    #
    # title		Windows 95/98/NT/2000
    # root		(hd0,0)
    # makeactive
    # chainloader	+1
    #
    # title		Linux
    # root		(hd0,1)
    # kernel	/vmlinuz root=/dev/hda2 ro
    #
    
    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ##      kopt_2_6_8=root=/dev/hdc1 ro
    ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ##      alternative=false
    # alternative=true
    
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ##      lockalternative=false
    # lockalternative=false
    
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ##      lockold=true
    # lockold=false
    
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ##      altoptions=(recovery) single
    # altoptions=(recovery mode) single
    
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ##      howmany=7
    # howmany=all
    
    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ##      indomU=true
    ##      indomU=false
    # indomU=detect
    
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ##      memtest86=false
    # memtest86=true
    
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    
    ## ## End Default Options ##
    
    title		Ubuntu 9.04, kernel 2.6.28-19-generic
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-19-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro quiet splash 
    initrd		/boot/initrd.img-2.6.28-19-generic
    quiet
    
    title		Ubuntu 9.04, kernel 2.6.28-19-generic (recovery mode)
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-19-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro  single
    initrd		/boot/initrd.img-2.6.28-19-generic
    
    title		Ubuntu 9.04, kernel 2.6.28-11-generic
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro quiet splash 
    initrd		/boot/initrd.img-2.6.28-11-generic
    quiet
    
    title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=b6eb6801-352a-4cf6-b7eb-4bbeb752783a ro  single
    initrd		/boot/initrd.img-2.6.28-11-generic
    
    title		Ubuntu 9.04, memtest86+
    uuid		b6eb6801-352a-4cf6-b7eb-4bbeb752783a
    kernel		/boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title		Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Microsoft Windows XP Professional
    rootnoverify	(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    
    
    title Justlinux dude Saikee suggestion to boot hdd2 
    root (hd1)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    Suggestions?
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  8. #8
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    For IDE or ATA hatd disks the best pin setting I could suggest is Cable Select. One you put both disks on cable select then the one plug to the middle is the Slave and the disk attached to the end plug is the Master.

    For years I have set all my IDE hard disks to cable select. The one attached to the end of the cable is always the master. If I want it to become a slave I swap it with the middle plug. Thus all of my IDE hard disks were set once only and never touched again.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  9. #9
    Join Date
    Apr 2003
    Posts
    220

    The mystery continues...

    Thanks for that cable select tip. Now the BIOS recognizes both hard drives and everything almost works right.

    Upon boot there are no error beeps and Grub (from my ubuntu/xp hd) starts. When I select the "justlinux dude suggestion" option, I get the following text:

    "Starting up.
    Grub loading, please wait"

    then the screen goes black, and Windows XP (from the slave hd - i.e. xp and mint) loads. This is good, it means the slave hd is being used to boot an OS. However, there is never the option to boot Linux Mint. I have a few ideas as to why...

    a) The time out on the slave hd's Grub is about 5 seconds, so maybe by the time grub gets ready to boot, it auto boots XP (xp is at the top of the list on that menu).

    b) I'm using either linux mint 10 or linux mint 11 (on the slave drive). Linux Mint 8 and above uses Grub 2 which is not the same as the version of Grub which is used on the master drive. See the following link for more info:

    http://forums.linuxmint.com/viewtopi...=37187&start=0

    On Ubuntu I can open the file "/boot/grub/grub.cfg" (which is on the mint linux slave drive) but it is read only. Additionally, I have no clue what value to change to make the menu display for say 60 seconds (which seems reasonable).

    Here's the code:

    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #

    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi

    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    }

    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    }

    function load_video {
    insmod vbe
    insmod vga
    }

    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    load_video
    insmod gfxterm
    fi
    terminal_output gfxterm
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    set locale_dir=($root)/boot/grub/locale
    set lang=en
    insmod gettext
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###

    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###

    ### BEGIN /etc/grub.d/06_mint_theme ###
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    insmod png
    if background_image /boot/grub/linuxmint.png ; then
    set color_normal=white/black
    set color_highlight=white/light-gray
    else
    set menu_color_normal=white/black
    set menu_color_highlight=white/light-gray
    fi
    ### END /etc/grub.d/06_mint_theme ###

    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Linux Mint 10, 2.6.35-22-generic (/dev/sda6)' --class linuxmint --class gnu-linux --class gnu --class os {
    recordfail
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    linux /boot/vmlinuz-2.6.35-22-generic root=/dev/sda6 ro quiet splash
    initrd /boot/initrd.img-2.6.35-22-generic
    }
    menuentry 'Linux Mint 10, 2.6.35-22-generic (/dev/sda6) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {
    recordfail
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    echo 'Loading Linux 2.6.35-22-generic ...'
    linux /boot/vmlinuz-2.6.35-22-generic root=/dev/sda6 ro single
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-2.6.35-22-generic
    }
    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/10_lupin ###
    ### END /etc/grub.d/10_lupin ###

    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###

    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    linux16 /boot/memtest86+.bin
    }
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos6)'
    search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
    linux16 /boot/memtest86+.bin console=ttyS0,115200n8
    }
    ### END /etc/grub.d/20_memtest86+ ###

    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
    insmod part_msdos
    insmod fat
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set 0755-1e03
    drivemap -s (hd0) ${root}
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###

    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    Any thoughts? Thanks for your help!
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  10. #10
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    You can edit any read only file in a Linux as a root user.

    For Ubuntu family no root user account is permitted but prefixed the editing command with "sudo" should give you the temporary root privilege. For example in a terminal
    Code:
    sudo gedit /boot/grub/grub.cfg
    or
    Code:
    sudo nano /boot/grub/grub.cfg
    You have to supply the password for the ordinary user when such a command is first issued.
    Last edited by saikee; 08-07-2011 at 06:39 AM.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  11. #11
    Join Date
    Apr 2003
    Posts
    220
    Thanks What should I edit to make the menu display time longer (for the Grub 2 on the slave hd).
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  12. #12
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    Code:
    set timeout=1000
    or
    Code:
    #set timeout=10
    The red bits are the additions or alterations.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  13. #13
    Join Date
    Apr 2003
    Posts
    220

    Status Update

    Still only a triple boot. Been messing with this a little bit. Here's the status so far:

    Grub (version 1) on the master hd will boot either Ubuntu or windows xp (that is on the master hd). However, selecting the "justlinux dude" option, simply displays

    "Starting up.
    Grub loading, please wait"

    the screen flashes black and I am back to the grub menu that is on the master hd. However, there is one key difference: when I select the Windows XP option, the version of win xp that is on the slave drive loads. (Not sure why that works considering the grub menus looks exactly like the menu that is on hd0 (the master hd).

    But I can live with that quirk. I just need to figure out how to add an entry to Ubuntu/windows xp's grub so that Linux Mint will boot. Linux mint lives in (hd1,1) i.e. the second partition of slave hard drive. It is on an ext3 filesystem.

    Suggestions? (As captain Picard frequently asked his warroom).
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

  14. #14
    Join Date
    Jun 2004
    Location
    Newcastle upon Tyne
    Posts
    2,983
    I have looked deeper into the swapping of disk order and now believe there is a severe limitation.

    When you boot up Grub the MBR of say disk1 and instruct the disk order to be swapped with disk2 and then chainload to a second boot loader. That will work as long as a second boot loader does not chainload a third boot loader.

    If the second boot loader chainloads a third boot loader the last one will load the OS from scratch and start the hard disk detection again. In so doing it will revert back the original hardware disk order.

    In conclusion if you use Grub from disk1 to jump onto disk2 Grub can boot the systems in the disk2 directly but unable to chainload any of the Linux. MS Systems are slightly different though.
    Last edited by saikee; 08-14-2011 at 12:37 PM.
    Linux user started Jun 2004 - No. 361921
    Using a Linux live CD to clone XP
    To install Linux and keep Windows MBR untouched
    Adding extra Linux & Doing it in a lazy way
    A Grub menu booting 100+ systems & A "Howto" to install and boot 145 systems
    Just cloning tips Just booting tips A collection of booting tips

    Judge asked Linux "You are being charged murdering Windoze by stabbing its heart with a weapon, what was it?" Replied Linux "A Live CD"

  15. #15
    Join Date
    Apr 2003
    Posts
    220

    Hmmm...

    In conclusion if you use Grub from disk1 to jump onto disk2 Grub can boot the systems in the disk2 directly but unable to chainload any of the Linux. MS Systems are slightly different though.
    I see. Hmmm. So, it's not possible? Considering you are the master of the Grub if you say it's not possible, it's not possible. Meatloaf says "Two outta 3 aint bad" so 3 out of 4 is okay.

    One Last Idea!

    What about a grub boot disk? Way back when I tried my first dual boot (circa 2000, 2001) I remember installing the red hat boot loader to a floppy disk. Windows worked fine. There was no grub on the hd. But when I put that disk in, Grub loaded from it and there was my Red Hat.

    The question becomes would a Grub boot disk be able to load Mint even though its on the slave drive? The Grub on the hd shouldn't load at all because the cd drive boots before the hard drive. Thanks again for all your help.
    Currently running Xubuntu & Blag.

    My blog:
    http://truthjournal.blogspot.com

    The Easy Guide to Installing debian:
    http://www.osnews.com/story.php?news_id=2016

Posting Permissions

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