Hello,

I have a lot of troubles making my config to dual boot :

Asus P4P800 with Intel 82801ER SATA RAID set, 1 IDE HD and 1 SCSI Adaptec 2940UW adapter with 1 SCSI HD.

/dev/hda
/dev/sdc
/dev/sdb

Windows is installed on the RAID set, SuSE 9.1 on the IDE
(I previously used the SCSI drive, but due tu bugs related to 2940UW and int13, I moved Linux to IDE)

1. The GRUB way
If I use the IDE drive as 1st boot disk from the BIOS, GRUB starts and boot SuSE correctly. If I try to boot Windows from GRUB, I get the famous

root (hd1,0)
Filesystem type unknown, partition type 0x7
chainloader +1

Tried the fix suggested by SuSE support, but as I dont have the SuSE CDs, it does not work (installed SuSE from ftp)

2. The NTLDR Way
If I switch the 1st boot disk into the BIOS to Intel Array 1 (SATA RAID)
then windows is starting normally with NTLDR.
I thought, ok, I can maybe boot linux from NTLDR with a bootsec.lnx file, I tried to make a LILO boot disk, made the dd if= of= bs=512...
Then added the entry into NTLDR, unfortunately I get 99 99 99....

ne1 having any suggestion about how I could fix that multi boot problem without switching through the BIOS, kinda boring...

Thanks
Sylv1

lets deal with 2 first. When your bios was changed did you change your /boot/grub/device.map ..I suspect not.
anyhow my tutorial has a link to ntldr stuff here
http://www.linuxquestions.org/questi...hlight=trouble

2) your may need to post your grub file /boot/grub/menu.lst or /etc/grub.conf
so far as I can see you can NOT specify a root command to boot a windows system. Grub can not find a kernel so you need to use a norootverify command like this

title windows
norootverify (hd1,0)
hide (hd0,0) (your ide /boot partition table check your fstab)
makeactive
chainloader +1

a normal device.map file has ide then scsi devices like this

(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
(fd0) /dev/fd0

Thank you for your reply, lets deal with GRUB (I would prefer this bootloader)

Here are my config files :

------------------------------------------------------------------------------------------------------- /boot/grub/device.map

(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
(hd3) /dev/sdc
(fd0) /dev/fd0

-------------------------------------------------------------------------------------------------------- /boot/grub/menu.lst

# Modified by YaST2. Last modification on Thu Oct 21 23:28:06 2004


color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,1)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x31a splash=silent desktop resume=/dev/hda1 showopts
initrd (hd0,1)/boot/initrd

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

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,1)/boot/initrd

-------------------------------------------------------------------------------------------------- /etc/grub.conf

root (hd0,1)
install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst
quit

-------------------------------------------------------------------------------------------------

I will read your tutorial and post later any comment.

Sylv1

you appear to be claiming you now have one ide drive hd0=hda and three scsi drives?
me thinks you have only 2 so change your device map file to get rid of one.
the sda normally means primary sdb means slave you will have to remember or look how how you installed those drives or use a knoppix its either sda and sdb or sda and sdc

True ! did not notice that, I think the SATA RAID which is built with 2 SATA disks are sda and sdb, the sdc is a SCSI drive on a AHA-2940UW controller.

I removed sdb from the device.map file, and booted with IDE (hda=hd0) as 1st boot disk (GRUB is on that disk MBR) then I choosed Windows XP, but still getting :

booting 'Windows XP'

rootnoverify (hd1,0)
hide (hd0,1)
makeactive
chainloader +1

Error 13 : Invalid or unsupported executable format

Press Any key to continue...

Then back to GRUB select screen.

what ? so you do have 3 non-ide drives...heh heh
and error 13 is an error trying to mount a unknown kernel so you may have to force the device map file try

1) force the map file
open terminal command su then your root password then grub to go into a live grub
grub --device-map=/boot/grub/device.map ### (or where-ever you put it)
root (hd0,0)
###response must be a linux filesystem ext2 reiserfs etc if you get something weird here do NOT proceed please post response.
####If you do get something weird its because grub is seeing ide as not hd0

