Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!solaris.cc.vt.edu!csugrad.cs.vt.edu!not-for-mail From: jaitken@csugrad.cs.vt.edu (Jeff Aitken) Newsgroups: comp.os.386bsd.misc Subject: Crash! Bang... Oops Date: 18 Aug 1994 21:29:56 -0400 Organization: Virginia Tech Computer Science Dept, Blacksburg, VA Lines: 46 Message-ID: <3311uk$t08@csugrad.cs.vt.edu> Reply-To: jaitken@vt.edu NNTP-Posting-Host: csugrad.cs.vt.edu X-Newsreader: TIN [version 1.2 PL2] I'm not sure what happened here, but I'll summarize as best I can: I moved recently (back to school). Everything worked fine before I packed up. Once I got to school, I added 8MB of RAM (to bring my total to 16MB) Then I booted FreeBSD, and everything seemed to work ok Then I booted DOS, and things started to go haywire. First, himem started complaining about memory being bad. Well, OK, lets run a memory exerciser on it. I assume FreeBSD has one, so I attempt to boot it. I get something like this Automatic reboot in progress /dev/rwd1a /dev/rwd1e pid 30: rm: exit on signal 11 seg fault - core dumped pid 4: sh: exit on signal 11 Then I reboot, and there's a rm.core and sh.core file in / (I booted into single user, BTW, because /dev/rwd1a was modified). I try to rm rm.core. System crashes, tries to sync disks (and fails), then dumps a memory image. It then tries to reboot, but now cannot find /dev/wd1a. I cannot fsck it manually because fsck is not on the bootable floppy! (Or if it is I cannot find it) When I try to mount either /dev/wd1a or /dev/wd1e, I get "/dev/wd1x on /mnt: Bogus super block" Hmmn, looks like the crash was a good one. I yanked the extra 8MB of memory, and get the same results. Does anyone have any idea what I can do to remedy this, other than re-install everything? I really don't want to reconfigure everything. I forget, does the installation muck with /usr? Or does it just create a usable / ?? Thanks! Jeff -- Jeff Aitken jaitken@vt.edu