I subscribe to the digest, so I've copied the message and excluded the quoting characters (>)
------------- Quote ------ Received: from a.mx.surfutopia.net (a.mx.surfutopia.net [69.63.196.98]) by shear.ucar.edu (8.14.1/8.13.6) with ESMTP id l47HTpuJ013519 for <misc@openbsd.org>; Mon, 7 May 2007 11:29:52 -0600 (MDT) Received: by a.mx.surfutopia.net (Postfix, from userid 1000) id 5B2B9F23B; Mon, 7 May 2007 10:29:50 -0700 (PDT) Date: Mon, 7 May 2007 10:29:50 -0700 From: "John Mendenhall" <[EMAIL PROTECTED]> To: "Artur Grabowski" <[EMAIL PROTECTED]> CC: misc@openbsd.org Subject: Re: new openbsd 4.0 server, panic on ufsdirhash Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.6i X-Archive-Number: 200705/407 X-Sequence-Number: 49945 Artur, > Have you done forced fsck of the partitions? This sounds like a > problem with the data you have on disk. It would be even nicer if you > could update to a newer fsck because it has been updated to deal with > many new strange corner cases we've been seeing. Although, that might > or might not require a fully -current system, I'm not fully aware of > everything that has been going in fsck, but some of the ffs2 support > might have messed things up. > > We've seen one of those panics recently on an important OpenBSD > infrastructure machine and that led to a lot of fsck work (since > fsck didn't catch the particular problem). But on production > machines we deal with filesystem corruption by simply dumping the > filesystem and restoring it from scratch. You might want to try > that as well. We have done a forced fsck on the partition with the error. The problem is, there is no data other than the openbsd install. All I was trying to do was load the source from the openbsd cd into /usr/src. I don't need to restore since this is a new machine. I have not done anything to it. I'll just reinstall the entire thing. Unless someone wants me to try something else. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services ------------------- /QUOTE John, I've heard, and seen, a lot of odd problems that can't be duplicated with the same error when there's either of the following true. 1) overclocked hardware 2) bad system memory I'm doubting your system memory, but I'm curious about your overclocking. I don't think I've followed very carefully what you've already tried, and wonder if the mindset has ever drifted away from Hard Drives and ATA controllers. Another thread suggested catting /dev/ad0s1 >/dev/null and seeing how many errors you get. If you get errors, it might point to what can't be read (and maybe can't be written then). You might have to use another tool, but you should get the jist of what I'm trying to suggest. Good luck. If opportunity doesn't knock, build a door. "I can" is a way of life. More and Bigger is not always Better. The road to success is always uphill. Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com