Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!cs.mu.OZ.AU!acci.com.au!janj From: janj@acci.com.au (Jan Jaeger) Subject: Re: bad144 problem? Message-ID: <9323215.4533@mulga.cs.mu.OZ.AU> Sender: news@cs.mu.OZ.AU Reply-To: janj@acci.com.au Organization: Australian Computing and Communications Institute References: <9322908.27770@mulga.cs.mu.OZ.AU> <1993Aug16.180751.16931@crash> Date: Fri, 20 Aug 1993 05:19:08 GMT Lines: 26 1) IPL is an IBM term for boot if you like. 2) The bad sector table must be enabled by the badsect flag in the disklabel. To set this you issue 'disklabel -e wd0' and append badsect to the line with something like 'flags:' on it. 3) I have had problems where bad144 did not write the bad sector table in the same location as wd.c did expect it to be when the badsect flag was set in the disklabel. The result was a non-bootable... system. This was fixed by modifying the size of the 'c' partition. It seems that if you run 386bsd from a 'fdisk' type partition rather than a whole disk, then the bad sector table is located on the last track of the 'c' partition. However if your disk is a 'real' 386bsd disk then it will be allocated on the last track. 4) I have also had a problem with using disklabel on a newly lowlevel formatted disk. There seems to be a bug which prevents you from using disklabel because it can not read the label... 5) All this works for disks > 1023 cylinders. The only thing that has to reside within that is wdboot because that is loaded by the bios. -- Jan Jaeger