Dualboot Two Hard Drives

[Trinity1976]

I have no file called 'menu.lst' in my grub directory. Does anyone know if things are different in Karmic?

[robbielink]

I have no file called 'menu.lst' in my grub directory. Does anyone know if things are different in Karmic?

I didn't either - and that was why I wasn't able to boot directly into Ubuntu. I had to reinstall grub and then run "update-grub" which then asked me if I wanted to create a menu.lst which then solved my boot problem (after I edited it to accommodate the Dell Utility Partition on my Windows drive.)

[Trinity1976]

I think the new equivalent is grub.cfg. I tried lots of different combinations of master and slave with my drives and couldn't even get Windows to boot up if I selected the drive manually in the Boot menu.

So I've given up on dual-booting and am going to set up a Virtual Box instead. Windows was on a very old 20GB hard-drive anyway, and it's probably best I get rid of it.

[natgab]

I wanted to add my set-up to the information in this tutorial, and thank Confused57 for making this tutorial.

I was able to use the information here in this thread to make a dual boot set-up of Ubuntu Studio 9.04 and Haiku.

I will describe my HD set-up:

Master SATA 160GB HD / SDc / ubuntu / start-up

Master SATA 80GB HD / SDb / blank / non-formated

Slave IDE 10GB HD / SDa / haiku / 2nd system

Please note that Ubuntu 9.10 and later use GRUB-2 and this is only for Ubuntu 9.04 or older.

Below is my GRUB list.

Notes for GRUB errors:

Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.28-17-generic
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/vmlinuz-2.6.28-3-rt
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

__________________________________

# 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         3

## 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=fad67457-b54e-46e4-8540-613cce54dcdc ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=fad67457-b54e-46e4-8540-613cce54dcdc

## 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-17-generic
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-17-generic root=UUID=fad67457-b54e-46e4-8540-6$
initrd          /boot/initrd.img-2.6.28-17-generic
quiet

title           Ubuntu 9.04, kernel 2.6.28-17-generic (recovery mode)
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-17-generic root=UUID=fad67457-b54e-46e4-8540-6$
initrd          /boot/initrd.img-2.6.28-17-generic

title           Ubuntu 9.04, kernel 2.6.28-11-generic
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-11-generic root=UUID=fad67457-b54e-46e4-8540-6$
initrd          /boot/initrd.img-2.6.28-11-generic
quiet

title           Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-11-generic root=UUID=fad67457-b54e-46e4-8540-6$
initrd          /boot/initrd.img-2.6.28-11-generic

title           Ubuntu 9.04, kernel 2.6.28-3-rt
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-3-rt root=UUID=fad67457-b54e-46e4-8540-613cce5$
initrd          /boot/initrd.img-2.6.28-3-rt
quiet

title           Ubuntu 9.04, kernel 2.6.28-3-rt (recovery mode)
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/vmlinuz-2.6.28-3-rt root=UUID=fad67457-b54e-46e4-8540-613cce5$
initrd          /boot/initrd.img-2.6.28-3-rt

title           Ubuntu 9.04, memtest86+
uuid            fad67457-b54e-46e4-8540-613cce54dcdc
kernel          /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

title           Haiku OS
rootnoverify    (hd2,0)
chainloader     +1

Also if this is helpful, here is the info from fdisk:

Disk /dev/sda: 10.2 GB, 10242957312 bytes
255 heads, 63 sectors/track, 1245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0006bce6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        1245    10000431   83  Linux

Disk /dev/sdb: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System

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

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       18716   150336238+  83  Linux
/dev/sdc2           18717       19457     5952082+   5  Extended
/dev/sdc5           18717       19457     5952051   82  Linux swap / Solaris

Hopefully this will help someone and also encourage more linux users to also test Haiku.

[trickpat]

HI. this post has been really helpful so thanks. i've had problems doing this before, and i managed to get it working once so i'm fairly confident i can do it again... but something isn't quite working right.. so i could really use some help. Thanks in advance for any tips

Right now, i've got windows 7 installed on a slave 500 Gig IDE drive and ubuntu 9.10 freshly installed on a 250 Gig Sata drive. I installed them both seperately with only one hard drive connected at a time. when i boot with both hard drives connected it's not giving me the option to boot either, it just automatically boots into ubuntu. which is great because it means i can just go into terminal and change the boot bios right? so here's my drive configureation when i type :

sudo fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x283f283e

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30027 241191846 83 Linux
/dev/sda2 30028 30401 3004155 5 Extended
/dev/sda5 30028 30401 3004123+ 82 Linux swap / Solaris

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
16 heads, 63 sectors/track, 969021 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x48cb4d3f

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 969018 488385040+ 7 HPFS/NTFS
patrick@patrick-desktop:~$


So i think i just need to tweek the line that i put in the edited menu.lst
gksudo gedit /boot/grub/menu.lst
title Windows XP Professional
root (hd1,0)
savedefault
makeactive
chainloader +1
map (hd0) (hd1)
map (hd1) (hd0)


replace windows xp professional with Windows 7

and change the Hd0 HD 1 Lines but.. i cant figure what i need to change. any tips? or anything else i need to change? i tried putting it in unchanged just the way i pasted it there and i thought it would work.. but it didn't seem to do anything. I used to have XP and ubuntu running like this on 2 hard drives and it worked great so i hope i can figure this out. Thanks for your time!

[ssican]

TIP

-BOOTING XP ON A NON-FIRST HARD DRIVE-

SOURCE:
KubuntuForums.net
GRUB 2 A Guide for Users
AUTHOR: Qqmike

