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!munnari.OZ.AU!news.hawaii.edu!news.uoregon.edu!hunter.premier.net!op.net!news.mathworks.com!newsfeed.internetmci.com!ns1.netone.com!news.sprintlink.net!news-fw-12.sprintlink.net!news2.insinc.net!onramp.ca!geac!itcyyz!jhui From: jhui@itcyyz.ipsa.reuter.com (Jimmy Hui) Subject: Bad144 not working? Organization: Reuters Information Services (Canada) Ltd., Toronto Message-ID: <DvB5H7.ALK@itcyyz.ipsa.reuter.com> Date: Mon, 29 Jul 1996 13:58:17 GMT Lines: 20 Has anybody ever had problems with bad144 working on ESDI drives? We have a Micropolis 1558 adn a WD1007 controller running 2.1.5Release. The drive had been low-level formatted with the WDFMT.EXE program from www.wdc.com to 15 heads, 1224 cyls and 35 sect/track. During the install of 2.1.5, a bad block scan picked up the bad sectors, but later when I use the disk, it would report a "hard write error" at a certain block with matches with the ones in the bad144 table. This happened for about two thirds of the bad blocks in the table. I assume bad144 isn't doing its job of forwarding the data to valid blocks on the disk. I end up having to use badsect to tie up the bad blocks so that it won't use those bad parts of the disk. Does anyone have any ideas getting bad144 to work correctly in this case? Any advice will be appreciated. Thanks in advance. ../Jim