Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!darwin.sura.net!europa.asd.contel.com!awds.imsd.contel.com!wlbr!snidely!staylor
From: staylor@snidely.UUCP (Scott G. Taylor)
Newsgroups: comp.unix.bsd
Subject: [BSD386] wd.c and badblocks with the WD1007V
Message-ID: <148@snidely.UUCP>
Date: 1 Dec 92 23:22:29 GMT
Lines: 39
Problem: WD1007V with a 766mb drive won't do the alternate sector mapping.
First off, my BSD386 system works great.
But(t), I can't get around the bad sectors on my Wren VI (676mb
formatted) drive.
The WD1007V-WE2 controller is set for alternate sectoring. This should
allow the controller to do its own mapping of bad sectors after it formats
the drive. The physical drive parameters are 1630c/15t/53s. With alternate
sectoring enabled, it is reporting 1630/15/52 and using the extra sectors
for its own mapping. Thus, it should provide a virtually error-free
drive to BSD386, as it does to MACH386 and DOS.
However, using the BIOS on the WD1007V to format, mark bad sectors,
and surface analyze the drive, the sector mapping is not happening;
every track and sector that the BIOS maps bad shows up with BAD144
as bad. The alternate sectoring appears to be either overridden
or corrupted.
Additionally, when running BAD144, there is *NO* bad block table
present on the drive. I have modified my BAD144 to initialize the
table, but after mapping just a few bad tracks, I run out of room
(>126 bad sectors).
I have verified the problem with two controllers, so I assume there
is a software issue here.
I have already installed the Norway Wd.c, but that should not affect
how the controller itself presents the drive to 386BSD.
Any clues?
--
Scott G. Akmentins-Taylor InterNet: staylor@snidely.pmdr.wlv.ca.us
MRY Systems staylor@cerfnet.com
UUCP: snidely!staylor
---- "Dzied akmens, Briva Latvija!" ----