Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!beartrk!ceilidh!dnichols From: dnichols@ceilidh.beartrack.com (DoN Nichols) Newsgroups: comp.sys.3b1 Subject: Re: Fun with the Bad Block Table Message-ID: <1991Feb16.051327.537@ceilidh.beartrack.com> Date: 16 Feb 91 05:13:27 GMT References: <1991Feb15.231011.19453@cbnewsc.att.com> Organization: D and D Data, Vienna, VA. Lines: 33 In article <1991Feb15.231011.19453@cbnewsc.att.com> cmv@cbnewsc.cb.att.com (C M Votava) writes: >Helpful hint: [ ... text deleted ... ] > >OK, maybe sector 10 really means sector 11, so I un-bad-block sec 10 and >bad-block sec 11. Still no good...rats! Well, after diddling around for a >couple of days with this garbage, I finally did something that bad-blocked >BOTH sectors 10 and 11... THAT WORKED! Just to double-check, I took each >out one at a time and re-verified... they BOTH have to be marked as bad >blocks to get rid of that nasty HDERR message. > >Anybody know why??? I don't. Well, one consideration is that the unix-pc uses 512 byte PHYSICAL sectors on the hard drive, and 1K LOGICAL blocks from within the system. It takes two physical sectors to make one logical block. When you map out a bad sector, it replaces it with a nearby sector, usually sector 17 from that track. However, if you have both physical sectors bad from a block, the system may give up on reading a block when the first sector fails, and never even TRY the second sector of the block. (I don't have source, so this is just a guess). Anyone who knows more of the internals have a better answer? Good Luck with the drive DoN. -- Donald Nichols (DoN.) | Voice (Days): (703) 664-1585 D&D Data | Voice (Eves): (703) 938-4564 Disclaimer: from here - None | Email: --- Black Holes are where God is dividing by zero ---