Hi,

I have two Maxtor HDDs that started to produce errors a few weeks ago
after they overheated (I think).

The disks were in use commercially, and have since been swapped out but
I thought I'd try to resurrect these.

I've run all the tests provided with the Maxtor PowerMax and all pass,
including the tests that when passed means the disks are 'certified
error free'. But I'm still not sure if they're working correctly and
am hesitant to put anything important on them. All tests pass, but if
I try to run a full low level format from within PowerMax it fails
almost immediately saying there's an error.

Curiously though, I am able to completely low level format the disks if
I use the low level format of my controller card, which seems to
complete without error.

Any thoughts on what's going on here. I don't understand why
everything seems fine, except for the low level format in PowerMax, and
then only in PowerMax.

Any thoughts would be greatly appreciated.

david_moss1@hotmail.com wrote

PowerMax can be rather flakey, so that may not mean much.

Those just tell the drive to do that and dont have any
real error checking, so that doesnt mean a lot either.

Likely just PowerMax having a brain fart when doing a LLF.

Post the Everest SMART data for the drives.
http://www.majorgeeks.com/download.php?det=4181

Run a full SMART test using smartctl from a linux like knoppix.

<david_moss1@hotmail.com> wrote in message news:1156695688.000228.255990@m79g2000cwm.googlegr oups.com
So may be your next if you don't solve what's causing this.

'the' tests?

Why don't you tell us by telling us what it fails with.

Never post wide listings through Google.

threshold cur low

Good!

High!

Odd attribute values.

Very high.

"Arno Wagner" <me@privacy.net> wrote in message news:4ld56oF1aglsU1@individual.net
Whatever that has got to do with that LLF test failing, babblebot.

*Your* Maxtor disks, babblebot. There are 2 divisions within Maxtor.
His may well be from the other group than yours are from.

"Rod Speed" <rod.speed.aaa@gmail.com> wrote in message news:4le08kF1evtuU1@individual.net
Having fun playing with words, Roddy?

You've never seen a drive with that many reallocated sectors, ever.

But 2 drives exhibiting the same problems is too much of a coincidence.
The problem is likely external and therefor to be solved externally.

[misquoted shit removed]

Previously david_moss1@hotmail.com wrote:
Typical Maxtor issue.

I have had that with Maxtors. The SMART thresholds are set
far too optimistically on those.

Don't waste your time on those disks. They will just continue to
produce more defects. I have seen it several times with Maxtor
disks.

Arno

Thanks for the replies.

I've run the everest smart tests and the results are below.
Interestingly, the first drive failed with:

05 Reallocated Sector Count 63 61 59 1946
Pre-Failure: Imminent loss of data is being predicted

so I guess it's only fit for the bin.

The second passed all tests, but even then the same test produced:

05 Reallocated Sector Count 63 242 215 115 OK:
Value is normal

- 115 reallocated secotors? I guess that's not good either.

Is the second disk worth the effort? I guess it should be ok if it has
passed the tests?
The PowerMax LLF still fails on both disks. Could it be having an
issue working with my controller card?

Any thoughts greatly appreciated.

[ Maxtor 6Y160M0 (Y47ZRH0E) ]

03 Spin Up Time 63 252 252 3599
OK: Value is normal
04 Start/Stop Count 0 253 253 20
OK: Always passing
05 Reallocated Sector Count 63 61 59 1946
Pre-Failure: Imminent loss of data is being predicted
06 Read Channel Margin 100 253 253 0
OK: Value is normal
07 Seek Error Rate 0 253 252 0
OK: Always passing
08 Seek Time Performance 187 253 249 38537
OK: Value is normal
09 Power-On Time Count 0 251 251 45474
OK: Always passing
0A Spin Retry Count 157 252 252 0
OK: Value is normal
0B Calibration Retry Count 223 253 252 0
OK: Value is normal
0C Power Cycle Count 0 253 253 37
OK: Always passing
C0 Power-Off Retract Count 0 253 253 0
OK: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
OK: Always passing
C2 Temperature 0 253 253 52
OK: Always passing
C3 Hardware ECC Recovered 0 253 252 490
OK: Always passing
C4 Reallocation Event Count 0 248 248 5
OK: Always passing
C5 Current Pending Sector Count 0 253 251 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 253 249 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 37 35 1280
OK: Always passing
C8 Write Error Rate 0 253 252 0
OK: Always passing
C9 <vendor-specific> 0 253 247 1
OK: Always passing
CA <vendor-specific> 0 253 241 0
OK: Always passing
CB <vendor-specific> 180 253 252 0
OK: Value is normal
CC <vendor-specific> 0 253 251 0
OK: Always passing
CD <vendor-specific> 0 253 252 0
OK: Always passing
CF <vendor-specific> 0 252 252 0
OK: Always passing
D0 <vendor-specific> 0 252 252 0
OK: Always passing
D1 <vendor-specific> 0 193 193 0
OK: Always passing
63 <vendor-specific> 0 253 253 0
OK: Always passing
64 <vendor-specific> 0 253 253 0
OK: Always passing
65 <vendor-specific> 0 253 253 0
OK: Always passing


