Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail
From: burgess@hrd769.brooks.af.mil (Dave Burgess)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: bad144 problem?
Date: 17 Aug 1993 08:49:35 -0500
Organization: Armstrong Laboratory, Brooks AFB, TX
Lines: 40
Message-ID: <24qnlt$s4p@hrd769.brooks.af.mil>
References: <9322908.27770@mulga.cs.mu.OZ.AU> <1993Aug16.180751.16931@crash>
NNTP-Posting-Host: hrd769.brooks.af.mil
In article <1993Aug16.180751.16931@crash> warelock@crash.cts.com (Tom Zacharoff) writes:
>Jan Jaeger (janj@acci.com.au) wrote:
>:
>: You will need to have the badsect flag in you disklabel set before
>: wd.c will even look at the bad sector table. Depending on what
>: configuration you run (a 386BSD partition or full disk) you
>: will also have to ensure that the table ends up in the right spot
>: else you won't be able to ipl your system. Also, I have had a few
>: problems with running disklabel on a 0.2.4 system where there was
>: no label yet.
>
>How do I set the badsect flag in my disklabel? Is it a function of the
>disklabel program?
>
In the disklabel in disktab, there should be an entry ':sf'. There is a
similar entry ('flags:') in the 'text' version of the disklabel.
>I have a full disk configuration. Where does the table have to be? How do I
>get it there? What does it mean that I won't be able to ipl my system?
With a full disk configuration, your bad sector table should be the last
track. There have been problems identified with disk drives that
physically have more than 1023 cylinders (which I think the disk in
question has), but I don't recall if this is specifically for those
units that have DOS loaded on them or not.
Putting the bad track on the disk involves making sure that the
disklabel identifies your disk as as a 'sector forwarding' drive and
having run bad144 to locate and lock out the bad sectors. Be sure to
run fsck after you run bad144 to make sure that any files that are
affected by the change are flagged as broken.
IPL is an old mainframe term (Honeywell??) for 'Initial Program Load' as
I recall.
--
------
TSgt Dave Burgess
NCOIC AL/Management Information Systems Office
Brooks AFB, TX