Harddrive Failure - but tech says it's fine

My harddrive recently failed, and I lost alot of data. I downloaded seagates' tool and ran a scandisk. Both tools said drive is failing and Smart errors were triggered.

I tested the other internal drive, and it was perfect.

the drive is less than a month old so I took the drive back. The technition said he ran the same diagnostics tools and got no errors. They said that they will likely have to return the drive to me (possibly add a dignostics fee on top).

I am absolutely not going to put a drive that's failed once, back into my PC. That's insanity.

2 questions...

Is it possible that this is caused by motherboard sata controller?? remember the drive I use now is perfect.

If it is a bad drive (which it almost certainly is), how do i convince the techs that they're wrong?


diagnostic results below
--------------------------------------








seagate's tool


Drive Self Test DST
===================

Run: 11/23/2005 11:59:08 AM

Secondary IDE Channel : ST3120827AS
Model: ST3120827AS
Serial Number: 4MT0N3GX 4MT0N3GX
Capacity: 120.03 GB
Test result: Self-test routine completed with a S.M.A.R.T. alert error!

The Drive Self-Test has determined that the drive may have one or more failing sectors. Please run SeaTools Desktop for additional information about this problem.
Any drive reporting a S.M.A.R.T. error should be considered likely to fail at any time. You should back up your data from any such drive as soon as possible. Contact your computer or hard drive vendor to obtain return information.

File System Check
===================

Results for volume K: (NTFS)

Volume Label:
Volume Size: 20.97 GB
The file system contains errors that need to be repaired.

chkdsk log
------------------------------------

Checking file system on F:
The type of the file system is NTFS.
Volume label is Program Files.

A disk check has been scheduled.
Windows will now check the disk.
Read failure with status 0xc000009c at offset 0x5dc9ae000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x5dc9ae000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x5dc9ae000 for 0x1000 bytes.
The multi-sector header signature for VCN 0x1 of index $I30
in file 0x1417 is incorrect.
78 01 07 00 78 01 07 00 8f 36 4a 09 00 00 00 00 x...x....6J.....
00 00 00 00 00 00 00 00 28 00 00 00 f8 08 00 00 ........(.......
Correcting error in index $I30 for file 5143.
The index bitmap $I30 in file 0x1417 is incorrect.
Correcting error in index $I30 for file 5143.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 0c 00 00 00 00 00 00 00 ................
bf 0d 4a 00 00 00 00 00 0d 00 00 00 00 00 00 00 ..J.............
Sorting index $I30 in file 5143.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file mmcl70u.dll (12425) into directory file 5143.
Recovering orphaned file mmcp70.dll (12426) into directory file 5143.
Recovering orphaned file mmcr70.dll (12427) into directory file 5143.
Recovering orphaned file PSAPI.DLL (12433) into directory file 5143.
Recovering orphaned file ssleay32.dll (12436) into directory file 5143.
Recovering orphaned file unicows.dll (12437) into directory file 5143.
Recovering orphaned file zlib.dll (12439) into directory file 5143.
Recovering orphaned file Samples (12539) into directory file 5143.
Recovering orphaned file MMxpt.dll (12814) into directory file 5143.
Recovering orphaned file MMXPTR~1.DLL (12815) into directory file 5143.
Recovering orphaned file MMxptResources.dll (12815) into directory file 5143.
Recovering orphaned file NetIO.dll (12816) into directory file 5143.
Recovering orphaned file NetIOFTP.dll (12817) into directory file 5143.
Recovering orphaned file NETIOS~1.DLL (12818) into directory file 5143.
Recovering orphaned file NetIOSFTP.dll (12818) into directory file 5143.
Recovering orphaned file ReadMe.htm (12819) into directory file 5143.
Recovering orphaned file Register.htm (12820) into directory file 5143.
Recovering orphaned file XERCES~1.DLL (12821) into directory file 5143.
Recovering orphaned file xerces-c_1_7.dll (12821) into directory file 5143.
Cleaning up 17 unused index entries from index $SII of file 0x9.
Cleaning up 17 unused index entries from index $SDH of file 0x9.
Cleaning up 17 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

40957685 KB total disk space.
6551116 KB in 42973 files.
16980 KB in 2178 indexes.
4 KB in bad sectors.
112393 KB in use by the system.
65536 KB occupied by the log file.
34277192 KB available on disk.

4096 bytes in each allocation unit.
10239421 total allocation units on disk.
8569298 allocation units available on disk.

 

Hi ,
this itself saying that their is a BAD cluster on it :

how ever your system has some files missing tooo

Regards

 

If the drive is still under warranty and it has bad clusters/sectors, then you are entitled to a replacement.

The cluster has been marked by chkdsk as bad. Maybe the tech has not looked for marked bad clusters.

Send your information to the tech. If he/she does not "understand" that there is a bad cluster, ask if the information can be looked at by a Seagate tech (or a senior Seagate tech if one you are speaking about happens to be a Seagate tech).

Matt

 

Hi,
As suggested it has BAD Cluster and if its in Warranty period you can give it back to supplier for replacment and if he refuse show and send a test report you have along with the HDD.


Regards