From owner-freebsd-scsi Tue Jun 20 2: 0: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 86EC337BDA4 for ; Tue, 20 Jun 2000 02:00:02 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5K8xq286360; Tue, 20 Jun 2000 18:59:52 +1000 (EST) Date: Tue, 20 Jun 2000 18:59:52 +1000 From: Nick Slager To: Don Lewis Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000620185952.A86159@albury.net.au> References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006200754.AAA28201@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Tue, Jun 20, 2000 at 12:54:07AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > On Jun 20, 5:28pm, Nick Slager wrote: > } > } I have swapped out, individually, one at a time, each component of the SCSI > } subsystem - controller, cable, drive and terminator. I'm still getting the > } error message. > > You left out the power supply and power cable to the drive. A good point; I'll swap power supplies tomorrow. Thanks for the suggestion. > 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. > > Imagine the havoc you could cause by unplugging a drive that held a > mounted filesystem that was being written to and hooking up another > drive containing important data in its place if FreeBSD didn't detect > this condition. Yes, this would certainly be sub-optimal. The sporadic nature of this fault has been particularly frustrating. Often the system will run fine, all the time doing hefty reads/writes to various parts of the filesystem, for a whole day before it dies. One more thing I meant to mention in the original post: when the error occurs the small green LED on the front of the drive flashes in a peculiar pattern. It's hard to record exactly *what* the pattern is, as I have no reference point and the sequence is fairly lengthy. Seagate support insist they have no idea what the pattern represents, and "not even an engineer would know". Needless to say, it's not in the manual for the drive. :-( Has anyone come across a reference to the LED flash patterns on Seagate drives? Regards, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message