From owner-freebsd-stable Tue Apr 2 11:24:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from droid2.spawar.navy.mil (droid2.spawar.navy.mil [128.49.192.70]) by hub.freebsd.org (Postfix) with ESMTP id 698C737B41D for ; Tue, 2 Apr 2002 11:24:32 -0800 (PST) Received: from huckabeec (spyglass.nosc.mil [198.253.22.245]) by droid2.spawar.navy.mil (8.11.6/8.11.6) with ESMTP id g32JOAr31278; Tue, 2 Apr 2002 11:24:10 -0800 Message-ID: <020901c1da7b$f54ef6b0$90b411ac@huckabeec> From: "Craig Huckabee" To: "Doug Silver" , "Kenneth D. Merry" Cc: References: Subject: Re: SCSI tape error using Amanda/dump Date: Tue, 2 Apr 2002 14:24:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-MailScanner: Found to be clean Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM >command to clear this state. >(sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM >command to clear this state. For what it's worth, I get this same error with an Exabyte M2 drive we have here, also on an Adaptec controller, and most of the time the error is clear just by doing an "mt offline" and "mt status" (as the above error would suggest). But we've also had a bunch of bad tapes (sometimes brand new bad tapes) that also cause things to freeze like this. --Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message