Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!europa.chnt.gtegsc.com!newsfeed.internetmci.com!news.mathworks.com!gatech!swrinde!elroy.jpl.nasa.gov!ames!hpg30a.csc.cuhk.hk!hkpu01.hkp.hk!c1221442 From: c1221442@comp.polyu.edu.hk (Arthur S.L. Hsieh) Subject: bad144 runs at least 16 hrs! Message-ID: <DCByrH.3I0@hkpu01.polyu.edu.hk> Sender: usenet@hkpu01.polyu.edu.hk (Usenet Account) Nntp-Posting-Host: csun76.comp.polyu.edu.hk Reply-To: c1221442@comp.polyu.edu.hk Organization: Department of Computing, The Hong Kong Polytechnic University X-Newsreader: TIN [version 1.2 PL2] Date: Wed, 26 Jul 1995 15:52:29 GMT Lines: 13 I tried to install FreeBSD 2.0.5R from the updated bootdisk to the Seagate ST251 MFM 40M hard drive. I turned on bad144 checking because I know there're 3 bad sectors on that drive. After commit was choosen, the bad144 process had been running for at least 16 hrs before I reset the system. Does it really need so long to check only 40M disk space? The time was far more than what is needed in low level formatting that drive. From the noise, I feel the process has different idea on the interleave value that the drive has. Any successful story on using bad144 on a MFM drive? If so, how long does it take? -- Arthur Hsieh c1221442@comp.polyu.edu.hk