Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!oleane!tank.news.pipex.net!pipex!news.mathworks.com!news.kei.com!newsstand.cit.cornell.edu!newsfeed.cit.cornell.edu!news.tc.cornell.edu!newsserver.sdsc.edu!news.cerf.net!pagesat.net!quack!quack.kfu.com!nsayer From: nsayer@quack.kfu.com (Nick Sayer) Subject: bad144 trouble - possible bug in SBR code? Message-ID: <m#8b0Zx@quack.kfu.com> Sender: news@quack.kfu.com (0000-News(0000)) Organization: The Duck Pond public unix, +1 408 249 9630, log in as guest. Date: Fri, 1 Dec 1995 14:31:30 UTC Lines: 15 My FreeBSD partition has a bad block on it 30 sectors in. The 2.1.0 install seemed quite happy to run bad144 and isolate the block, and so long as I load the kernel off a floppy (and use the -r flag), everything is fine. If I attempt to load the kernel from the hard disk, it works, but it tries to read the bad block for about a minute before realizing that it has been mapped elsewhere (it does note the existence of the bad144 table). Since it found the bad block map, why doesn't it just go to the replacement sector immediately? This big delay is a big drag. -- Nick Sayer <nsayer@quack.kfu.com> | "When DEC hits bottom, they're going N6QQQ @ N0ARY.#NORCAL.CA.USA.NOAM | to make an awful big splat." +1 408 249 9630, log in as 'guest' | URL: http://www.kfu.com/~nsayer/ | -- David Hawkins