*BSD News Article 92887


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!uunet!in2.uu.net!199.0.154.56!ais.net!ix.netcom.com!newsfeeds.sol.net!uniserve!news.mindlink.net!nntp.portal.ca!news.bc.net!info.ucla.edu!nnrp.info.ucla.edu!nntp.club.cc.cmu.edu!goldenapple.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!fas-news.harvard.edu!giffin.student.harvard.edu!user
From: giffin@fas.harvard.edu (Daniel B Giffin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: boot manager freaks with (flakey?) disk
Date: Sat, 05 Apr 1997 22:21:26 -0500
Organization: Harvard University, Cambridge, Massachusetts
Lines: 45
Message-ID: <giffin-0504972221260001@giffin.student.harvard.edu>
NNTP-Posting-Host: giffin.student.harvard.edu
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38516



I have had what looked like disk problems (bad144 seemed to be reporting
bad blocks in my root partition) right after installing some new memory
(it might be non-parity).  After all sorts of problems playing with the
disk and trying to reinstall things, I discovered 

The partition editor gives the following about my disk, which is supposed
to have a 16MB DOS partition followed by a FreeBSD partition taking the
rest of the disk:

   Geometry: 135 cyls/196 heads/63 sectors = 1666980 sectors

         offset      end         PType Desc  Subtype  Flags
   -------------------------------------------------------------
         0        62       6     unused   0
   wd0s1 63       24633    2     fat      6
   wd0s2 24696    1642284     3     freebsd  165      C
         1666980     1667231     6     unused   0

The install went fine (no complaints about the disk), but when I try to
start the thing up, the boot manager seems to get confused:


F1 . . . dos
F2 . . . BSD

Default: F? <I press F2>

F1 . . . dos
F2 . . . BSD

Default: F? <I press F2>

etc. ...

Is there anything more drastic I could do to my disk to fix whatever the
memory might have done to it?  Or perhaps the disk is permanently
damaged?  (I ran the bad-block check on things when I repartitioned, and
it either didn't find any problems or else wrote the bad block list to
disk without stopping to tell me.)

Thanks for any help.

daniel