Date: Wed, 21 Jun 2000 14:36:09 +1000 From: Nick Slager <nicks@albury.net.au> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000621143609.A3012@albury.net.au> 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 References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > } 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. I pulled out the power supply this morning, and replaced it with a brand new unit. The system has just crashed again with the 'Invalidating pack' error messages. > } After looking through the archives, I thought the 'Invalidating pack' message > } was a sure indicator of bad hardware/termination etc. Now I'm not so sure. > > 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. If this is the case (and I'm not doubting what you say), what else could cause this problem? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000621143609.A3012>