Is my 500GB Seagate faulty?

Associate
Joined
16 Nov 2006
Posts
365
Hi guys,

Turned on my PC the other day to find it wouldn't boot, went into bios and found it had switched itself to trying to boot from my data drive instead of my raptor raid. Switched it back, started to boot and then came up with the scandisk of drive E (my data drive). Found a few corrupt ntfs entries and continued into Windows. I checked the event log and the day before it had recorded a load of page errors on drive E at the same time as I was doing a lot of IO on the system. My data drive is a Seagate ST3500630AS. I've got another one which is for backups and in a removable caddy so I immediately performed a backup of drive E. All of the files copied across fine except for the files being worked on at the time of the page errors the previous day.

After I backed up the drive I downloaded the latest version of Seagates drive testing CD and ran a full diagnostics:

Seagate DiagATA Quick Test Result: Passed
Timer Resolution: 0.000122
Short Test Begin: 26-Jan-2007 08:09:54
Cable Test - 0 Errors
Buffer Test - 0 Errors
Identify Data
Model Number: ST3500630AS
Serial Number: *
Firmware Revision: 3.AAC
Default CHS: 16383-16-63
Current CHS: 16383-16-63
Current Capacity: 16514064 Sectors
Total Capacity: 976773168 Sectors
ID Method: Unknown
SMART Check: Passed
DST Poll Time = 60 seconds
DST - Passed
PIO/DMA Data Compare
Total Bytes = 21628928
Estimated PIO Transfer Rates
Min: 2.14MB/s Max: 3.03MB/s Avg: 2.73MB/s
Estimated DMA Transfer Rates
Min: 247.08MB/s Max: 329.44MB/s Avg: 262.48MB/s
SMART Check: Passed
Short Test Passed: 26-Jan-2007 08:11:36

ATA Full Test Result: Failed



Results from Seagate's DiagATA/SCSI:
-----------------------------------------------------------------

DIAGATA.EXE Version 3.08.50629ML
Copyright (c) 2002-2005 by Seagate Technology LLC. All rights reserved.

-----------------------------------------------------------------
Timer Resolution: 0.000122
Long Test Begin: 26-Jan-2007 08:11:37
Cable Test - 0 Errors
Buffer Test - 0 Errors
Identify Data
Model Number: ST3500630AS
Serial Number: *
Firmware Revision: 3.AAC
Default CHS: 16383-16-63
Current CHS: 16383-16-63
Current Capacity: 16514064 Sectors
Total Capacity: 976773168 Sectors
ID Method: Unknown
SMART Check: Passed
Full Scan (0 to 976773168) - Errors
---------------------------
|LBA |Error Register|
---------------------------
|392191020 |00h |
|392191021 |00h |
|392191022 |00h |
|392191023 |00h |
......
|392191078 |00h |
|392191079 |00h |
---------------------------
Long Test Failed: 26-Jan-2007 10:25:09

-----------------------------------------------------------------
End results from Seagate's DiagATA/SCSI

The Following Sectors MAY be damaged
------------------------------------
LBA: 392191020
STATUS: Write-reallocation SKIPPED
USAGE: Not Resolved

LBA: 392191021
STATUS: Write-reallocation SKIPPED
USAGE: Not Resolved
....
LBA: 392191079
STATUS: Write-reallocation SKIPPED
USAGE: Not Resolved



Bugger I thought, I'll have to return the drive. Figured I'd zero the drive using a drive cleaning CD I had which I did. Then I thought I'd test the drive again, this time it passed! Thought maybe it was because it didn't have a partition so I created an ntfs partition in Windows with a full format (no errors reported) and then bunged a load of data on it (about 50% full). Another drive test and it still passes:

Results from Seagate's DiagATA/SCSI:
-----------------------------------------------------------------

DIAGATA.EXE Version 3.08.50629ML
Copyright (c) 2002-2005 by Seagate Technology LLC. All rights reserved.