[ Maxtor 7Y250M0 (Y65LGPQE) ]

03 Spin Up Time 63 185 183 7604
OK: Value is normal
04 Start/Stop Count 0 253 253 27
OK: Always passing
05 Reallocated Sector Count 63 242 215 115
OK: Value is normal
06 Read Channel Margin 100 253 253 0
OK: Value is normal
07 Seek Error Rate 0 253 252 0
OK: Always passing
08 Seek Time Performance 187 251 248 37490
OK: Value is normal
09 Power-On Time Count 0 243 243 18497
OK: Always passing
0A Spin Retry Count 157 253 252 0
OK: Value is normal
0B Calibration Retry Count 223 253 252 0
OK: Value is normal
0C Power Cycle Count 0 253 253 52
OK: Always passing
C0 Power-Off Retract Count 0 253 253 0
OK: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
OK: Always passing
C2 Temperature 0 253 253 50
OK: Always passing
C3 Hardware ECC Recovered 0 253 252 2019
OK: Always passing
C4 Reallocation Event Count 0 1 1 309
OK: Always passing
C5 Current Pending Sector Count 0 253 226 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 1 1 268
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 8726
OK: Always passing
C8 Write Error Rate 0 253 252 0
OK: Always passing
C9 <vendor-specific> 0 253 252 0
OK: Always passing
CA <vendor-specific> 0 253 214 0
OK: Always passing
CB <vendor-specific> 180 253 251 0
OK: Value is normal
CC <vendor-specific> 0 253 248 0
OK: Always passing
CD <vendor-specific> 0 253 252 0
OK: Always passing
CF <vendor-specific> 0 253 252 0
OK: Always passing
D0 <vendor-specific> 0 253 252 0
OK: Always passing
D1 <vendor-specific> 0 196 192 0
OK: Always passing
63 <vendor-specific> 0 253 253 0
OK: Always passing
64 <vendor-specific> 0 253 253 0
OK: Always passing
65 <vendor-specific> 0 253 253 0
OK: Always passing

david_moss1@hotmail.com wrote:

Yeah, that's the problem.

Yep, that's what I'd do with it myself. I've never seen a drive
with that many reallocated sectors ever be reliable after that.

Yeah, thats not good either, tho obviously not as obscene as the other one.

Not in my opinion. You dont see that many sectors going bad for
no reason, and that reason usually indicates that the drive is dying.

Nar, the SMART is being too optimistic there, its an ex drive.

Then I'd make a warranty claim on both drives.

Nope, that wont produce reallocated sectors.

<david_moss1@hotmail.com> wrote in message news:1156629796.122312.157170@b28g2000cwb.googlegr oups.com
Since no current (and not so current) HD do support LLF (Format Track)anymore
(except IBM/Hitachi, Format Unit) there are obviously different degrees of 'LLF'.

Folkert Rienstra <see_reply-to@myweb.nl> wrote
Having fun playing with your dick, fucknert ?

Guess which pathetic little pseudokraut prat has just
got egg all over its pathetic little face, as always ?

Nope, not when they are both Maxtors.

Those dont usually produce reallocated sectors, fuckwit.

Previously david_moss1@hotmail.com wrote:
Indeed.

It depends. I have two maxtors with 100-200 reallocated sectors and
they have been running reliably for several years now. But they
never had additional defects and are very well cooled.

Not necessarily. What you can try is to operate it for some weeks
carefully. Don't put important data on it but use it. Run a long
SMART self-test every few days. If the number of defects increases,
then throw it away. If it stays constant, the disk may be fine.

Quite likely. But it does just trigger SMART self-tests. You can do
that e.g. with smartctl -t <long|short> <device> yourself. smartctl is
available under Linux and Windows.

Arno