setup (hd0)#### (to re-install grub into ide mbr)
quit #### and close down terminal.

2) Now that I know you have a third drive its possible hd1 was the third drive. So take back what I said about deleting your third entry in device map file.
make a new device map file
(hd0) /dev/hda
(hd1) /dev/sdc (notice the change)
(hd2) /dev/sda
(hd3) /dev/sdb

then redo (1) to force acceptance of the device map file

3) I am hoping its the third scsi thats the difference. (you notice my confidence waning as grub and RAID are not hot items)
then we change your menu list file to rootnoverify (hd2,0)

and post the response.

4) I don't have raid have a peep at this link http://www.linuxquestions.org/questi...=raid+and+only

and go to the gentoo guy who has raid ok but raid on linux not raid on windows. It is my very personal opinion that we may still have an issue with your bios order. I am really really hoping that the hd1 error is because your bios jumps from ide to SDC.

5) so post your bios order. Once you understand what I am saying about your bios order feel free to make it (if different)
IDE then sda then sdb then SDC. and keep map file same order then see what happens.

But I am no longer confident. if this fails change your bios back to windows and do the ntldr thing in my other post as suggested by another LQ user to boot windows then chainload grub to boot linux

finally for your consideration re-read my trouble shooter section.

when your bios starts it jumps to mbr for IDE and as grub is in there (the stage1 file) it tells the computer to jump to location of grub stage2 file with an intermediate step of stage 1.5 for some filesystem formats. (This is becoming obsolete in later grub versions so its stage1 to 2 direct.)
then its up to your menu.lst to do the rest.

Now while in this menu file you can troubleshoot.

press C for commands
type root (hd then press tab you may get 4 responses h0 to hd3

type root (hd0,0) you should get a response showing a linux filesystem
by trying out root (hd1,0) and then hd2 etc and find that you get a linux response for a NON-HD0 we have solved it.

as Error 13 for your windows entry suggests something funny is happening and the rootnoverify FAILED. If it fails it tries to load a kernel and finds no acceptable kernel.

so bear with me on this one, a guess that you have a typo either in device.map file or in menu.lst file?

Here are some outputs

GNU GRUB version 0.94 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]

grub> root (hd0,0)
Filesystem type unknown, partition type 0x92 /* swap partition */
grub> root (hd0,1)
Filesystem type is reiserfs, partition type 0x93 /* root partition */

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/reiserfs_stage1_5" exists... yes
Running "embed /boot/grub/reiserfs_stage1_5 (hd0)"... 26 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+26 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.


---------------------------------- fdisk -l output -----------------------------------------------------------

linux:/home/sylvain # fdisk -l

Disk /dev/hda: 20.0 GB, 20020396032 bytes
16 heads, 63 sectors/track, 38792 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 2044 1030144+ 92 Unknown
/dev/hda2 * 2045 38792 18520992 93 Amoeba
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0xfffffeff of partition table 5 will be corrected by w(rite)

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

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3916 31455238+ 7 HPFS/NTFS
/dev/sda2 3917 26166 178723125 f W95 Ext'd (LBA)
/dev/sda5 ? 3916 3916 2147483647+ ff BBT

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

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

Disk /dev/sdc: 18.3 GB, 18351959040 bytes
255 heads, 63 sectors/track, 2231 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 1116 8964238+ 83 Linux

3) I am hoping its the third scsi thats the difference. (you notice my confidence waning as grub and RAID are not hot items)
then we change your menu list file to rootnoverify (hd2,0)

and post the response :

rootnoverify (hd2,0)
hide (hd0,1)
makeactive
chainloader +1


_ (blinking cursor)



It hangs.

5) so post your bios order. Once you understand what I am saying about your bios order feel free to make it (if different)
IDE then sda then sdb then SDC. and keep map file same order then see what happens.

Boot device Priority

1. Floppy
2. DVD Drive
3. IDE-Drive (that entry is the nr. 1 of the following list)

Hard Disk Drives

1. IDE-Drive
2. Intel Array
3. 2940UW - SCSI Drive

Boot device Priority

1. Floppy
2. DVD Drive
3. IDE-Drive (that entry is the nr. 1 of the following list)

