Date: Fri, 2 Aug 1996 16:00:03 -0700 (PDT) From: "Keith Beattie[SFSU Student]" <beattie@george.lbl.gov> To: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Cc: questions@freebsd.org Subject: Re: Reinstall from scratch (was vnode_pager_input: I/O read error) Message-ID: <199608022300.QAA01865@george.lbl.gov> In-Reply-To: <199608021451.OAA02181@btp1da.phy.uni-bayreuth.de> from "Werner Griessl" at Aug 2, 96 02:51:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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 \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608022300.QAA01865>