Re: libata pm

2008-02-05 Thread [EMAIL PROTECTED]
Hi everybody, it looks like this will be a never ending story... After I got the new PSU and the raid was in full sync without any error for 48h, I thought all problems were gone. Today the sata errors reappeared and whenever the load is high enough I get the following: I exchanged two

Re: libata pm

2008-02-01 Thread Mark Lord
[EMAIL PROTECTED] wrote: Sorry for my late answer, but i had to sort this out first. After replacing the first PSU with a new Corsair 650W the power no longer fluctuated more than 0,01 V (and this only when booting up the drives...) I did a full resync on both raid arrays and got no more errors

Re: libata pm

2008-02-01 Thread [EMAIL PROTECTED]
Sorry for my late answer, but i had to sort this out first. After replacing the first PSU with a new Corsair 650W the power no longer fluctuated more than 0,01 V (and this only when booting up the drives...) I did a full resync on both raid arrays and got no more errors or resets, but there

Re: libata pm

2008-02-01 Thread Tejun Heo
Mark Lord wrote: After I got the new PSU and the raid was in full sync without any error for 48h, I thought all problems were gone. Today the sata errors reappeared and whenever the load is high enough I get the following: .. What exact brand/model drives are those again (hdparm --Istdout,

Re: libata pm

2008-01-30 Thread [EMAIL PROTECTED]
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

Re: libata pm

2008-01-30 Thread Tejun Heo
[EMAIL PROTECTED] wrote: Sorry for my late answer, but i had to sort this out first. After replacing the first PSU with a new Corsair 650W the power no longer fluctuated more than 0,01 V (and this only when booting up the drives...) I did a full resync on both raid arrays and got no more

Re: libata pm

2008-01-28 Thread [EMAIL PROTECTED]
Hello, Am Mo, 28.01.2008, 01:17, schrieb Tejun Heo: Hello, [EMAIL PROTECTED] wrote: With one, two and three drives on the pm I got no errors, so I tried to change the power supply. I got two power supplies for the 16 harddrives and the second one (with all Maxtor drives and the first pm)

Re: libata pm

2008-01-28 Thread Tejun Heo
Hello, Dusty. [EMAIL PROTECTED] 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

Re: libata pm

2008-01-27 Thread [EMAIL PROTECTED]
Am So, 27.01.2008, 01:38, schrieb [EMAIL PROTECTED]: Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo: [EMAIL PROTECTED] wrote: I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c That's a strange story. The reported error was PHY readiness changed and

libata pm

2008-01-26 Thread [EMAIL PROTECTED]
I'm currently running Linux *** 2.6.23 #1 SMP PREEMPT Sat Jan 26 17:59:58 CET 2008 x86_64 Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux with the libata-tj-2.6.23-20071011 path for 2.6.23 and for testing purposes linux-2.6.24-rc6-mm1 on a Asus P5WDG2-WS with two PCI-X Dawicontrol DC

Re: libata pm

2008-01-26 Thread [EMAIL PROTECTED]
I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c Am Sa, 26.01.2008, 18:03, schrieb [EMAIL PROTECTED]: I'm currently running Linux *** 2.6.23 #1 SMP PREEMPT Sat Jan 26 17:59:58 CET 2008 x86_64 Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux

Re: libata pm

2008-01-26 Thread [EMAIL PROTECTED]
Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo: [EMAIL PROTECTED] wrote: I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c That's a strange story. The reported error was PHY readiness changed and Device exchanged, both of which point to hotplug event.