From owner-freebsd-questions Tue Jun 20 1:52:34 2000 Delivered-To: freebsd-questions@freebsd.org Received: from zeus.tassie.net.au (zeus.tassie.net.au [203.57.213.21]) by hub.freebsd.org (Postfix) with ESMTP id B6BBD37BDA4; Tue, 20 Jun 2000 01:52:25 -0700 (PDT) (envelope-from Scott.Donovan@tassie.net.au) Received: from scott (xaviar.live.net.au [203.27.117.243]) by zeus.tassie.net.au (8.8.8/8.8.8) with SMTP id SAA26550; Tue, 20 Jun 2000 18:51:57 +1000 (EST) From: "Scott Donovan" To: "Don Lewis" , "Nick Slager" , , Subject: RE: Invalidating pack messages Date: Tue, 20 Jun 2000 18:51:54 +1000 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-reply-to: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Importance: Normal Disposition-Notification-To: "Scott Donovan" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG } } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } 1 Seagate 18Gb Baracuda drive > I believe this error means that the drive has gone away (power failure) > and come back (and has told FreeBSD that it has freshly powered up) in > such a way that FreeBSD has no way to tell if the drive it was talking > to before is the same drive that it is talking to now. To avoid severe > filesystem damage, FreeBSD prevents further access to the drive. We are having exactly the same problem with these drive at the moment. I can assure the drive remains powered. Perhaps this isa manufacturing fault ? However we brought around 8 of these drives only 4 went to freebsd machines these all play up. The ones on the NT 4.0 systems don't show any hickups ??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message