From owner-freebsd-scsi Tue Oct 24 2:57:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 8E42537B479 for ; Tue, 24 Oct 2000 02:57:49 -0700 (PDT) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id UAA21075 for ; Tue, 24 Oct 2000 20:57:46 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.1.1.R) for ; Tue, 24 Oct 2000 20:57:33 +1100 Reply-To: From: "Chris Knight" To: Subject: SCSI Errors... Date: Tue, 24 Oct 2000 20:57:32 +1100 Message-ID: <002401c03da0$d4868020$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal X-MDRcpt-To: freebsd-scsi@freebsd.org X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy, I've got an Infortrend IFT3102 with a 3-channel U2W daughterboard. One of the channels has decided to start running the following error: (da0:0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR (0x168) SCSIRATE (0x93) I've got the channel clocked at 40MHz. Clocking the channel back to 33MHz or 20MHz appears to work OK (several hours tested only), but clocking it straight back to 40MHz results in the above error immediately after the "Waiting for SCSI devices to settle" message. Cable replacement and different ASUS P2B-S motherboards attached to the channel make no difference. Just to be sure, I popped the disk array from the other IFT3102 and restored the NVRAM settings from the array. Sure enough, the logical disk mapped to channel #3 failed with the above error message when clocked at 40MHz. All logical disks have FreeBSD 4.1 installed to them. I don't expect anyone to be able to fix this problem. My guess is there's a timing issue between the host controller and the channel controller - enough for the host controller to see the data across the SCSI bus as garbage. I'd be interested in hearing from people with lots of SCSI experience whether controllers "turning bad" is a common event or not. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message