From owner-freebsd-questions Fri Aug 2 16:00:14 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08519 for questions-outgoing; Fri, 2 Aug 1996 16:00:14 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA08510 for ; Fri, 2 Aug 1996 16:00:12 -0700 (PDT) Received: (beattie@localhost) by george.lbl.gov (8.6.10/8.6.5) id QAA01865; Fri, 2 Aug 1996 16:00:04 -0700 From: "Keith Beattie[SFSU Student]" Message-Id: <199608022300.QAA01865@george.lbl.gov> Subject: Re: Reinstall from scratch (was vnode_pager_input: I/O read error) To: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Date: Fri, 2 Aug 1996 16:00:03 -0700 (PDT) Cc: questions@freebsd.org In-Reply-To: <199608021451.OAA02181@btp1da.phy.uni-bayreuth.de> from "Werner Griessl" at Aug 2, 96 02:51:30 pm X-Mailer: ELM [version 2.4 PL25] 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? 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 \\