Re: ATA problems again ... general problem of ICH7 or ATA?


Am 20.08.2006 um 18:20 schrieb Greg Byshenk:

On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
On Sunday 20 August 2006 13:00, freebsd-stable-request@xxxxxxxxxxx wrote:

Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from provider, but as I
can saw, they picked whole new machine from their HW storage and put new
Samsung disk drives in. So these two last machines are brand new with
new cables. (Probably with a same type of cables - all machines are ASUS
RS120)

I can confirm the same behaviour with a ULi M1689/Newcastle Athlon64 based
system running 6.1-RELEASE-p3 (i386). ad6 just detaches without warning and
it takes a reboot to bring it back. atacontrol reinit has no effect. Tried
the following to resolve the problems:

- Changed cables (both ad4 and ad6)
- Changed SATA power to legacy
- Moved the NIC and anything else from the shared PCI INT (thought I'd cracked
it at this point as it was stable for a month, then it lost ad6 on a nightly
dump)
- Remade my gmirror array as an ar. Put it straight back to gmirror again when
I found out what a pain it is to rebuild after ad6 disappears.

I am not sure if it is related, but... I experienced a similar sort of
problem, although the details in my case are quite different.

What was similar was that I would "lose" two ATA drives from an array,
inexplicably. Reconfiguring the same drives and rebuilding would cause
them to work perfectly again -- for some number of days, after which
the same failure would occur.

What is different is that this was with a 3Ware RAID controller --
which made removing/raconfiguring/rebuilding much easier -- but I was
seeing the exact same errors.

No your errors are not related. As of my experience (and the experience of others) the controller forgetting or loosing drives is a "feature" 3ware.
We had similar problems with 3ware-7500-8 ATA controllers and i was reported of the same errors with 3ware-9000 series. Our in-house 3ware-9500S are not showing this kind of errors.

This errors are not driver or OS dependent such as they appear on FreeBSD as well on different Linux distros.
Since not all controllers suffering of these errors it is maybe depending on the firmware or board/chip revisions.

--

Best regards,

Konstantin Saurbier

------------------------------------------------------
Konstantin Saurbier Tel.: 0521 106 3861
Computerlabor Mathematik U5-138
Universitaet Bielefeld Universitaetsstr.25
33501 Bielefeld
email: saurbier@xxxxxxxxxxxxxxxxxxxxx
------------------------------------------------------



Attachment: PGP.sig
Description: Signierter Teil der Nachricht

Relevant Pages

  • Re: ST506 and/or ST412 hard disk drives
    ... couldn't make a machine with multiple 34 pin cables. ... spec for floppy drives but became standard usage. ... But as a matter of fact this particular controller *is* close to what ... floppies and the hard disk and the common signals are brought out on ...
    (comp.os.cpm)
  • Re: What do you think, will connecting a ST-225 HDD work?
    ... HDD controller type WD1002A-WX1. ... The last time I used one of these drives must be a quarter of a century ... the machine, but a small IDE drive, costing pennies will be much ... Yes, there are two ribbon cables per drive, a data cable per drive (the ...
    (uk.comp.homebuilt)
  • Re: ATA problems again ... general problem of ICH7 or ATA?
    ... change cables by myself, servers are dedicated from provider, but as I ... Samsung disk drives in. ... (Probably with a same type of cables - all machines are ASUS ... I found out what a pain it is to rebuild after ad6 disappears. ...
    (freebsd-stable)
  • RAID0 setup on FC3 (effect of IDE controllers and how to maximize throughput)
    ... A summary of my ide controller configuration is included below. ... 2-Assuming that drive speed is not the bottleneck, would drives on ide1 ... around with the cables for IDE0 and IDE1. ...
    (comp.os.linux.setup)
  • Re: Odd DVD-RW Drive Failure
    ... Maybe the cables weren't fully seated in the MB or drive, ... Oh and the drives that got the 36" seem just fine. ... The controller that the message mentioned is usually the one located on ... The key to your problem is in understanding "The driver detected a ...
    (microsoft.public.windowsxp.general)
Loading