Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jun 2000 18:51:54 +1000
From:      "Scott Donovan" <Scott.Donovan@tassie.net.au>
To:        "Don Lewis" <Don.Lewis@tsc.tdk.com>, "Nick Slager" <nicks@albury.net.au>, <scsi@FreeBSD.ORG>, <questions@FreeBSD.ORG>
Subject:   RE: Invalidating pack messages
Message-ID:  <NDBBLPAOMLLPBEFBDMMJCEENCBAA.Scott.Donovan@tassie.net.au>
In-Reply-To: <200006200754.AAA28201@salsa.gv.tsc.tdk.com>

next in thread | previous in thread | raw e-mail | index | archive | help
}
} 	(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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBLPAOMLLPBEFBDMMJCEENCBAA.Scott.Donovan>