<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [ale] Disk testing app wanted</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>OK - I'll give those various suggestions a shot.<BR>
<BR>
Thanks to all who replied.<BR>
<BR>
- Mills<BR>
<BR>
-----Original Message-----<BR>
From: rs@ale.spam.futz.org [<A HREF="mailto:rs@ale.spam.futz.org">mailto:rs@ale.spam.futz.org</A>]<BR>
Sent: Wed 8/19/2009 1:19 PM<BR>
To: Atlanta Linux Enthusiasts - Yes! We run Linux!<BR>
Cc: Mills John M-NPHW64<BR>
Subject: Re: [ale] Disk testing app wanted<BR>
<BR>
>Is there a simple read/write test or script I can turn loose on a suspect SATA drive and let it run? There's no data on the disk I care to preserve.<BR>
<BR>
Whenever I get a new disk, I do the following:<BR>
<BR>
- smartctl -t short /dev/sdX (~ 2 minutes)<BR>
- smartctl -t long /dev/sdX (1TB drive, ~ 240 minutes)<BR>
- mke2fs -c -c /dev/sdX1 (1TB drive, 24+ hours)<BR>
<BR>
If all those pass, then I re-partition the drive like I want and put it into<BR>
service. I'm actually on that 3rd step for 2 1TB drives that arrived<BR>
yesterday. And yes, I've had new drives fail these tests. Sometimes the 3rd<BR>
test will fix a drive failing a selftest, as writing to a bad sector causes it<BR>
to be remapped...<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>