From owner-freebsd-hackers Mon Mar 29 11: 7:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 3834C155DF for ; Mon, 29 Mar 1999 11:07:37 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA00197; Mon, 29 Mar 1999 12:07:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA12026; Mon, 29 Mar 1999 12:06:59 -0700 Date: Mon, 29 Mar 1999 12:06:59 -0700 Message-Id: <199903291906.MAA12026@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Darren Reed Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), hackers@FreeBSD.ORG Subject: Re: another ufs panic.. In-Reply-To: <199903291550.BAA28981@cheops.anu.edu.au> References: <40322.922716596@zippy.cdrom.com> <199903291550.BAA28981@cheops.anu.edu.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I toggled the internal BIOS termination setting and > it still crashes. Is it possible this disk corrupted so badly that it won't work until you newfs it and restore from scratch? This happened to me when I had some bad L2 cache, and over time the disk became so corrupted that even fsck could not repair the disk. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message