thanks for the advice on cutting my losses, i can never seem to really get the hang of that; so after 3 weeks of puttering i finally broke down and got a different controller to use as the third; a CMD649 based siig ultra ata 100 pci. though not a cakewalk to set up, it is working reliably for 72hrs of heavy use under 2.4.19-ac4. so i am happy. IIRC the raid reconstruction would take around 145 min if i wasn't doing anything else on the machine. Of course slowing down if i was impatient and decided to build the filesystem during reconstruction. The closest i got with the 3 promise cards was to have all the hardware correctly detected. build the array. build the filesystem on it. fsck it. copy files onto it. try to check those files' md5sums ---CRC, dma timeout, channel reset, various errors eventually leading to hard reboot. upon reboot, kernel panic during md stuff. cheers, ryan On Thu, 2002-09-05 at 06:58, John Burton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Saturday 24 August 2002 06:26 pm, T. Ryan Halwachs wrote: > > Hi all, > > hoping you can help me diagnose and correct some problems I am having > > with 3 promise ultra100 cards I am trying to use with 6 WD1200 drives to > > create an ide raid5 array. > > > > I posted this to the ataraid list originally. > > https://listman.redhat.com/pipermail/ataraid-list/2002-August/001029.html > > > > since then, using 2.4.19-ac4 I was able to successfully build a raid5 > > array on 5 disks attached to 3 Promise ultra100 pci add-in cards > > (described in the original thread). I put some files on the array and > > they passed md5check. > > I couldn't unmount the array. > > I couldn't raidstop it. > > When I restarted the machine, it intermittently would not talk to the > > drive on the third card. > > Just out of curiosity, how long did you let the raid 5 array "build" in the > first place? I have seen similar problems (couldn't unmount etc) when the > array has not completed the build process. The larger the array, the longer > the build time (can take hours?). Patience is *definitely* a virtue when > working with raid 5 arrays. > > I had a similar setup (3 Ultra 100 TX2 cards + 6 WD drives) that I could never > get to work *reliably*. I would get a similar dmesg file. Note the last > controller stating "PDC20267: (U)DMA Burst Bit DISABLED" and ide6 and ide7 > being set to PIO (*not* UDMA 100) mode. I got this same message. The array > might boot up fine, but virtually every time within a few hours one or both > of the drives on the last controller would drop down to PIO mode and I/O to > the array would drop to the 2-3 MB/sec range (as measured by hdparm -Tt) > instead of the normal 30 MB/sec range. Bottom line, I *never* was able to > get 3 Promise Ultra100 TX2 cards working *reliably* in the same system. I > just recalled, I was never able to get 3 Ultra100 TX2 cards working *at all* > in the same system. What I did to get it functioning (and giving the results > described above) was to use 2 Ultra100 TX2 cards, and 1 Ultra100 card. > > I also tried the promise SuperTrak 100 with little or no success under linux. > I finally shelled out a few extra bucks and purchased a 3Ware board and have > been *very* happy with it ever since. Be willing to cut your loses before you > spend too much more time trying to get the three controllers to work > together.. > > John > > > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > PIIX4: IDE controller on PCI bus 00 dev 39 > > PIIX4: chipset revision 1 > > PIIX4: not 100% native mode: will probe irqs later > > ide0: BM-DMA at 0x14e0-0x14e7, BIOS settings: hda:DMA, hdb:pio > > ide1: BM-DMA at 0x14e8-0x14ef, BIOS settings: hdc:DMA, hdd:pio > > PDC20267: IDE controller on PCI bus 00 dev 68 > > PCI: Found IRQ 11 for device 00:0d.0 > > PCI: Sharing IRQ 11 with 00:11.0 > > PDC20267: chipset revision 2 > > PDC20267: not 100% native mode: will probe irqs later > > PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. > > ide2: BM-DMA at 0x1400-0x1407, BIOS settings: hde:pio, hdf:pio > > ide3: BM-DMA at 0x1408-0x140f, BIOS settings: hdg:pio, hdh:pio > > PDC20267: IDE controller on PCI bus 00 dev 78 > > PCI: Found IRQ 10 for device 00:0f.0 > > PDC20267: chipset revision 2 > > PDC20267: not 100% native mode: will probe irqs later > > PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. > > ide4: BM-DMA at 0x1440-0x1447, BIOS settings: hdi:DMA, hdj:pio > > ide5: BM-DMA at 0x1448-0x144f, BIOS settings: hdk:pio, hdl:pio > > PDC20267: IDE controller on PCI bus 00 dev 80 > > PCI: Found IRQ 9 for device 00:10.0 > > PCI: Sharing IRQ 9 with 00:07.2 > > PDC20267: chipset revision 2 > > PDC20267: not 100% native mode: will probe irqs later > > PDC20267: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode. > > PDC20267: FORCING BURST BIT 0x00 -> 0x01 ACTIVE > > ide6: BM-DMA at 0x1480-0x1487, BIOS settings: hdm:pio, hdn:pio > > ide7: BM-DMA at 0x1488-0x148f, BIOS settings: hdo:pio, hdp:pio > > hda: QUANTUM FIREBALL_TM3840A, ATA DISK drive > > hdc: RICOH CD-R/RW MP7040A, ATAPI CD/DVD-ROM drive > > hdf: WDC WD1200AB-00CBA1, ATA DISK drive > > hdh: WDC WD1200AB-00CBA1, ATA DISK drive > > hdj: WDC WD1200AB-00CBA1, ATA DISK drive > > hdl: WDC WD1200AB-00CBA1, ATA DISK drive > > hdm: WDC WD1200JB-75CRA0, ATA DISK drive > > hdp: WDC WD1200BB-00CAA0, ATA DISK drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > ide1 at 0x170-0x177,0x376 on irq 15 > > ide2 at 0x1800-0x1807,0x14f6 on irq 11 > > ide3 at 0x14f8-0x14ff,0x14f2 on irq 11 > > ide4 at 0x1818-0x181f,0x180e on irq 10 > > ide5 at 0x1810-0x1817,0x180a on irq 10 > > ide6 at 0x1830-0x1837,0x1826 on irq 9 > > ide7 at 0x1828-0x182f,0x1822 on irq 9 > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: task_no_data_intr: error=0x04 { DriveStatusError } > > hda: 7539840 sectors (3860 MB) w/76KiB Cache, CHS=935/128/63, DMA > > hdf: host protected area => 1 > > hdf: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, > > UDMA(100) hdh: host protected area => 1 > > hdh: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, > > UDMA(100) hdj: host protected area => 1 > > hdj: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, > > UDMA(100) hdl: host protected area => 1 > > hdl: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, > > UDMA(100) hdm: host protected area => 1 > > hdm: setmax LBA 234375120, native 234375000 > > hdm: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=232514/16/63, > > UDMA(100) hdp: host protected area => 1 > > hdp: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, > > UDMA(100) Partition check: > > hda: [PTBL] [469/255/63] hda1 hda2 > > hdf: hdf1 > > hdh: hdh1 > > hdj: hdj1 > > hdl: hdl1 > > hdm: [PTBL] [14589/255/63] hdm1 > > hdp: [PTBL] [14593/255/63] hdp1 > > Floppy drive(s): fd0 is 1.44M > > FDC 0 is a post-1991 82077 > > 8139too Fast Ethernet driver 0.9.25 > > PCI: Found IRQ 11 for device 00:11.0 > > PCI: Sharing IRQ 11 with 00:0d.0 > > eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0x1000, > > 00:e0:29:46:7f:97, IRQ 11 eth0: Identified 8139 chip type 'RTL-8139A' > > Linux agpgart interface v0.99 (c) Jeff Hartmann > > agpgart: Maximum main memory to use for agp memory: 232M > > agpgart: Detected Intel 440BX chipset > > agpgart: AGP aperture is 64M @ 0xf8000000 > > SCSI subsystem driver Revision: 1.00 > > md: linear personality registered as nr 1 > > md: raid0 personality registered as nr 2 > > md: raid1 personality registered as nr 3 > > md: raid5 personality registered as nr 4 > > raid5: measuring checksumming speed > > 8regs : 736.000 MB/sec > > 32regs : 346.000 MB/sec > > pII_mmx : 912.400 MB/sec > > p5_mmx : 950.800 MB/sec > > raid5: using function: p5_mmx (950.800 MB/sec) > > md: multipath personality registered as nr 7 > > md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 > > md: Autodetecting RAID arrays. > > [events: 0000000c] > > [events: 0000000c] > > [events: 0000000c] > > [events: 00000004] > > md: autorun ... > > md: considering hdl1 ... > > md: adding hdl1 ... > > md: adding hdj1 ... > > md: adding hdh1 ... > > md: adding hdf1 ... > > md: created md0 > > md: bind<hdf1,1> > > md: bind<hdh1,2> > > md: bind<hdj1,3> > > md: bind<hdl1,4> > > md: running: <hdl1><hdj1><hdh1><hdf1> > > md: hdl1's event counter: 00000004 > > md: hdj1's event counter: 0000000c > > md: hdh1's event counter: 0000000c > > md: hdf1's event counter: 0000000c > > md: superblock update time inconsistency -- using the most recent one > > md: freshest: hdj1 > > md: kicking non-fresh hdl1 from array! > > md: unbind<hdl1,3> > > md: export_rdev(hdl1) > > md0: max total readahead window set to 744k > > md0: 3 data-disks, max readahead per data-disk: 248k > > raid5: device hdj1 operational as raid disk 2 > > raid5: device hdh1 operational as raid disk 1 > > raid5: device hdf1 operational as raid disk 0 > > raid5: md0, not all disks are operational -- trying to recover array > > > - -- > John Burton, Ph.D. > Principal Associate GATS, Inc. > j.c.burton@xxxxxxxxxxxx 11864 Canon Blvd - Suite 101 > jcb@xxxxxxxx (personal) Newport News, VA 23606 > (757) 873-5920 (voice) (757) 873-5924 (fax) > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE9d2MDOw+BDg//vTwRAkJ3AKCHUCjvf0HRv9wujm3uygJU6EThygCg12AY > G1bdq2VLxTAqikniuE9rn88= > =+kl8 > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > Ataraid-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ataraid-list >
