From owner-freebsd-scsi Wed Feb 4 11:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19390 for freebsd-scsi-outgoing; Wed, 4 Feb 1998 11:24:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19385 for ; Wed, 4 Feb 1998 11:24:35 -0800 (PST) (envelope-from ath@bellcore.com) Received: from grapenuts.bellcore.com (grapenuts.bellcore.com [192.4.4.35]) by thumper.bellcore.com (8.8.8/8.8.8) with ESMTP id OAA16087; Wed, 4 Feb 1998 14:23:45 -0500 (EST) Received: from bellcore.com (localhost [127.0.0.1]) by grapenuts.bellcore.com (8.8.8/8.8.8) with ESMTP id OAA15899; Wed, 4 Feb 1998 14:23:44 -0500 (EST) Message-Id: <199802041923.OAA15899@grapenuts.bellcore.com> From: Andrew Heybey To: Doug White Subject: Re: SCB and 2940 Problems! In-reply-to: Doug White's message of Wed, 4 Feb 1998 09:27:07 -0800 (PST) Cc: scsi@FreeBSD.ORG, Lars Koeller References: Date: Wed, 04 Feb 1998 14:23:37 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" [Description of problems with a Seagate DDS-2 drive elided.] Definitely try to get a firmware update from Seagate. I had a similar problem with a Seagate DDS-1 drive (one that identified itself as an "ARCHIVE Python 25501-XXX 5.45"), and a firmware update fixed it. It is now at revision "5ACB" instead of "5.45" and it works fine. Try sending mail to tapesupport@seagate.com. It may take them a few days to answer, but they did eventually. andrew