From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.16-22 i686) The promise fasttrack 66 controller seems to be recognised by the kernel, but diskdruid or fdisk only shows the physical parameters of the first drive in a definded raid 0 array. Booting after install is not possible, lilo hangs after displaying LI Reproducible: Always Steps to Reproduce: 1. plug in a promise fasttrack 66 controller, setup a raid 0, install dos on a small partition on it. 2. install fisher, look at the wrong raid 0 parameter 3. boot after install Actual Results: Booting Linux not possible Expected Results: Linux should have booted At boot time kernel shows some infos about the chip set on the fasttrack 66, which looks ok. Seems that the controlelr is not asked about existing raid arrays.
This is a "fake software raid" card. Promise refuses to give specs for it, but drivers on the first cable work fine. Drives on the second cable are invisible for now, I'm working on fixing that. But it means you cannot mix linux with that other OS for now.
If promise refuses to give out the specs to the public why do FreeBSD seems to have it? Did a test with a fasttrack 100 today and it works perfectly with FreeBSD 4.2 and recognises the existing raid 0 array and the 2 drives connected to the second chanel! There are drivers avail from promise, but onhly for RH 6.2 and 7.0. Do somebody know if this drivers will work in the next RH release ( 7.1?).
If the driver is binary only, it will not work unless Promise update it. We won't ship it in this case. If it is GPL'd and open source, I would not mind having a look at it.
More info: Our kernel will find the second drive just fine. I'm looking into the bsd driver to see if there enough information there to make linux support it.
Using the existing RAID0 is not doable in a reasonable timeframe. Although the needed information is there, there is a very dangerous interaction with setups where people ignored the "RAID" and used linux to just install partitions on the drives. There is no safe way to detect if it is a "Windows RAID" or a "Linux drive" yet. Development will continue, but doing it properly will take some time.
Ok, FreeBSD uses different devices for disk and raid on this controller and does not allow to use a drive in both.