From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205 Description of problem: I have several machines with a built in Promise Raid controller Promise Technology, Inc. 20267 (rev 02) On the machines where all of the drives are on the controller (Raid 1) the installer doesn't see any disks (even with a driver disk, and/or expert mode) On a machine that has a drive on the normal ide controller, the install goes fine on that one drive, but even after an install, the drives on the raid controller are never seen. But the controller is seen (by doing a lspci) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Put all hard drives on a Promise Technology 20267 Raid Card 2.Make all drives a raid 1 (I believe any type of raid would do) 3.Try to do an install Actual Results: The installer said that I had no drives to install to Expected Results: It should have just used the drives like normal drives Additional info: These machines work fine under RedHat 7.1, with the 2.4.3 kernel (and the standard one as well)
I assume you've already tried the pdcraid driver. could you attach the dmesg of a machine booting but not seeing it ? (preferably one where you modprobe pdcraid)
Created attachment 51704 [details] errors from doing a modprobe pdcraid
Yes, I had tried the pdcraid driver, but always without success. I am attaching both /var/log/dmesg from the machine that boots, and the error output I get when I try a modprobe pdcraid. I don't have anything in the /etc/modules.conf relating to the pdcraid, so something there might be needed, but all of my searching hasn't brought up anything.
Created attachment 51705 [details] dmesg of bootable machine (unedited)
Arjan - I thought our pdcraid driver still only supported raid0 ?
I am sorry, this was a Raid 0 (striping). I always get the two mixed up. But since said that, I went and tried all of the different settings that were available, on the machine that two disks on the normal ide, and two on the raid controller. I tried Stripping-all disks, Stripping-each disk it's own stripe, Spanning-all disks, Spanning-each disk it's own span, Mirroring, No raid arrays at all, and turned the thing off in the bios. All of them (except turning it off in the bios) showed the same results in the dmesg, /proc/partitions, and modprobe pdcraid. Turning it off, and then I didn't even get anything in the dmesg or lspci.
I don't know if this will help, but here is the snippit from dmesg from the 2.4.18 kernel (from skipjack) and from the 2.4.3-12 kernel **2.4.18** PDC20267: IDE controller on PCI bus 00 dev 18 PDC20267: chipset revision 2 PDC20267: not 100% native mode: will probe irqs later PDC20267: ROM enabled at 0xfeae0000 PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode. PDC20267: neither IDE port enabled (BIOS) **2.4.3-12** PDC20267: IDE controller on PCI bus 00 dev 18 PDC20267: chipset revision 2 PDC20267: not 100% native mode: will probe irqs later PDC20267: ROM enabled at 0xfeae0000 PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode. ide0: BM-DMA at 0xdf00-0xdf07, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xdf08-0xdf0f, BIOS settings: hdc:pio, hdd:pio I don't know if that will help at all, but it might.
Is there a web page, or someplace I can look to see what parameters to put in modules.conf, or pass in lilo (I currently don't know how to pass parameters in grub) to make this work where I have it half and half. I've done plenty of searches but all I get is either old pages (dealing with 2.2 or 2.4.2) or very indepth discussions about the code in the kernel. I am not finding anything in between.
It is working now with Skipjack Beta2 for the system with half the drives on, and half off. It still doesn't see the drives during install, and I don't see the ataraid or pdcraid during install. But after install I can now load those modules and it let's me use the drives. So one part of the problem is working now.
PDC raid drive detect was problematic in some older kernels. Its fine in current ones. The trace shows a kernel which didnt have the needed PDC options. If this is still a problem with current kernels please re-open
I am sorry for not responding, I should have responded a while ago. Yes, It is working now with the latest errata kernels. I'm not positive exactly which one started working correctly with it, but I know the one I started using was the 2.4.18-9. I have put RedHat 9 on the machines and they work perfectly, with it's standard kernel as well as the latest errata kernel 2.4.20-18.