On 10/23/2012 9:13 PM, V G wrote:
> Hi all,
>
> If I run `badblocks -wsv /dev/sdd` on Linux (for example), which does a
> filesystem-level bad-block scan on a hard disk using a write-read -compar=
e
> method, would it trigger the hard disk's own internal bad block
> flagging/remapping mechanism? If not, how would I go about triggering the
> hard disk's internal hardware bad block flagging mechanism? Would a lengt=
hy
> SMART scan do the job? Or does it generally work automatically when a
> read/write error is "detected"?


It is really brand and model specific as to how it handles both SMART=20
and recording of errors. I have seen some drives that will automatically=20
log it when a rw error occurs while others will only do it when you=20
instruct the drive to perform the SMART self test.   I had a drive=20
appear to fail two days ago, bios said rw error on boot. Removed the=20
drive, put it in another pc and ran the SMART long test and nothing bad=20
found, but the drive listed multiple CRC endpoint errors. Endpoint=20
errors occur when the interface to the pc is bad, I knew right away what=20
it was, the SATA cable. I despise SATA cables because they don't really=20
keep a solid grip on the connection and like I thought my cables socket=20
was cracked, drive now works fine but SMART recorded those CRC errors so=20
it still test bad while the drive is fine. Now windows keeps popping up=20
the warning, drive is about to fail, back up data, so I had to silence=20
the alert.


Mark

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.