From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 4 13:07:18 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7811837B401 for ; Fri, 4 Jul 2003 13:07:18 -0700 (PDT) Received: from mail.inform.com.hk (mail.inform.com.hk [206.220.132.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 57EB843FFB for ; Fri, 4 Jul 2003 13:07:17 -0700 (PDT) (envelope-from achan@achan.com) Received: (qmail 10889 invoked by uid 0); 4 Jul 2003 20:07:16 -0000 Received: from unknown (HELO goofy) (achan@achan.com@203.169.176.76) by mail.inform.com.hk with SMTP; 4 Jul 2003 20:07:16 -0000 Message-ID: <014b01c34267$e5687a00$4200a8c0@goofy> From: "Andrew Chan" To: Date: Sat, 5 Jul 2003 04:07:28 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: ATA READ command timeout (and worse) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2003 20:07:18 -0000 While we are on this topic... I have been running 2 Seagate ATA66 disks (one on each channel) on a = HighPoint HPT370 ATA100 controller (FreeBSD 4.7 and then 4.8) for more = than a year and never had any problems. I recently built a new server with 2 Maxtor ATA133 80GB disks on a = Promise Fasttrak 100/TX2 and have been having random timeout problems = since. Sometime the system would be okay for a few days with no = problems, even after doing a few "make world" runs. Sometime timeout = problems showed up only minutes after a fresh install (I had been = re-installing to try to debug the problem). When timeout occured, the = ata driver took out the disk from the mirror array, and then either I am = stupid or something is wierd with the Promise firmware, there just = doesn't seem to be a good way to re-sync'ing array without major file = system corruption and the system was toasted. Assumming the disks, cables and power supply are all okay, is timeout = problems on Promise RAID cards still an existing and known issue = experienced by others? Andrew achan _A_T_ achan.com