Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!hellgate.utah.edu!cc.usu.edu!ivie From: ivie@cc.usu.edu Newsgroups: comp.os.386bsd.questions Subject: Re: bad block handling... documentation? what documentation? Message-ID: <1993May24.103504.68390@cc.usu.edu> Date: 24 May 93 10:35:04 MDT References: <C7J4Dt.A1A@sugar.NeoSoft.COM> Organization: Utah State University Lines: 20 In article <C7J4Dt.A1A@sugar.NeoSoft.COM>, peter@NeoSoft.com (Peter da Silva) writes: > Well, I've been trying to get bad144 turned on on my ESDI drives for months > and I still get the same errors on boot up: a hard read error on the bad > sector map itself. Now, the 'c' and 'd' partitions cover the map, and I can > read and write it just fine... at least when I read I read the same thing > I wrote. This happens on wd0 and wd1, and it happens even when I adjust > the diskmap to 1221 cylinders instead of 1222 (and adjust 'c' and 'd' to > match). > > Any ideas? No, but sympathy. In order to get NetBSD to run on my RD53 MFM disk, I had to lop a bunch of cylinders off the end and a head off the bottom. It seemed to be getting strategically placed bad blocks while it was trying to set everything up. Let me know if you figure out what's going on. Roger Ivie ivie@cc.usu.edu