On Thu, Mar 10, 2011 at 1:38 PM, EXTERNAL Konold Martin (Firma, RtP2/TEF72) <external.Martin.Konold@de.bosch.com> wrote:
Hi Greg,
From: Greg KH [mailto:gregkh@suse.de]
I also experience severe data loss whenever such an error occurs.
Perhaps you have a failing drive?
I hooked up another WD drive WDC WD5002ABYS-02B1B0 from a different familiy instead of the failing drive WDC WD3200AAJS-60Z0A0 to one of the failing machines and doing endless kiwi builds.
Sofar it is working since about 4 hours with an otherwise unmodified setup.
Can the observed error be explained with a firmware bug?
All failing machines have drives from the same family either WDC WD2500AAJS-60M0A0 or WDC WD3200AAJS-60Z0A0.
(Yes I validated that a failing drive had the most recent available firmware 03.03E03)
Best regards
Martin Konold
I haven't followed this thread, but there have been reported situations where a firmware bug caused smartd to actually trigger data loss. I don't recall if that was a rotating or SSD drive. That is when smartd would query the drive for diagnostic info, the drive would somehow lose data. If that might be your situation, you could attempt to disable smartd for a period of time and see if your issue goes away. Thanks Greg -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org