Hello, Dusty. dusty@xxxxxx wrote: > Shuffling the drives did not change anything to the linkspeed of the 3 > ports running with 1.5 Gbps. Looks like the problem is port-related. Hmm... Okay. Maybe the signal traces or connectors have some problems. But 3.0Gbps on downstream port doesn't make any difference anyway so unless it leads to errors, it should be fine. > The first PSU (Multilane) offers (measured) 12,20 V on both lanes. This > falls during read/write access on all drives attached down to 12,10 V. That explains the PHY dropouts. I've even seen drives to do hard reset accompanying emergency head unload due to voltage dropping when high IO load hits. Of course, data in cache is lost. > The second PSU (Singlelane) offers (measured) 11,75 V. This doesn't change > during read/write access on all drives attached. I tested the second PSU > without anything attached and it still offered 11,75 V. 11.75 is still in spec and it doesn't fluctuate. I like this power much better. > I will try to add another PSU this evening and remeasure. > Currently the whole machine needs about 350W. > The PSUs are Targan 500W (Multilane - 2x12V 10A) Maybe one of the lane is only connected to video power connectors? IIRC, that was the idea of multilane power anyway. > and Noname 350W (Singlelane - 1x12V 10A) so this 'should' be enough... > > This night i copied the backup back to the first raid (the Maxtor drives) > without any error but during the transfer i got this on the second > (mounted but unused) raid: > ata10.00: failed to read SCR 1 (Emask=0x40) > ata10.01: failed to read SCR 1 (Emask=0x40) > ata10.02: failed to read SCR 1 (Emask=0x40) > ata10.03: failed to read SCR 1 (Emask=0x40) > ata10.04: failed to read SCR 1 (Emask=0x40) > ata10.05: failed to read SCR 1 (Emask=0x40) > ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen > ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen > ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen > ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1 cdb 0x0 data 0 > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Timeout during heavy IO can be caused from a number of things and bad power is one of them. Please lemme know your test result. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
