Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On 7/1/05, Dominic Marks <[EMAIL PROTECTED]> wrote: > On Friday 01 July 2005 17:27, Alan Jay wrote: > > Thanks for this - I haven't try but will do so - but I do need a > > little help. I have downloaded the STABLE version and put it onto my > > machines. Do I have to compile the ATA driver into the system and if > > so how do I do so (sorry to ask no instructions on the web site > > below). > > This should be the procedure, but I could be wrong. > > o Get a fresh RELENG_5 > o Copy the ata mkIII update to your source tree Instead of just copying the files into your source tree, you should rename the following directories: sys/modules/ata sys/modules/ata-old (if it exists) sys/dev/ata sys/dev/ata-old NOTE: Just incase you wish to go back to the old ata driver. Then extract the ata mkII update into your source tree. > o Apply the diff for RELENG_5 to your source tree > o Build a fresh world + kernel > > For proper instructions Google about for [EMAIL PROTECTED]'s original > instructions. I think the subject was 'UPDATE: ATA mkIII patches' > or something along those lines. > Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 17:27, Alan Jay wrote: > Thanks for this - I haven't try but will do so - but I do need a > little help. I have downloaded the STABLE version and put it onto my > machines. Do I have to compile the ATA driver into the system and if > so how do I do so (sorry to ask no instructions on the web site > below). This should be the procedure, but I could be wrong. o Get a fresh RELENG_5 o Copy the ata mkIII update to your source tree o Apply the diff for RELENG_5 to your source tree o Build a fresh world + kernel For proper instructions Google about for [EMAIL PROTECTED]'s original instructions. I think the subject was 'UPDATE: ATA mkIII patches' or something along those lines. > Thanks. > > > -Original Message- > > From: Dominic Marks [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 01, 2005 5:00 PM > > To: freebsd-stable@freebsd.org; [EMAIL PROTECTED] > > Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using > > Tyan S5350 > > > > On Friday 01 July 2005 16:34, Alan Jay wrote: > > > Further to this the same ATA Timeout is seen in the latest SNAP > > > binaries (1st July). > > > > Do you see them with ATA mkIII as well? > > > > http://people.freebsd.org/~sos/ATA/ > > > > > ___ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" > > > > HTH, > > -- > > Dominic > > GoodforBusiness.co.uk > > I.T. Services for SMEs in the UK. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 17:12, Tony Byrne wrote: > Hello Dominic, > > DM> Do you see them with ATA mkIII as well? > > I tried the ATA mkIII patches a few weeks ago on one of servers, > which was suffering DMA TIMEOUTs, but they made no difference. Tried Linux on the same hardware? A strange suggestion perhaps, but I suspect that something is wrong with the hardware, or its configuration. It might turn up something interesting, at least it will rule the possibility of bad hardware in, or out. > This problem may only occur with certain combinations of controller > and SATA hard drive. For example, I have a workstation with an ICH5 > controller which had been frequently emitting TIMEOUT messages when > it had a 80Gb 7200k Seagate Barracuda SATA drive installed. As a test See below for what is possibily a very similar story. > this afternoon, I swapped out the Seagate for a new 250Gb Western > Digital SATA drive, and installed 5.4 RELEASE. The machine is now in > the process of building world, and I've yet to see any TIMEOUTs. I have lots of ICH5 and ICH6 systems and I haven't had any WRITE_DMA errors on them (to my knowledge). All of my problems in this area are to with Sil3112 based cards. An 80GB seagate drive attached to an Adaptec "RAID" controller with the Sil3112 in had absolutely terrible performance, about 4MB/s (r+w) at best. Replacing the Seagate disc with a Maxtor fixed the problem. I wasn't looking for these messages at the time, so they may have been a factor. What I did notice is that the drive (according to gstat) was improbably busy almost all the time for the minor load I was placing on it. I have another two Sil3112 based cards from no-name suppliers, these also seem to have issues - but they vary quite a lot. Just this week I have been setting up a SATA RAID using graid3 and 3x 250GB WD discs. In my test system I installed two of the Sil3112 cards, in addition to the integrated ICH6 onboard. Attaching a drive to each controller gives good performance ~105MB/s peak according to diskinfo. However trying to use the raid array in this configuration results in either of the drives dedicated to data having frequent problems, including the drives dropping out of the array at random during periods of load because of write FAILUREs. This makes the array useless since it is incapable of sustaining even a rebuild of the array without one, or both of the data drives failing. I never have any errors from the disc used for parity, which I put on the ICH6. If I reconfigure the machine and put both data discs on one of the Sil3112 controllers the system is stable and I can work with it. Performance suffers quite a bit, dropping to a peak of 98MB/s (ok, it's not much to cry about :-)). If I put the parity drive on either of the Sil3112 controllers I normally get a write failure, followed by a panic within minutes. What concerns me more about this configuration is that the speed limit on a rebuild of array. If I place a drive on each controller the rebuild runs at ~50MB/s (from memory, might be a little less). However, in the stable configuration the rebuild cannot pass 20MB/s. Which on a 500GB array, makes quite a difference to the rebuild time. Incidentally, this configuration is only stable on one of the Sil3112 cards I have (no RAID). I have one with RAID (probably almost exactly like the Adaptec), and one without. If your stuck with the hardware you have, like I am, I suggest that you setup a gmirror of your two dodgy drives, if one of them happens to encounter a read/write failure its less likely to take the system down. Hardly a fix though. Mikhail, I hope you don't mind me CC'ing you here. I read in a message that you had cured some problems like this by changing some of the PCI timers (?). Could you possibly say a little about what you did? > Regards, > > Tony. Cheers, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
Thanks for this - I haven't try but will do so - but I do need a little help. I have downloaded the STABLE version and put it onto my machines. Do I have to compile the ATA driver into the system and if so how do I do so (sorry to ask no instructions on the web site below). Thanks. > -Original Message- > From: Dominic Marks [mailto:[EMAIL PROTECTED] > Sent: Friday, July 01, 2005 5:00 PM > To: freebsd-stable@freebsd.org; [EMAIL PROTECTED] > Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 > > On Friday 01 July 2005 16:34, Alan Jay wrote: > > Further to this the same ATA Timeout is seen in the latest SNAP > > binaries (1st July). > > > > Do you see them with ATA mkIII as well? > > http://people.freebsd.org/~sos/ATA/ > > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > HTH, > -- > Dominic > GoodforBusiness.co.uk > I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 16:34, Alan Jay wrote: > Further to this the same ATA Timeout is seen in the latest SNAP > binaries (1st July). > Do you see them with ATA mkIII as well? http://people.freebsd.org/~sos/ATA/ > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4
I thought that as well. My machine is using a Tyan motherbaord with the Intel 6300SEB and I thought that was a reasnably conservative choice of motherboard. I don't know if this is a hint not to use SATA/IDE controllers any more but there are lots of occasions when it is more than enough power to be going on with. What is annoying is that there doesn't seem to be enough in the way of problem reports to say this is not supported so we know we are on to a loosing streak and need to find an alternate type of hardware. Does anyone know if the "Adaptec AIC-8110 SATA I" controller, which Tyan offer, as an add on module is supported. The release notes which I have checked do not mention this number. But hten this is probably a part number and not the chip number. Thanks. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias > Buelow > Sent: Friday, July 01, 2005 12:49 PM > To: Tony Byrne > Cc: Alan Jay; freebsd-stable@freebsd.org > Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 > with FreeBSD 5.4 > > Tony Byrne <[EMAIL PROTECTED]> writes: > > >ICH5 must be common in the field along with SATA disks from Western > >Digital. I would have believed faulty hardware to be the cause, but I > >have *three* machines that are capable of generating DMA TIMEOUTs > >while reading or writing SATA disks. > > In my case here, it's ICH6 and Seagate. Normally this is a good > combination that should work flawlessly... I mean, you can't get > more conservative than an Intel chipset and a Seagate disk. > > mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 (Adaptec AIC-8110 Compatibility maybe?)
Totally agree - I have 2 idential machines that have the same problem And have tried alternate hard disks all of which exhibit the same Problem. I would agree with you that the ICH5 must be common and the Tyan S3530 (http://www.tyan.com/products/html/tigeri7320r_spec.html ) with the Intel 6300SEB which I would have thought (as you say) was very common. I did notice that Tyan offer the Adaptec AIC-8110 SATA I controller as an add on module and I wondered if that might be supported but it doesn't seem by that number to be on the release list (any thoughts). > -Original Message- > From: Tony Byrne [mailto:[EMAIL PROTECTED] > Sent: Friday, July 01, 2005 11:29 AM > To: Alan Jay > Cc: freebsd-stable@freebsd.org > Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 > with FreeBSD 5.4 > > Hello Alan, > > AJ> There have been a number of comments and queries about ATA problems and > SATA > AJ> problems with 5.4 but no views as to if this is a real problem. > > I have to agree. I've had nothing but trouble with various Intel > boards with Intel ICH5 controllers and SATA hard disks under FreeBSD > and yet the problem either doesn't seem to be widespread and isn't > recognized by the community in general. I find that strange since the > ICH5 must be common in the field along with SATA disks from Western > Digital. I would have believed faulty hardware to be the cause, but I > have *three* machines that are capable of generating DMA TIMEOUTs > while reading or writing SATA disks. > > Regards, > > Tony. > > -- > Tony Byrne > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4
Tony Byrne <[EMAIL PROTECTED]> writes: >ICH5 must be common in the field along with SATA disks from Western >Digital. I would have believed faulty hardware to be the cause, but I >have *three* machines that are capable of generating DMA TIMEOUTs >while reading or writing SATA disks. In my case here, it's ICH6 and Seagate. Normally this is a good combination that should work flawlessly... I mean, you can't get more conservative than an Intel chipset and a Seagate disk. mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4
Hello Alan, AJ> There have been a number of comments and queries about ATA problems and SATA AJ> problems with 5.4 but no views as to if this is a real problem. I have to agree. I've had nothing but trouble with various Intel boards with Intel ICH5 controllers and SATA hard disks under FreeBSD and yet the problem either doesn't seem to be widespread and isn't recognized by the community in general. I find that strange since the ICH5 must be common in the field along with SATA disks from Western Digital. I would have believed faulty hardware to be the cause, but I have *three* machines that are capable of generating DMA TIMEOUTs while reading or writing SATA disks. Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
