Re: read errors
- From: "Rod Speed" <rod.speed.aaa@xxxxxxxxx>
- Date: Fri, 30 May 2008 14:06:59 +1000
DonLogan <navajo@xxxxxxxxxxxxxxx> wrote:
My config is
c = 80 gig
d = 200 gig problem
both running ntfs
looked at smart from, everes,t first thing and saw no problems recognizable by me.
There are real problems tho, particularly with the second drive.
----------------------------------------------------------------------------
--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, Inc.
]------------------------------------------------------------
Version EVEREST
v2.20.405
Homepage
http://www.lavalys.com/
Report Type Quick Report
Computer P4STATION
(Digital Lathe)
Generator malcolm
Operating System Microsoft
Windows XP Professional 5.1.2600 (WinXP Retail)
Date 2008-05-29
Time 22:55
--------[ SMART
]-------------------------------------------------------------------------------------------------------
[ SAMSUNG SP0802N (S00JJ60Y558373) ]
01 Raw Read Error Rate 51 100 100 0
OK: Value is normal
03 Spin Up Time 25 100 100 6208
OK: Value is normal
04 Start/Stop Count 0 100 100 394
OK: Always passing
05 Reallocated Sector Count 11 97 97 7
OK: Value is normal
That number is getting up a bit, and since the other drive is much worse
in that area, the actual problem might be the power supply, but likely isnt.
07 Seek Error Rate 51 100 100 0
OK: Value is normal
08 Seek Time Performance 15 100 100 0
OK: Value is normal
09 Power-On Time Count 0 100 100 453320
OK: Always passing
0A Spin Retry Count 51 100 100 0
OK: Value is normal
0B Calibration Retry Count 0 100 100 0
OK: Always passing
0C Power Cycle Count 0 100 100 212
OK: Always passing
C2 Temperature 0 121 97 39
OK: Always passing
C3 Hardware ECC Recovered 0 100 100 1326755
OK: Always passing
C4 Reallocation Event Count 0 97 97 7
OK: Always passing
Thats just reporting the previous one again effectively.
C5 Current Pending Sector Count 0 100 100 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passing
C8 Write Error Rate 51 100 100 0
OK: Value is normal
C9 <vendor-specific> 51 100 100 0
OK: Value is normal
[ ST3200822A (3LJ16KS3) ]
01 Raw Read Error Rate 6 55 46 160374848
OK: Value is normal
03 Spin Up Time 0 97 96 0
OK: Always passing
04 Start/Stop Count 20 100 100 588
OK: Value is normal
05 Reallocated Sector Count 36 98 98 84
OK: Value is normal
Thats the reason you are getting so many bad files.
07 Seek Error Rate 30 87 60 561379378
OK: Value is normal
09 Power-On Time Count 0 89 89 9812
OK: Always passing
0A Spin Retry Count 97 100 100 0
OK: Value is normal
0C Power Cycle Count 20 100 100 424
OK: Value is normal
C2 Temperature 0 41 53 41
OK: Always passing
C3 Hardware ECC Recovered 0 55 46 160374848
OK: Always passing
C5 Current Pending Sector Count 0 100 100 667
OK: Always passing
Urk, that drive is clearly dying, thats an obscenely high number.
C6 Off-Line Uncorrectable Sector Count 0 100 100 667
OK: Always passing
Ditto.
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passing
C8 Write Error Rate 0 100 253 0
OK: Always passing
CA <vendor-specific> 0 100 253 0
OK: Always passing
<snipped stuff we didnt need>
sorry if formating an issue
Yeah, thats one real downside with Everest, along with the very
misleading OKs on those obscenely bad results with the bad sectors.
--------------------------
I've got a probable reproduceable app error on a specific file. This
should identify file name and can maybe map soft/bad spot(s)?
No point in doing that with so many uncorrectable bad sectors.
Just have the drive replaced under warranty.
So, good looking smart
Nope, one of the worst thats been posted here, actually.
& who knows what? I don't think it's any inboard strange interface issue.
Correct.
Gotta surface spot on the platter going bad, i think.
Nope, that doesnt happen. There's some other very fundamental
problem with the drive, likely a poor connection somewhere or a
cracked flexible connection to the heads etc.
Works good on 1,000s of i/os otherwise.
Nope, its dying.
Too bad Check-Disk didn't spit out info.
Just replace/warranty drive, but always like to use cadavers for forensics.
What ?
But smart looks ok?
Nope, one of the worst ever posted here.
DonLogan <navajo@xxxxxxxxxxxxxxx> wrote:
I have a 200 gig ide hard drive that's giving me read errors.
I write lots of files, daily, to the drive then use other
applications to read the files. The read applications are hiccuping
with their various errors.
I run xp pro so I ran Properties-Tools-Error-Checking. Took about 24
hours and seemed to be correcting but never gave me an analysis or
report. Now new files are also erroring.
I'd like to run a repair utility, free?, to correct problems.
Ideally i'd like to keep the existing files but not absolutely
necessary.
Would appreciate recommendations.
thanks
.
- Follow-Ups:
- Re: read errors (rich text)
- From: Squeeze
- Re: read errors (rich text)
- Prev by Date: Re: Write-protecting a flash drive
- Next by Date: Re: Write-protecting a flash drive
- Previous by thread: Re: read errors
- Next by thread: Re: read errors (rich text)
- Index(es):
Relevant Pages
|
