Peter Suetterlin wrote:
Not really - but somehow it looks as if the
communication with the drive is
Yes, that's what it looks like to me too.
Are all disks in the set the same and approximately of
the same age?
No and yes. It's a new machine with new disks. Half are Seagate and half
are WD just in case there is a manufacturer-specific batch-related problem.
I recall having trouble with WD disks when combining
older and newer 750GB
disks. Somehow they were very different in typical response time and this
could confuse the controller (or driver?). Symptoms were either drives not
being recognized at all or dropouts after some days/weeks of use....
I know there can be problems with TLER with WD drives because they've
deliberately broken the ATA8 spec to try to get you to buy their
expensive drives instead of their cheap ones (they succeeded in this
case, by accident, so I don't have that issue). But the symptoms of that
are the drive dropping out of the RAID whereas this is a complete
freeze, which I think is different.
My problem is compounded by the inconvenience that suse is on another
partition on that drive, so when it freezes the whole system goes down.
I think what I'm going to do is:
(1) run the WD diagnostic - if it says the disk is faulty then game
(2) move suse to a different disk so (a) hopefully the system doesn't
fall over if there's a problem and (b) it may change the symptoms.
(3) just buy another (non-WD) disk and see if the problem goes away. (if
I have to pay three times as much for a WD drive, I don't expect obscure
problems like this).
At present I still don't know whether the problem is a flaky disk, a
flaky motherboard, or just possibly a kernel/driver bug.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org