Another Dual-boot

English Install/Boot/Login
1

OK, I have 3 separate hard drives. Drives 1 and 2 are striped together and I have openSUSE 11.3 installed. On the third disk I have WindowsXP-64 Professional. I installed SUSE first with the third disk unplugged. I then installed WinXP with the two SUSE disks unplugged. My fdisk -l is:

Disk /dev/sdb: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn’t contain a valid partition table

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000ca43

Device Boot Start End Blocks Id System
/dev/sda1 1 2090 16779776 82 Linux swap / Solaris
/dev/sda2 2090 2108 152576 83 Linux
/dev/sda3 2108 34744 262140672 83 Linux
/dev/sda4 * 34744 181786 1181114880 83 Linux

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x29915408

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

Disk /dev/md126: 1500.3 GB, 1500307783680 bytes
255 heads, 63 sectors/track, 182402 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x0000ca43

  Device Boot      Start         End      Blocks   Id  System

/dev/md126p1 1 2090 16779776 82 Linux swap / Solaris
/dev/md126p2 2090 2108 152576 83 Linux
/dev/md126p3 2108 34744 262140672 83 Linux
/dev/md126p4 * 34744 181786 1181114880 83 Linux

and my menu.lst is:

Modified by YaST2. Last modification on Wed Feb 16 12:51:45 EST 2011

THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader

Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

default 0
timeout 10
##YaST - generic_mbr
gfxmenu (hd0,1)/message
##YaST - activate

###Don’t change this comment - YaST2 identifier: Original name: linux###
title Desktop – openSUSE 11.3 - 2.6.34.7-0.7
root (hd0,1)
kernel /vmlinuz-2.6.34.7-0.7-desktop root=/dev/disk/by-id/md-uuid-9cd877c9:c09ad6c9:5174e424:a060748f-part3 resume=/dev/disk/by-id/md-uuid-9cd877c9:c09ad6c9:5174e424:a060748f-part1 splash=silent quiet showopts vga=0x375
initrd /initrd-2.6.34.7-0.7-desktop

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.3 - 2.6.34.7-0.7
root (hd0,1)
kernel /vmlinuz-2.6.34.7-0.7-desktop root=/dev/disk/by-id/md-uuid-9cd877c9:c09ad6c9:5174e424:a060748f-part3 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x375
initrd /initrd-2.6.34.7-0.7-desktop

###Don’t change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (fd0)
chainloader +1

title WinXP-64 Pro
map (hd0,1) (hd1,0)
map (hd1,0) (hd0,1)
rootnoverify (hd1,0)
makeactive
chainloader +

I can select Windows in grub loader and it looks like Windows will start. It starts with the Windows screen and then it reboots. I can start Windows if I unplug the SUSE disks.

Any help is greatly appreciated.

David

2

So Windows is rebooting because it does not understand the raid setup. This is very common when adding in such hardware to an existing Windows XP installation. Windows 7 is MUCH better at this. I have heard some people go into Windows XP, with the original setup and then DELETE ALL Hard drives and controllers and then shut it down and bring it back up with the added drive(s) on-line and have success. But if that does not work then the solution is to reload Windows onto the single hard drive as before but set as the boot drive in your BIOS AND with ALL hard drives on-line. Then, after you get it installed, you can switch back to your present setup and see if it will now work.

Thank You,