MandrivaUsers.org > Boot winblows from secondary drive [solved]

Full Version: Boot winblows from secondary drive [solved]

MandrivaUsers.org > General Help > Hardware

{BBI}Nexus{BBI}

Aug 15 2008, 03:31 PM

I hope you guys will forgive my laziness, I've had a verrrrry long studio recording session and now I'm fit to drop. I've done a quick search to see what hits I get, but nothing showed up to give me the quick fix I require.

Anyway can someone please take a look at this and tell me changes I need to make to get winblows (installed on a secondary sata hard drive) to boot via the grub menu. It just keeps going to the primary drive.

CODE

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,1)/usr/share/gfxboot/themes/pclinuxos/boot/message
default 1

title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/hdc2 acpi=on splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title Games < This is the sata drive.
root (hd1,0)
makeactive
chainloader +1

Thanks for any responses. I'm off to get my head down. ZZZZzzzzz

ianw1974

Aug 16 2008, 06:57 PM

Can you provide an:

CODE

fdisk -l

so that we can see which partitions are available on each disk.

Reiver_Fluffi

Aug 16 2008, 11:11 PM

Try this:

CODE

title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1

Source: http://fedorajim.googlepages.com/dualbootl...6xpthesafeway...

scarecrow

Aug 17 2008, 01:47 PM

Like Reiver Fluffi suggested. If it does not work, add a line
makeactive
right after the rootnoverify one.

Lexicon

Aug 17 2008, 02:25 PM

Always necessary tiny partition FAT (NTSC) on first disc is .....Lex

{BBI}Nexus{BBI}

Aug 17 2008, 03:21 PM

Thanks for the suggestions.

@ian1974 I will post the output of fdisk -l if none of the above works. Thanks again guys

{BBI}Nexus{BBI}

Aug 17 2008, 08:51 PM

Partial success. The secondary (sata) drive does boot using Reiver Fluffi's listing but I am no longer able to boot the winblows installation on the primary drive. I know it there is something that needs amending in the menu.lst and I have tried a few combinations. I get error parsing number each time. I am posting the output of fdisk -l in the hope someone can post what I need to have in the menu.lst for this to work.

CODE

fdisk -l

Disk /dev/hdc: 123.5 GB, 123522416640 bytes
255 heads, 63 sectors/track, 15017 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1       11047    88734996    7  HPFS/NTFS
/dev/hdc2           11048       14851    30555630   83  Linux
/dev/hdc3           14852       15017     1333395    5  Extended
/dev/hdc5           14852       15017     1333363+  82  Linux swap / Solaris

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

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       30400   244187968+   7  HPFS/NTFS

Just to recap, I have PCLinuxOS & Winblows on the primary drive, with Winblows also installed on the Secondary sata drive.

Greg2

Aug 17 2008, 11:38 PM

QUOTE ({BBI}Nexus{BBI} @ Aug 17 2008, 04:51 PM)

CODE

fdisk -l

Disk /dev/hdc: 123.5 GB, 123522416640 bytes
-snip-

What happened to hda and hdb? Where are they?

{BBI}Nexus{BBI}

Aug 18 2008, 12:12 AM

QUOTE (Greg2 @ Aug 18 2008, 12:38 AM)

What happened to hda and hdb? Where are they?

They have been assigned to the two dvd drives. To cut a long story short the system is setup as follows:

2 dvd drives connected to the ide on the motherboard

1 pata (primary drive) connected to a ide/raid card (hdc)

1 sata (secondary drive) connected to the motherboard (sda)

Nope this is not my system, and please don't suggest I switch things around.

ianw1974

Aug 18 2008, 06:22 AM

OK, well you'll need to add another Windows boot entry to the grub.conf/menu.lst so that you can boot the one from the primary drive. However, I need to see the fdisk output for this hard disk to be sure of the partition order, but it will be similar to:

CODE

title windows
rootnoverify (hd0,0)
makeactive
chainloader +1

of course, I'm unsure of the hd0,0 bit without seeing the partition table from the fdisk as before.

{BBI}Nexus{BBI}

Aug 18 2008, 09:31 PM

As requested the fdisk output of hdc (Pata Drive):

CODE

fdisk -l /dev/hdc

Disk /dev/hdc: 123.5 GB, 123522416640 bytes
255 heads, 63 sectors/track, 15017 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1               1       11047    88734996    7  HPFS/NTFS
/dev/hdc2   *       11048       14851    30555630   83  Linux
/dev/hdc3           14852       15017     1333395    5  Extended
/dev/hdc5           14852       15017     1333363+  82  Linux swap / Solaris

Extra info the fdisk of sde (Sata drive this drive changed from sda for some unknown reason):

CODE

fdisk -l /dev/sde

Disk /dev/sde: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 * 1 30400 244187968+ 7 HPFS/NTFS

Current menu.lst:

CODE

cat /boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,1)/usr/share/gfxboot/themes/pclinuxos/boot/message
default 1

title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/hdc2 acpi=on splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title Windows (Pata)
root (hd0,1)
makeactive
chainloader +1

## title Windows (Sata) Using this instead of the above boots the Sata drive but there's no entry in grub to boot Pata
# map (hd0) (hd1)
# map (hd1) (hd0)
# rootnoverify (hd1,0)
# chainloader +1

Reiver_Fluffi

Aug 18 2008, 11:23 PM

I would try changing the "root" entry for the "title Windows (Pata)" entry to:

CODE

root (hd0,0)

Given that it is the first partition on the first drive.

ianw1974

Aug 19 2008, 06:22 AM

I'd do that, but also later, we might actually have to check in grub which order the disks are actually seen by grub if hd0,0 doesn't work.

{BBI}Nexus{BBI}

Sep 16 2008, 10:36 PM

I finally got round to sorting this. I am posting the solution here, it may help someone else. Before I do that, a bit of background. The system configuration for this fix was:

1 Pata drive (master) connected to a raid card operating in ide mode. Dual booting Gnu/Linux and XP

1 Sata drive (slave) booting XP for playing games.

2 DVD drives chained together and connected to the single motherboard ide port.

CODE

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,1)/usr/share/gfxboot/themes/pclinuxos/boot/message
default 0

title linux (Pata Drive)
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/hdc2  acpi=on splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hdc2  acpi=on
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hdc2  failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title windows (Pata Drive)
root (hd0,0)
makeactive
chainloader +1

title windows1 (Sata Drive)
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1

Thanks again guys for your input.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.