Ethical Hacking Training at InfoSec Institute

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Computer Forensics Computer-Forensics
[Top] [All Lists]

Re: how to simulate/insert a hard drive (physical) bad block error?

Subject: Re: how to simulate/insert a hard drive (physical) bad block error?
Date: Sun, 03 Apr 2005 20:26:11 -0400
On Fri, 01 Apr 2005 19:58:32 PST, Gary Funck said:

We'd like to test a disk imaging/copy device/procedure to see how it
fares if the source drive has one/more bad block errors.  Is there a way,
by communicating with the hard drive, presumably at a very low level,
to convince the drive that it should mark a sector as having a
permannent error, and to _not_ have it try and spare this particular
sector to a good sector on an alternate track?  Basically, we'd like
to insert what appears to be several (physical) bad blocks for the
purposes of testing.

Get yourself a cheap drive, and communicate with it with a hammer while
it's running. (Seriously.. it's probably the cheapest way to do it...)

Mst drives can only spare a sector on a *write*, because it needs data to write
into the spared block.  Also, it's usually silent about doing the sparing,
unless you use SMART or similar to ask it what's going on. If a block was OK
when written but subsequently goes bad, the drive really has no choice but to
report that the block is bad (it certainly can't return the data as it's bad,
and returning a block of zeros is a bad idea as well).

So you really need a way to create a bad block without actually sending
anything down the cable to the drive - thus the hammer...


Attachment: pgpfg6PTUUBQ2.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>