From owner-freebsd-questions  Mon Aug  5 03:28:32 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA07165
          for questions-outgoing; Mon, 5 Aug 1996 03:28:32 -0700 (PDT)
Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA07096
          for <questions@freebsd.org>; Mon, 5 Aug 1996 03:27:12 -0700 (PDT)
Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.7.5/8.6.12) id MAA03592; Mon, 5 Aug 1996 12:25:47 GMT
From: Werner Griessl <croot@btp1da.phy.uni-bayreuth.de>
Message-Id: <199608051225.MAA03592@btp1da.phy.uni-bayreuth.de>
Subject: Re: Reinstall from scratch (was vnode_pager_input: I/O read error)
To: beattie@george.lbl.gov (Keith Beattie[SFSU Student])
Date: Mon, 5 Aug 1996 12:25:47 +0000 ()
Cc: questions@freebsd.org
In-Reply-To: <199608022300.QAA01865@george.lbl.gov> from "Keith Beattie[SFSU Student]" at "Aug 2, 96 04:00:03 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Werner Griessl wrote:
> > 
> > I had the same fsck error (float) in the past because a damaged rambank.
> > After replacing the ram, a "fsck -b32 /dev/..." (alternate superblock)
> > worked for me.
> > 
> 
> Thanks, It's too late for me now but I'll remember this for the
> (hopefully never) next time I have to run fsck manually.
> 
> Out of curiosity, how did you determine that your RAM was bad, unless
> there was obvious physical damage.  I believe that demaged RAM will
> cause all sorts of problems, like mysterious signals killing processes
> and damaging data, but so will software problems.  Is there a way to
> check the integrity of a machines RAM with software?
> 

Sorry, don't know such a way.
I had the problem immediatly after installing a new 16Mb-module.
The ram was detected from the bios, but after booting FreeBSD the
system crashed after a few minutes.
A DOS based "RAM-test" even passed, but changing the module
with another (was a local vendor) solved all my problems.

Werner

> Thanks,
> Keith
> 
> -- 
> // Keith Beattie                  Lawrence Berkeley Laboratory (LBL) \\
> // SFSU Grad Student   Imaging and Distributed Computing Group (ITG) \\
> // KSBeattie@lbl.gov                 http://www-itg.lbl.gov/~beattie \\
> // 1 Cyclotron Rd.  MS: 50B-2239  Berkeley, CA 94720  (510) 486-6692 \\
>