Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!library.ucla.edu!news.mic.ucla.edu!unixg.ubc.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!xenlink!fsa.ca!news
From: hpeyerl@cpsc.ucalgary.ca (Herb Peyerl)
Subject: Re: bad144 problem?
Message-ID: <1993Aug17.151238.28169@fsa.ca>
Sender: news@fsa.ca
Nntp-Posting-Host: newt.fsa.ca
Organization: Little Lizard City
References: <9322908.27770@mulga.cs.mu.OZ.AU> <1993Aug16.180751.16931@crash> <24qnlt$s4p@hrd769.brooks.af.mil>
Date: Tue, 17 Aug 1993 15:12:38 GMT
Lines: 45
In article <24qnlt$s4p@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes:
>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.
The disk in question has 1222 cylinders. The problem is with the bootblocks.
Since they use BIOS to access the disk, the bootblocks can't read the
bad-block table if it's past the 1024th cylinder.
>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.
Also; remember that replacement sectors are allocated from the beginning
of the bad-block table backwards into the disk in a dynamic fashion; so
you don't want to be creating any filesystems in the region near the
beginning of the bad block table...
From dkbad.h:
---
* The bad sector information is located in the first 5 even numbered
* sectors of the last track of the disk pack. There are five identical
* copies of the information, described by the dkbad structure.
*
* Replacement sectors are allocated starting with the first sector before
* the bad sector information and working backwards towards the beginning of
* the disk. A maximum of 126 bad sectors are supported. The position of
* the bad sector in the bad sector table determines which replacement sector
* it corresponds to.
---
>IPL is an old mainframe term (Honeywell??) for 'Initial Program Load' as
>I recall.
I thought it was IBM but I could be wrong...
--
hpeyerl@novatel.cuc.ab.ca (actual but UUCP) | NovAtel Commnications Ltd.
hpeyerl@fsa.ca <faster> | <nothing I say matters anyway>
<NetBSD: A drinking group with a serious computing problem!>