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
DonLogan wrote in news:stbu34havvcgk1cpedbbo9a44ue6e3rin3@4ax.com
> 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
Previously DonLogan <navajo@neonfeather.com> 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
First, it is very unliekely that you can repair the drive, if indeed
it is the source of the problems. Modern drives that give lots of read
errors are dying in allmost all cases.
Second, get a SMART utility and post the SMART status here.
Nothing else allows disgnostics with reasonable effort.
> 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.
That wont help if the drive is dying.
> Ideally i'd like to keep the existing files but not absolutely necessary.
> Would appreciate recommendations.
Have the drive replaced under warranty if the SMART report shows its dying.
--------[ 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
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)?
So, good looking smart & who knows what? I don't think it's any
inboard strange interface issue. Gotta surface spot on the platter
going bad, i think. Works good on 1,000s of i/os otherwise.
Too bad Check-Disk didn't spit out info.
Just replace/warranty drive, but always like to use cadavers for
forensics. But smart looks ok?
thanks
DonLogan <navajo@neonfeather.com> 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
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@neonfeather.com> 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
Attribute 01 is very low. In addition you already have 84 reallocated
sectors and 667 sectors the dive cannot read that will likely
be reallocated on the bnext write. Also a lot of sectors are marginal
(attribute C3) and can only be read using ECC. This may be an
external problem as the seek error rate (07) ia also pretty baed.
A bad PSU or strong vibration can do this occasionally. It may also
be a sign of the read-amplifier dying, as it is needed for positioning.
Damaged drive heads are also possible.
Anyways: Make a backup NOW. This drive is very likely dying. You will
loose more data and it can die catastrophically at any moment.
> 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)?
Modern drives do not have soft/bad spots anymore. This type
of indicates bad heads or electronics, i.e. impeding complete
drive failure.
> So, good looking smart & who knows what? I don't think it's any
> inboard strange interface issue. Gotta surface spot on the platter
> going bad, i think. Works good on 1,000s of i/os otherwise.
It is not an interface issue, the ATA error counts are normal
and very low or zero.
> Too bad Check-Disk didn't spit out info.
Checkdisk works on filesystem level. It cannot deal with this.
> Just replace/warranty drive, but always like to use cadavers for
> forensics. But smart looks ok?
No, it looks pretty bad. Dont take any stock in the thresholds.
HDD manufacturers set these often far too high.
Arno Wagner wrote in news:6a92ucF35f85nU1@mid.individual.net
> Previously DonLogan <navajo@neonfeather.com> 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
>
> First, it is very unliekely that you can repair the drive, if indeed
> it is the source of the problems.
> Modern drives that give lots of read
> errors are dying in allmost all cases.
Pity about those cases of bad power supply, Babblebot.
Those drives are not dying, they just show the signs
of a dying power supply or a bad supply of power.
>
> Second, get a SMART utility and post the SMART status here.
> Nothing else allows disgnostics with reasonable effort.
Arno Wagner wrote in news:6aa4h1F3675j3U1@mid.individual.net
> Previously DonLogan <navajo@neonfeather.com> 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.
>
> The Seagate Drive has a serious problem:
>
> > [ ST3200822A (3LJ16KS3) ]
>
>> 01 Raw Read Error Rate 6 55 46 160374848 OK: Value is normal
>> C3 Hardware ECC Recovered 0 55 46 160374848 OK: Always passing
>> 05 Reallocated Sector Count 36 98 98 84 OK: Value is normal
>> 07 Seek Error Rate 30 87 60 561379378 OK: Always passing
>> C5 Current Pending Sector Count 0 100 100 667 OK: Always passing
>> C6 Off-Line Uncorrectable Sector Count 0 100 100 667 OK: Always passing
>
> Attribute 01 is very low.
You mean high, don't you, Babblebot?
Oh well, that's what you get when you are wake all night.
> In addition you already have 84 reallocated sectors and 667
> sectors the dive cannot read that will likely be reallocated on
> the bnext write.
> Also
Also, Babblebot?
> a lot of sectors are marginal (attribute C3) and can only be read using ECC.
Those are the same ones as in att. 01, babblebot.
C3 a sub-specification of att. 01.
> This may be an external problem as the seek error rate (07) ia also pretty
> baed. A bad PSU or strong vibration can do this occasionally. It may also
> be a sign of the read-amplifier dying, as it is needed for positioning.
> Damaged drive heads are also possible.
The bad sector count didn't even make a dent in the normalized values.
> Anyways: Make a backup NOW.
What makes you think he hasn't got one, Babblebot?
> This drive is very likely dying.
You have to excuse the babblebot, it has very short memory:
"This may be an external problem ...."
> You will loose more data and it can die catastrophically at any moment.
So can any drive at any moment, Babblebot.
So what about the Samsung, Babblebot, it has bad sectors too.
But those bad sectors are fine, huh.
At least they made a dent in the normalized values.
>
> > 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)?
> Modern drives do not have soft/bad spots anymore.
Yep, very short memory. So what are attributes 05 and C5 for, Babblebot?
> This type of indicates bad heads or electronics, i.e. impeding complete
> drive failure.
Very, very short memory. "This may be an external problem ...."
>
> > So, good looking smart & who knows what? I don't think it's any
> > inboard strange interface issue. Gotta surface spot on the platter
> > going bad, i think. Works good on 1,000s of i/os otherwise.
> It is not an interface issue, the ATA error counts
Which ones, Babblebot?
> are normal and very low or zero.
>
> > Too bad Check-Disk didn't spit out info.
>
> Checkdisk works on filesystem level. It cannot deal with this.
What, checkdisk doesn't have a surface scan, Babblebot?
>
> > Just replace/warranty drive, but always like to use cadavers for
> > forensics. But smart looks ok?
>
> No, it looks pretty bad. Dont take any stock in the thresholds.
> HDD manufacturers set these often far too high.
Yes, obviously harddrive manufacturers have no idea how to make
harddrives, Babblebot.
Rod Speed wrote in news:6a9crlF35nejbU1@mid.individual.net
> DonLogan <navajo@neonfeather.com> 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
Nope. Those are history. It's the pending ones that cause the bad files.
And it's those that were found during a drive internal scan so may not be in any files at all.
>
> > 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.
Nonsense. Maden't even a dent in the normalized values.
There are other attributes with values that *did* make a *considerable* dent in the normalized values.
The formatting looks fine to me, once you correct the stupid cut&paste.
> along with the very misleading OKs on those
> obscenely
Oh really.
> 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.
What makes you think they are "uncorrectable bad sectors".
They are 'uncorrectable bad reads' the underlying sectors
themselves may be fine. Are probably fine.
>
> 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.
Not by itself, usually.
> There's some other very fundamental problem with the drive, likely a poor
> connection somewhere or a cracked flexible connection to the heads etc.
Yeah, and it is affecting the other drive too. Very good, Rodbots.
>
> > Works good on 1,000s of i/os otherwise.
> Nope, its dying.
Very good, Rodbots, call him a liar.
>
> > 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?
Nice troll. A bit old in the tooth now.
>
> Nope, one of the worst ever posted here.
>
>
> > DonLogan <navajo@neonfeather.com> 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
read errors 
Linear Mode
