Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!news.easystreet.com!not-for-mail From: tedm@agora.rdrop.com (Ted Mittelstaedt) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: How do I interpret bad144 error mesages? Date: 4 Mar 1997 08:34:14 GMT Organization: Cool Dudes Inc. Lines: 28 Message-ID: <5fgmq6$b7d$1@easystreet03> References: <33158FC6.1BB1@ccmail.bms.com> <5fd060$jd@uriah.heep.sax.de> NNTP-Posting-Host: sunnet.portsoft.com X-Newsreader: WinVN 0.92.6+ Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36509 In article <5fd060$jd@uriah.heep.sax.de>, j@uriah.heep.sax.de (J Wunsch) says: > >"Jeffrey M. Metcalf" <Jeffrey_M._Metcalf@ccMail.bms.com> wrote: > >> bad144: /dev/wd0s2: bad flag in bad-sector table bad144: /dev/wd0s2: >> bad magic number >> bad144: cyl/trk/sect out of range in existing entry: sn=62466193, >> cn=15491, tn=1 00, sn=181 > >Have you ever initialized the bad144 table at all? It's years ago >that i've been using my last ESDI drive that required bad144, but i >remember... > >I think you need to > > bad144 /dev/rwd0s2 0 > >to initialize it. Btw., *never* use the block device for this kind of >operation, always use the raw device. > If during the Install you mark bad-sector scanning in the fdisk screen, this is done automagically. You only have to do this if you add a second disk that needs it. bad144 isin't just for ESDI, some braindead IDE drives need it as well. Ted