Logo 
Search:

Unix / Linux / Ubuntu Forum

Ask Question   UnAnswered
Home » Forum » Unix / Linux / Ubuntu       RSS Feeds

Ubuntu 8.04 - dualboot on two hard drives

  Date: Dec 20    Category: Unix / Linux / Ubuntu    Views: 359
  

I've read a post on this on another forum and somehow it doesn't seem
to work for me... ubuntu 8.04 seems quite clever. It finds the
winblows drive and puts the necessary code at the bottom of the
menu.lst file. I'd rather use dualboot with two drives as it is then
easier for installing new ubuntu releases (IMHO).

hard drives both standard IDE on a 2.6ghz desktop.
master drive - ubuntu 8.04
slave drive - win2k (no reason other than i don't have a copy of XP...
my only reason for wanting to do dualbooting is that i've got several
apps and a scanner than i can't run on ubuntu)

Following the beginning of the guide that worked fine - installing
win2k on master and then connecting the master for ubuntu carefully
switching the win2k disk to slave.

I want ubuntu to load as default. I read through the forum listed
menu.lst carefully taking note of what was said about needing to put
the ammendments at the bottom of the file. In 8.04 at the foot of
menu.lst IT IS ALREADY THERE - no editing required.

It would seem that 8.04 DOES the necessary!

On rebooting i selected the bottom item i.e windows and it didn't seem to load.

windows message
"Windows 2000 could not start because of a computer disk hardware
configuration problem. Could not read from the selected boot disk.
Check boot path and disk hardware"

I don't think this message can be relevant to the problem as i
installed win2k fine?
I'd be very grateful if you put put me right! Menu.lst below 8.04
original no ammendments.

# menu.lst - See: grub(, info grub, update-grub(
# grub-install(, grub-floppy(,
# 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 10

## 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=4a8cf581-73c8-41dc-a4d0-2bee78c3e5fc ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

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

## 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 8.04.1, kernel 2.6.24-19-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-19-generic
root=UUID=4a8cf581-73c8-41dc-a4d0-2bee78c3e5fc ro quiet splash
initrd /boot/initrd.img-2.6.24-19-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-19-generic
root=UUID=4a8cf581-73c8-41dc-a4d0-2bee78c3e5fc ro single
initrd /boot/initrd.img-2.6.24-19-generic

title Ubuntu 8.04.1, kernel 2.6.24-16-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=4a8cf581-73c8-41dc-a4d0-2bee78c3e5fc ro quiet splash
initrd /boot/initrd.img-2.6.24-16-generic
quiet

title Ubuntu 8.04.1, kernel 2.6.24-16-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=4a8cf581-73c8-41dc-a4d0-2bee78c3e5fc ro single
initrd /boot/initrd.img-2.6.24-16-generic

title Ubuntu 8.04.1, memtest86+
root (hd0,0)
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/sdb1
title Windows NT/2000/XP (loader)
root (hd1,0)
savedefault
makeactive
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1

Share: 

 

4 Answers Found

 
Answer #1    Answered On: Dec 20    

Here is the layout of my Linux partitions and Windows partition from
the output of the fdisk -l command (as root in Linux):
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x60276028

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 9728 78140128+ 7 HPFS/NTFS

Disk /dev/sdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5fd95fd9

Device Boot Start End Blocks Id System
/dev/sdd1 * 1 13 104391 83 Linux
/dev/sdd2 14 9538 76509562+ 83 Linux
/dev/sdd3 9539 9729 1534207+ 82 Linux swap /
Solaris


Here are the contents of my menu.lst file to give you and idea of how
it was setup for dual booting on two separate disks. Note: the Linux
distro, Fedora Core 3 (FC3) is the default=0. Change it to default=1
if you want Windows to boot; and the timeout=15 means there are 15
seconds to decide which OS to boot:
# 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/sdb2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=15
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.10-1.770_FC3smp)
root (hd1,0)
kernel /vmlinuz-2.6.10-1.770_FC3smp ro root=/dev/sdb2 rhgb quiet
initrd /initrd-2.6.10-1.770_FC3smp.img
#title Fedora Core (2.6.10-1.770_FC3)
# root (hd1,0)
# kernel /vmlinuz-2.6.10-1.770_FC3 ro root=/dev/sdb2 rhgb quiet
# initrd /initrd-2.6.10-1.770_FC3.img
#title Fedora Core (2.6.9-1.667smp)
# root (hd1,0)
# kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/sdb2 rhgb quiet
# initrd /initrd-2.6.9-1.667smp.img
#title Fedora Core-up (2.6.9-1.667)
# root (hd1,0)
# kernel /vmlinuz-2.6.9-1.667 ro root=/dev/sdb2 rhgb quiet
# initrd /initrd-2.6.9-1.667.img
title WindowsXP
rootnoverify (hd0,0)
chainloader +1

You will need to modify your setup with your own system's data for
device names, files, etc. to implement this scheme, and check all of
the details to insure that none of my data is referenced - i.e. use
only your data.

 
Answer #2    Answered On: Dec 20    

I think the problem is that you changed the Windows drive. My computer
is set up with Windows on the primary drive and Ubuntu on the secondary
drive. You need to change the boot order in grub to change the default
system.

 
Answer #3    Answered On: Dec 20    

I have 8.04 installed on a USB hard drive that I dual boot on my system.

I select the boot drive at boot time through the bios, as my wife is a
Windoze user only and doesn't want any hassle at boot time.

When I installed 8.04, I did a manual install from the menu.

I had it put the install and GRUB on the second drive. (It saw it as
just another drive.)

I had to edit GRUB to get 8.04 to boot properly.

When you install it like that, GRUB sees the second drive as Drive 1.
But when you boot from the second drive, GRUB sees it as Drive 0. So
I had to change the entry to boot from 0,0 rather than 1,0.

This way Linux gets too boot from its own loader and Windows gets to
boot from its own also.

 
Answer #4    Answered On: Dec 20    

I did manage to solve the problem - win2k
works slightly differently from winXP. After posting this thread i
found (hidden in some manuals) in the box that came with this PC the
recovery disks having all drivers etc. Once i had installed XP and
switched the cables back it worked fine. For me to use win2k i needed
to modify the boot.ini and i would have also had the pain of finding
the necessary drivers... so as i had XP it was better to install that.

This method of dualboot is excellent as it allows one to do an
independent install of either operating system. In my case ubuntu for
95% use and just switching occasionally to windows for a couple of
apps and using the scanner that came with it. I still find that i have
some DVDs that won't play on ubuntu and yet play on windows media
player (a wimbledon finals which i loved watching!).

The other advantage of this dualboot method (imo) is that ubuntu 6
month releases are easy to accommodate. One can change the file to
allow winXP to boot first if that is desired.

 
Didn't find what you were looking for? Find more on Ubuntu 8.04 - dualboot on two hard drives Or get search suggestion and latest updates.




Tagged: