Need help with dual boot

I have a raid 0 nvidia and one other hard drive installed. raid 0 had win xp and I installed opensuse 11.1 on the second hard drive.

My problem is that I can’t get into xp. When i boot the computer it shows up on grub and when i select it, it goes to this black screen with something like hd(0,0) i forgot the exact line. I am at work right now so i can’t even check.

But the thing is that it just stays there and not boot into xp. I need some solution to this. All my documents and on xp and need to retrieve them. Also, how can I mount the xp sector using ntfs-3g?

Thanks

I’m not sure exactly what the problem is but I would try taking a look at your menu.lst file in /boot/grub/menu.lst. As for the mounting of your windows partition, did you try looking in /windows because that is where it mounts by default.

I know my partition is a mess, but this is what is in the menu.lst file

# Modified by YaST2. Last modification on Sun Jan 18 22:50:28 UTC 2009
default 0
timeout 8
gfxmenu (hd2,3)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.7-9
    root (hd2,3)
    kernel /boot/vmlinuz-2.6.27.7-9-pae root=/dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907-part4 resume=/dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907-part2 splash=silent showopts vga=0x31a
    initrd /boot/initrd-2.6.27.7-9-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.7-9
    root (hd2,3)
    kernel /boot/vmlinuz-2.6.27.7-9-pae root=/dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907-part4 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.27.7-9-pae

###Don't change this comment - YaST2 identifier: Original name:  openSUSE 10.2 - 2.6.18.8-0.3 (/dev/sdc3)###
title openSUSE 10.2 - 2.6.18.8-0.3 (/dev/sdc3)
    rootnoverify (hd2,2)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
    rootnoverify (hd0,0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: Linux other 1###
title Linux other 1
    rootnoverify (hd0,0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
    map (hd2) (hd0)
    map (hd0) (hd2)
    rootnoverify (hd2,0)
    makeactive
    chainloader +1

I found your troubles interesting. Have my own ideas on fixing it but I also found this reference with a lot of good info. Take a look at: Dual-Boot Linux and Windows 2000/Windows XP with GRUB HOWTO
Take care and have fun,
Chuck

according to the link you gave me when i typed in the df command i got a list of partitions but no /boot partition. what should i do?

Did you have a look at swerdna’s very instructive thread: Fixing vista multiboot with openSUSE - openSUSE Forums

Your menu.lst says, that you have at least three disks in your pc. The third partition of the third disk “in linux speak /dev/sdc3” is your linux 10.2 system. Does this still start correctly? The next partition /dev/sdc4 is your boot partition for Suse 11.1, right?

Your windows partition is on the first disc (with respect to the bios boot order). however, there is a mess concerning /dev/sda1: The next entry in your menu.lst says, that there - on /dev/sda1 - is an extra linux system installed (ubuntu? fedora? redhat? What did you try out there?) And yet another windows resides on the first partition of your third disk /dev/sdc1. In the last entry of your menu.lst this partition is mapped to the first disk, to make this partition look as drive “C:” to windows. What happens, when you choose this enty “windows 2” in grub? What starts, when you chose “linux other” in grub?
A lot of questions, I know. You might succeed pretty easily, when you clarify these questions and read the thread in the link above. If not, well, tell us.

If I am not mistaken, since you have a fakeraid (software) raid array, for it to be seen by linux and by grub then dmraid must be used. Boot into openSUSE, open a terminal, and post back here the output of the following:

sudo cat /boot/grub/device.map
sudo cat /etc/fstab
sudo mount

Thanks for all your help.

I think I was able to mount the raid hard drive to a folder in linux, but my other problem still continues. Can’t boot into Windows. I tryied to boot into the recovery mode with xp CD but a new problem happened. It is saying that there are no hard drive installed so I can do a fixmbr command. I need SATA control drivers for nvidia now. Dell only has for xp not linux. Is there a solution for that.

sudo cat /boot/grub/device.map

(hd0)   /dev/disk/by-id/raid-nvidia_gdcdbdbb
(hd2)   /dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907

sudo cat /etc/fstab

dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907-part4 /                                                                                                ext3       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD5000AAJS-00TKX0_WD-WDAPW0010907-part2 swap                                                                                             swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0


Device    Mountpoint  Filesystem  Parameters
/dev/sdc1  /A  ntfs-3g     user,users,gid=users,umask=0002  0 0
/dev/mapper/nvidia_gdcdbdbb_part1 /B ntfs-3g     user,users,gid=users,umask=0002                                                                              0 0

sudo mount

/dev/sdc4 on / type ext3 (rw,acl,user_xattr)
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sdc1 on /A type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096)
/dev/mapper/nvidia_gdcdbdbb_part1 on /B type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
gvfs-fuse-daemon on /home/dr3am/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=dr3am)
/dev/sr1 on /media/SU1110.001 type iso9660 (ro,nosuid,nodev,noatime,uid=1000,utf8)
/dev/sdd1 on /media/disk type vfat (rw,nosuid,nodev,noatime,flush,uid=1000,utf8,shortname=lower)

May help to clarify a few details. You have two drives which are in a fakeraid striped array; to enable that there (usually) is bios firmware which creates the array but also an OS driver to see the array. And, typically the array as set up in the bios is at the entire drive level, not at the partition level (if this is not the case, pls indicate such). So in Windows you must have installed the Windows raid driver that comes with this chipset. Linux will detect the fakeraid from the bios, and will use dmraid to access the array; this is what you see in fstab (as /dev/mapper) and in device.map in the designation for (hd0).

Be extremely careful to understand beforehand what you are doing with any Windows drivers, trying to change the MBR, etc. You could easily end up having to reinstall everything. The XP recovery that comes with retail XP (i.e., the “Recovery Console”) will of course not see the array; the driver will not be running. Recovery media that typically comes from a purchased computer usually just restores an image of the OS as delivered from the factory. Neither may see the drives as they are registered with the nvidia fakeraid firmware, not with the bios as they would be if not in the array, and again, the OS driver is not running when this media is used. As far as needing the nvidia SATA controller driver - why? If this raid is integrated into the motherboard chipset, then the firmware driver is enabled with a switch and/or utility in bios setup. The Windows OS driver should still be there intact.

You indicate that you were able to mount the Windows part of the array. Is that what is mounted under /B?

Before going any further, we need to see the disk layout and where/how grub was installed. So in openSUSE from a terminal please do the following and post back here the output:

sudo /etc/grub.conf
sudo fdisk -lu

(In the -lu above that is an “l” as in “long”, not the numeral 1.)

Finally, is the bios boot configuration still set up to boot from the first disk?

First of all thank you for all the help. I think i mentioned that i was able to mount the raid partition to /B folder.

Yes the array is set at entire drive level and is not partitioned. I have a third drive which has 3 partitions, one of which has Suse installed.

I have the drivers for nvidia and when i try to boot from XP cd in the beginning i am asked to press F6 if I want to load other drivers for raid control the only problem with that is that it has to be on a floppy drive and I don’t have one. I don’t mind reinstalling windows all over again except that i can’t right now.

sudo /etc/grub.conf

setup --stage2=/boot/grub/stage2 --force-lba (hd2,3) (hd2,3)
setup --stage2=/boot/grub/stage2 --force-lba (hd0) (hd2,3)

sudo fdisk -lu

Disk /dev/sda: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x4a1c4a1b

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   976543154   488271546    7  HPFS/NTFS

Disk /dev/sdb: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x19ac3140

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63   236990942   118495440    7  HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sdc2       236990943   239095395     1052226+  82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/sdc3       239095396   291531555    26218080   83  Linux
Partition 3 does not end on cylinder boundary.
/dev/sdc4       291531556   354442094    31455269+  83  Linux

Disk /dev/dm-0: 499.9 GB, 499999965184 bytes
255 heads, 63 sectors/track, 60788 cylinders, total 976562432 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x4a1c4a1b

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-0p1   *          63   976543154   488271546    7  HPFS/NTFS

Disk /dev/dm-1: 499.9 GB, 499990063104 bytes
255 heads, 63 sectors/track, 60786 cylinders, total 976543092 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-1p1   ?   218129509  1920119918   850995205   72  Unknown
Partition 1 does not end on cylinder boundary.
/dev/dm-1p2   ?   729050177  1273024900   271987362   74  Unknown
Partition 2 does not end on cylinder boundary.
/dev/dm-1p3   ?   168653938   168653938           0   65  Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/dm-1p4      2692939776  2692991410       25817+   0  Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

Is there any suggestions? I am still stuck and need help :frowning: