From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 4 16:44:59 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 2017E37B401 for ; Fri, 4 Jul 2003 16:44:59 -0700 (PDT) Received: from community10.interfree.it (community10.interfree.it [213.158.72.65]) by mx1.FreeBSD.org (Postfix) with SMTP id B512944020 for ; Fri, 4 Jul 2003 16:44:55 -0700 (PDT) (envelope-from victorvittorivonwiktow@interfree.it) Received: (qmail 18973 invoked from network); 4 Jul 2003 23:44:54 -0000 Received: from unknown (HELO workstation) (80.104.111.71) by mail.interfree.it with SMTP; 4 Jul 2003 23:44:53 -0000 Message-ID: <003401c34286$460d6640$476f6850@workstation> From: ".VWV." To: References: <014b01c34267$e5687a00$4200a8c0@goofy> Date: Sat, 5 Jul 2003 00:44:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: RE: 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 23:44:59 -0000 Andrew Chan wrote: > 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. !Never touch arrays after they have been configured for an installed system! > 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? HighPoint chipset ATA-RAID controllers work fine when they are onboard - as example, on an Abit AD7-RAID mainboard -. When they are connected to PCI bus like on Promise boards, it's often a circus. I don't know why, but be happy: on Linux is much worse. We all have to choose among the complications and the costs of the U160 or U320 SCSI at the 'shiny' side, and the apparent simplicity with a lot of lacks and problems of the ATA UDMA at the 'dark' side. In my opinion, forget SATA at all, but mine is only an intuition of a 'tecno-perfectionist-sensitive'... > Andrew VITTORI