http://kubuntuforums.net/forums/inde...opic=3106368.0

On Reply #1 -POST 2-
http://kubuntuforums.net/forums/inde...5829#msg195829

Qqmike Recommend:
- Run First: grub install
sudo grub-install
before running
sudo grub-mkconfig -o /boot/grub/grub.cfg


(Qqmike wrote:
grub-mkconfig Detecting other OSs
grub-mkconfig automatically runs os-prober to detect other OSs on your PC (assuming os-prober is installed, which it will be in any normal installation).

grub-mkconfig: Is grub.cfg in sync with core.img?
=> Run first: grub-install
To be sure you get the best and the correct grub.cfg file, especially if there's been a change/update to core.img, it would be safe to run
sudo grub-install
before running
sudo grub-mkconfig -o /boot/grub/grub.cfg


XP on a non-first hard drive: (hdx,y), x > 1
Qqmike recommend:
See the following section titled "Booting XP on a non-first hard drive: The drivemap command in GRUB 2."

=> => Fact is, you might be able to use the GRUB 2 utility grub-mkconfig or grub-install to do this work for you: they might detect Windows properly and adjust for Windows being on a non-first HD (by implementing the drivemap commands automatically). (For the commands grub-mkconfig and grub-install, see Notes about some of the new GRUB 2 commands (in Reply #1 above); also see SECTION 3: Fixing Things)


Booting XP on a non-first hard drive The drivemap command in GRUB 2
Qqmike wrote: "I will present you with safe options that will not harm your GRUB 2 or dual-booting setup.

For a more compact Method 2 and for technical notes and other useful details about how drivemap works, see Reply #17. (Later, Reply # 17 may be incorporated here.)

The Quick-and-Dirty Solution

Method 1
To boot Windows XP installed to (hd1,1), use the following menuentry (in a script you write as a text file (and make executable) in the folder /etc/grub.d):

# Method 1 -- a safe, sure way to do it
# This method applies to Windows and to FreeDOS
# Windows XP on sdb1 (= (hd1,1)
menuentry “Windows XP on sdb1, by chainloader” {
drivemap (hd0) (hd1)
drivemap (hd1) (hd0)
set root=(hd0)
chainloader (hd1,1)+1 }


=> The drivemap command in GRUB 2 replaces the map command in GRUB Legacy.
=> That's all you need to know to make your grub.cfg work.

=> => Fact is, you might be able to use the GRUB 2 utility grub-mkconfig or grub-install to do this work for you: they might detect Windows properly and adjust for Windows being on a non-first HD (by implementing the drivemap commands automatically). (For the commands grub-mkconfig and grub-install, see Notes about some of the new GRUB 2 commands (in Reply #1 above); also see SECTION 3: Fixing Things"

EDIT 1
USING -sudo grub-install- Herman recommend to specify the Disk you wish to Install Grub:

sudo grub-install /dev/sda

Where: /dev/sda is the disk you wish to install GRUB to, (boot.img to first hard disk MBR), otherwise use '/dev/sdb' for second hard disk or '/dev/sdc' for third hard disk
How to Install, update and repair GRUB:
http://members.iinet.net/~herman546/...ate_and_repair

[betterspud]

Ok. I am a complete noob with linux systems and have no real clue what I'm doing.

Have read through many posts about changing Grub and am having no luck.

Whenever I try to save an edited version of grub.cfg I get a 'could not save the file' error because it is read only and I do not have permission. I thought that using sudo would allow me to save it?

What am I doing wrong?

EDIT: Just discovered that on 9.10, it uses Grub2.0 and that you CANNOT edit grub.cfg, but have to change the default within /etc/default/grub instead.

Have just installed startup manager from the package list and am configured through that. Hopefully, it will do the job...

[eljefe]

I havent had any luck here with my dual HD booting, as per this tutorial:
http://ubuntu-georgia.org/installing...ves#References

I got the required details into the grub menu and it all comes up great, the only problem is that when I hit the "Windows" option it says:

Error 21: Selected disc does not exist
Press any key to continue.....

When I do this Mint 7 loads as expected.

I have the HD1 cable plugged into the Linux HD and the HD2 cable plugged into the XP HD. The XP install was acatually done on this box, so I know it goes.

Normally in this machine HD1 cable goes to the XP HD, and the Mint HD is not there at all.

Both HDs were set with cable select positions for the jumpers, which is how the XP drive was installed too.

I then dicked about with the Jumpers.

Cable select for both HD's (Error 21)
Mint on cable select, Windows on slave (Error 21)
Mint on master, window on slave (No grub menu, just Error 21)

Has anyone got any clues on how to trouble shoot from here?

My bios says:

SATA Primary drive    OFF
SATA Seconday drive         OFF
Primary Master drive        HARD DRIVE
Primary Slave drive         OFF
Secondary master drive      cdrom device
Secondsary slave drive      OFF 

IDE drive  UDMA             ON

This is for my daughter. I want her to keep using Linux but want to have the windows boot as a last resort.

[confused57]

Hi eljefe,

You might see if there is an option in your bios to turn on your primary slave controller:

SATA Primary drive    OFF
SATA Seconday drive         OFF
Primary Master drive        HARD DRIVE
Primary Slave drive         OFF
Secondary master drive      cdrom device
Secondsary slave drive      OFF

I had a Dimension 4550, which would show grub error 21 if the primary slave controller was set to off...had to set it to "auto" to get Windows to boot properly.

Here's an excellent explanation of error 21 & possible causes:
http://members.iinet.net.au/~herman546/p15.html#21