Does anyone know how to work out what's going on when the system reports a resource collision? I remember the old days where you had to manually configure IRQ numbers, but I gather that that problem was solved some years back with the then-newer PCI cards...
I had my machine's motherboard, CPU and memory replaced today. Since all indications were that the motherboard was damaged and causing the reliable system crashes, I'm pleased that this problem seems to be solved now. <fingers crossed> The old motherboard had RAID support, and 4 IDE controllers. I have a CDRW, DVD, 2x40GB IDE drives mirrored for reliability, and another IDE drive. Rather than get another specialty motherboard, this time I got a RAID card - HighPoint HP372A, much like the HighPoint HP370 motherboard that was replaced, and which worked fine. It just gave access to the drives - the actual RAID was done by Linux. Now the problem with the new system is basically that Linux can't seem to use the RAID card to get at drives. The BIOS see the drives (much like they were detected via the old motherboard), and Linux even knows that there's a PCI IDE card there - but it reports a "resource collision" and that it can't use the device. Does anyone have any idea where I can go from here? At the moment I'm running with just one drive (half of one of the RAID mirrors). One of the IDE controllers on the motherboard as one 40GB drive plugged in, the other controller has the DVD and CDRW. I'm told the RAID card can't drive a CD or DVD. The actual dmesg lines that look relevant are: Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH4: IDE controller on PCI bus 00 dev f9 PCI: Device 00:1f.1 not available because of resource collisions ICH4: (ide_setup_pci_device:) Could not enable device. hda: WDC WD400BB-32AUA1, ATA DISK drive hdc: SONY CD-RW CRX175E, ATAPI CD/DVD-ROM drive hdd: Pioneer DVD-ROM ATAPIModel DVD-115 0122, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63 Partition check: hda: hda1 hda2 < hda5 hda6 hda7 hda8 > [...] md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. [events: 00000103] [events: 00000103] md: autorun ... md: considering hda7 ... md: adding hda7 ... md: created md2 md: bind<hda7,1> md: running: <hda7> md: hda7's event counter: 00000103 md: RAID level 1 does not need chunksize! Continuing anyway. md2: max total readahead window set to 124k md2: 1 data-disks, max readahead per data-disk: 124k raid1: device hda7 operational as mirror 0 raid1: md2, not all disks are operational -- trying to recover array raid1: raid set md2 active with 1 out of 2 mirrors md: updating md2 RAID superblock on device md: hda7 [events: 00000104]<6>(write) hda7's sb offset: 29567488 md: recovery thread got woken up ... md2: no spare disk to reconstruct array! -- continuing in degraded mode md: recovery thread finished ... md: considering hda6 ... md: adding hda6 ... md: created md0 md: bind<hda6,1> md: running: <hda6> md: hda6's event counter: 00000103 md: RAID level 1 does not need chunksize! Continuing anyway. md0: max total readahead window set to 124k md0: 1 data-disks, max readahead per data-disk: 124k raid1: device hda6 operational as mirror 0 raid1: md0, not all disks are operational -- trying to recover array raid1: raid set md0 active with 1 out of 2 mirrors md: updating md0 RAID superblock on device md: hda6 [events: 00000104]<6>(write) hda6's sb offset: 3076352 md: recovery thread got woken up ... md0: no spare disk to reconstruct array! -- continuing in degraded mode md2: no spare disk to reconstruct array! -- continuing in degraded mode md: recovery thread finished ... md: ... autorun DONE. luke -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
