Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!gatech!news.byu.edu!cwis.isu.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [NetBSD-0.8] Problems w/ boot blocks
Message-ID: <1993May25.021250.26490@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1993May24.132050.29563@crash>
Date: Tue, 25 May 93 02:12:50 GMT
Lines: 33
In article <1993May24.132050.29563@crash> fpm@crash.cts.com (Frank Maclachlan) writes:
>I noticed that NetBSD-0.8 replaces the stage 2 wd boot, bootwd,
>w/ Julian Elischer's boot code. This causes a problem w/ a drive
>which has more than 1024 cylinders, requires bad sector forwarding,
>and has a NetBSD (or 386bsd) partition which ends beyond cylinder
>1023 (mine ends at cylinder 1629). The bad144 replacement list
>and replacement sectors are at the very end of the 386bsd partition
>and are not accessable by the boot code; it can't read anything
>beyond cylinder 1023. The boot code issues an error message
>indicating that the bad144 table is invalid (it's reading the
>wrong cylinder).
The "bad144" code looks at the disklabel to do it's evil work; it's only if
you don't lie to the disklabel program (the install program on NetBSD) that
you will ever see this problem. From what I remember (from a couple weeks
ago) the "bad144" code only cares about absolute sector numbers, not about
the real number of heads/tracks/sectors. That information is never used
except by the first stage boot.
If your milage varies, mail me and I'll look at the boot code again and
repost when I can.
Of course the real unimpeachable source on this is Julian.
Terry Lambert
terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me