Hi, I wrote: > I'm experiencing problems with my Promise SATAII TX4 controller, quite > similar to what Kim reported a few months ago. > > Using a fresh linux-2.6.12.5 upstream kernel to boot into a rescue shell > (so there's no distribution specific stuff going on, nothing else > loaded, etc.), I can access my three connected Maxtor 120GB drives just > fine, as long as I do so individually. [...] >>Attached devices: >>Host: scsi0 Channel: 00 Id: 00 Lun: 00 >> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5 >> Type: Direct-Access ANSI SCSI revision: 05 >>Host: scsi1 Channel: 00 Id: 00 Lun: 00 >> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5 >> Type: Direct-Access ANSI SCSI revision: 05 >>Host: scsi3 Channel: 00 Id: 00 Lun: 00 >> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5 >> Type: Direct-Access ANSI SCSI revision: 05
OK, apparently it's somewhat hardware related after all. I've added a Seagate drive (Model: ST3120827AS, Rev: 3.42) and reading from this drive together with two of the Maxtor drives (any two of the three) currently works without problems (for now). Switching ports and cables doesn't change anything, so it's not related to that. But how can that be? The individual drives don't reveal any problems and (as reported in my previous mail) the drives worked seamlessly for a few weeks ... I'll have to do some more testing and this is probably off-topic by now, so I'll stop with the noise now. Fabian - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