-----------------------------------------------------------------
Timer Resolution: 0.000122
Short Test Begin: 27-Jan-2007 16:05:12
Cable Test - 0 Errors
Buffer Test - 0 Errors
Identify Data
Model Number: ST3500630AS
Serial Number: *
Firmware Revision: 3.AAC
Default CHS: 16383-16-63
Current CHS: 16383-16-63
Current Capacity: 16514064 Sectors
Total Capacity: 976773168 Sectors
ID Method: Unknown
SMART Check: Passed
DST Poll Time = 60 seconds
DST - Passed
PIO/DMA Data Compare
Total Bytes = 21508096
Estimated PIO Transfer Rates
Min: 1.99MB/s Max: 3.04MB/s Avg: 2.75MB/s
Estimated DMA Transfer Rates
Min: 247.08MB/s Max: 494.16MB/s Avg: 262.57MB/s
SMART Check: Passed
Short Test Passed: 27-Jan-2007 16:06:54


-----------------------------------------------------------------
End results from Seagate's DiagATA/SCSI

ATA Full Test Result: Passed



Results from Seagate's DiagATA/SCSI:
-----------------------------------------------------------------

DIAGATA.EXE Version 3.08.50629ML
Copyright (c) 2002-2005 by Seagate Technology LLC. All rights reserved.

-----------------------------------------------------------------
Timer Resolution: 0.000122
Long Test Begin: 27-Jan-2007 16:06:55
Cable Test - 0 Errors
Buffer Test - 0 Errors
Identify Data
Model Number: ST3500630AS
Serial Number: *
Firmware Revision: 3.AAC
Default CHS: 16383-16-63
Current CHS: 16383-16-63
Current Capacity: 16514064 Sectors
Total Capacity: 976773168 Sectors
ID Method: Unknown
SMART Check: Passed
Full Scan (0 to 976773168) - Passed
Elapsed Time: 2.17 Hours
Estimated Internal Transfer Rates
Min: 7.74Mb/s Max: 8538.32Mb/s Avg: 537.49Mb/s
PIO/DMA Data Compare
Total Bytes = 28999680
Estimated PIO Transfer Rates
Min: 2.55MB/s Max: 3.18MB/s Avg: 3.14MB/s
Estimated DMA Transfer Rates
Min: 246.94MB/s Max: 329.26MB/s Avg: 261.08MB/s
Long Test Passed: 27-Jan-2007 18:17:22

-----------------------------------------------------------------
End results from Seagate's DiagATA/SCSI

File Structure Test Result:

******************************************

Any ideas guys, is my drive going faulty? I've since swapped the drives over (the dodgy one above is now the removable one) and changed the sata cable. I think maybe its a controller problem but I had the same thing happen a few months back (again when performing heavy IO) and put the drive on the other controller on my board then (it was on Marvell and now its on Intel).

Suppose it could be an overclocking issue but the PCI bus is set to 33MHz in the bios and I don't get any memory errors with memtest or other errors with Otheos. Besides, it isn't heavily overclocked:

c2d e6700 running at 3.4GHz
4GB Ram (Geil ultra low latency) - only using 3GB at present because of 32 bit XP.
Asus P5W64 WS Pro
2x Raptor 150GB's in Raid 0 array on Intel MB controller
1x Seagate 500GB on Intel MB controller
1x Seagate 500GB removable on Marvell MB controller

I've checked the controller drivers and they're the most recent ones on the Asus site. I haven't had any problems with my Raptors which are using the same controller.

Other than performing a Windows ScanDisk on the drive, which I'll do later today, I'm at a bit of a loss at what to try next. Any ideas?

Sorry for the long post but I thought I'd post as much info as possible.

Cheers.
 
Problem is it can take a month or more to find out. Suppose I could try really stressing it deliberately to see if it can cope.

A full scandisk of the drive didn't find any errors either.
 
Back
Top Bottom