hi @LL!

yes, its a very log text, but its a big problem! hope anyone in here can help me!

following problem:
i have got OnBoard IDE Raid Promise Fasttrak 100. SuSE 8.0 is the first distribution wich supports this extravgant form of raid.
the setup worked fine, it got my 2 hdds as one, mounted it correctly and so i could install SuSE 8.0.
after the first CD my computer decidet to reboot. lilo wrpte itself into the MBR and the pc turned off.
after that ... booting ended with "LI"
i think i know already where the problem is. on installing lilo there appears a warning: "Warning: /dev/ataraid/d0 is not on the first disk"; i have already hat this problem on my old PC as my harddisk was connected to secondary IDE, so its name was hdc; i had got the same problem, it stopped on booting by "li" i solved this problem by changing the IDE slot. with my Raid aray i cant change something in this way!

following configuration:

/dev/hda ... first disk of my raid array.
/dev/hdc ... second disk of my raid arry
hda and hdc are bundled with Raid0 (stripe)

/dev/hde ... CDRom
/dev/hdf ... DVDRom
/dev/hdg ... CDR/CDRW

after loading kernel modules for my raidarray (atariad, pdcraid) my disk is mounted in:

/dev/ataraid/d0p<partitionnumber>

following partitionconfiguration:
/dev/ataraid/d0p1 = /boot
/dev/ataraid/d0p9 = /
/dev/ataraid/d0p10 = /home
/dev/ataraid/d0p11 = swap

the problem is that linux is able to see the 2 harddisks. and hda goes before d0p1

i tried with several bootmanager to boot my linuxsystem. lilo is able to boot, but system stops with kernel panic "couldnt mount root filesystem" ... and i have correctly typed in! (/dev/ataraid/d0p9 ... i think that should go right!)

also grub stops on the same postition - kernel panic! also here i have typed in correctly the root device!

now im searching for a bootmanager to try booting linux.

perhaps there is another posibility to boot my system: hda (the first harddisk of my raidarray) is checked several. can i write the masterbootrecors only on hda? i wont loose my raidarray, i have got a lot of data on it. and i think its not a good idea if i "split" a part of the array.

would be happy if anyone could help me!

>>>Alois

just pushing onto the top ... its urgent!!!

>>>Alois

I have a similar situation I'm getting into (although it's the FasTrack/133 PDC20276 chip on an asus board, and it's Gentoo instead of SuSE)....

I'm still halfway through my gentoo install, so I don't know for sure yet (I'll know by tommorow), but I think GRUB will work. I heard somewhere of someone getting LILO to work with mirroring, but not striping.

You might try making sure the entire grubstuff+kernel+initrd (/boot area) is below the 32G mark on the raid device, or if that doesn't work make sure it's below 8G (although hopefully neither restriction is neccesary).

I also am doing the same thing with a FasTrack/133 PDC20276 chip, mirroring 2x WD 120G 8mb cache drives.

I have got the new kernel 2.4.18 and patched it with 2.4.19-rc1 and compiled it with the all the promise support etc.

The thing I am not sure about is if if is /dev/ataraid/d0p1 or sda0 (I guess I will try both if I can get any boot disk to see the array?)

Which tool do I use to partition it after its all working as in the past I have had problems using partion magic and any *nix partitioners as partition magic always reports errors after I have used a disk druid or fdisk.

I hope this works as it is for the server at work!
When/If I get this working I will post a solution.
Cheers,
Steve

Hey cyberdiamond! Another OCAU'er on here!

I'm having trouble installing RH 7.3 onto my lovly new raid array. 2 x 40gb ide Seagate's in hardware raid0 ( stripe ) on a promise FastHack66......

The RH installer can't find the raid array, but can find the individual hdd's, and want's to re-write the partition table, destroying my Win2k setup. I like to play game's sometime's as well. Don't worry, even my laptop has Linux on it!

Any idea's?

Cheers

ToranaGuy

I'm having the same problem. The Promise driver is picky about which gcc version you use to compile the (partial source code driver), also, the driver has problems with any other kernel version. I had to install linux on a non-raid drive. I still get a message about symbol errors, but when running linux, I can use the raid drive. One thing to try is to compile a new kernel with PDC2067 selected. ( newer kernels ) Maybe the Promise driver isn't needed then, but I don't know.

I have what may be a dumb follow up question on the PDC 20267 raid problem:
How is lilo supposed to load in the kernel or initrd (one of which has the driver). Isn't this a catch 22 situation. Doesn't the driver need to be loaded before the raid drive recognized and read from? But the driver is on the raid drive (kernel or initial ram drive loadable module).
Is a different loader needed other than lilo or grub?

If you have an ATA RAID (Promise 2067) with XP W2K etc and then Linux on a seperate JBOD do you still need to get Promise support from Linux?

I just blew up my ATA RAID partitions trying to install RH 9 on a seperate single IDE drive. GRUB must need the Promise driver to even begin to boot Linux off of the JBOD Linux drive. ??? But why did it trash the RAID partitions?