Hard Disk Drives

1. IDE-Drive
2. 2940UW - SCSI Drive
3. Intel Array

GRUB hangs





Boot device Priority

1. Floppy
2. DVD Drive
3. IDE-Drive (that entry is the nr. 1 of the following list)

Hard Disk Drives

1. IDE-Drive
2. Intel Array
3. 2940UW - SCSI Drive

GRUB shows Error 13 : Invalid or unsupported executable format




FROM GRUB command

root hd(<TAB>
Possible disks are : hd0 hd1 hd2

root (hd0,0)
Filesystem type unknown, partition type 0x92
root (hd0,1)
Filesystem type is reiserfs, partition type 0x93
root (hd1,0)
Filesystem type unknowm, partition type 0x7
root (hd1,1)
Filesystem type unknowm, partition type 0xf
root (hd2,0)
Filesystem type is reiserfs, partition type 0x83

But I am no longer confident. if this fails change your bios back to windows and do the ntldr thing in my other post as suggested by another LQ user to boot windows then chainload grub to boot linux

Did that, installed GRUB on /boot (note I do not have a boot partition, it is inluded in the root partition)

did the dd to file, used it into NTLDR, but... I get GRUB _ (blinking cursor) and it hangs...

I must rely on the SuSE fix, but as I installed SuSE through ftp, I do not have CD and cant get to the parted fix dialog... SuSE personal CD does not work either...

Seriously thinking to re-install, but how can I be sure it won't happen again...

Great thx for your help aus9

if you are still tracking this..
the results of your grub hd tab only appear to have 3 drives and you have 4.

2) the ntldr way, which I can't test because I don't have XP says you may have an issue when you had no separate /boot partition.
by letting /boot be a subfolder of / you may have introduced the cylinder 1024 issue as per this
When I select Linux from the boot menu, I get a frozen "GRUB" (or an "L" in the case of LILO)

Make sure you created the linux.bin file correctly with the dd command. If you think you ran the command correctly, the problem may be that your /boot partition is beyond cylinder 1024 and your BIOS can't reach it. At system startup, the Windows boot loader lists the choices from boot.ini. When you select Linux, the boot loader then loads the 512-byte linux.bin file, and then BIOS tries to access the /boot partition to run GRUB. Some BIOS implementations can only address the first 1024 cylinders of a hard drive, which corresponds to ~8.5 GB. How do you fix this? Create your /boot partition before cylinder 1024; i.e. before ~8.5 GB.

3) I don't have SUSE either so can not accept any thanks as we did not solve it...yet.

Can you try looking at your bios and enabling LBA mode? to see if that resoves your ntldr issue?

4) the LILO way with ntldr is likely to have the same issue?

5) but you could always struggle along with a true grub boot floppies sloooow I know.

6) finally, if you do re-install please make a /boot partition below cylinder 1024 in case you want to try the ntldr way again

Thanks for outputs and your patience and sorry grub is not the answer.

7) can you post the message from suse support in case someone can give you a work around? You may need a separate post to get a result.

darn it, I have re-read some of your outputs and don't like what I am seeing.

when you did grub hd tab stuff some of your output was
hd0,0 = unknown
hd0,1 = reiserfs
hd2,0 = reiserfs

and later you say grub finds hd0,0 is a swap

1) in your menu for linux you have a kernel append line of resume=/dev/hda1
Was this once your initial file area to start ftp? or what

the reason I ask is if you truly don't need it you can use it to format it

now my maths is horrible I make hda1 9.8G and hda2 17.6G and that can't be right. Wheres my sleeping pills?

2) this hd2 intrigues me. You mention grub is in the mbr of the IDE drive and the output looks good when you re-run it.

But whats with the hd2 drive. Do you have another linux and if so are we actually counting correctly?

3) and I still can't work out why grub is not seeing 4 drives unless the bios is raided and the backup raid drive is lost to grub.

anyhow don't be shy whats on the scsi drive me thinks is hd2?

oops I mean we can use hda1 if its truly a swap and format it and make it a real /boot partition.

There are other posts I am sure we people have filled up their home directory and needed help getting a new bigger one

but more questions than answers oh well