From: Sam on
I had my power supply fail on me last week. My system rebooted a few
times then I realized what had happened. I replaced my PSU unit and XP
loaded [almost] completely. Then my system rebooted again, one more
time.

This time, the system ran chkdsk and spent a great deal of time "fixing"
the hard drive. There were no File Tructuations, I didnt record the
actual repair (is there a chkdsk log?). I see no FILE 0000 anywhere,
but my system is running now quite slow. I ran several powerful
anti-virus tools including Panda and Kaspersky, no malware was found.

I have also used SFC to repair any damaged files and then reloaded XP
SP2 but my performance is still slow. Is there a utility that can go
deeper and see what the file structure is like, if it is damaged in
anyway? Partition Magic doesn't tell me anything.

Just wondering if I have to kill my partition and reload Windows?


From: Yousuf Khan on
Sam wrote:
> I had my power supply fail on me last week. My system rebooted a few
> times then I realized what had happened. I replaced my PSU unit and XP
> loaded [almost] completely. Then my system rebooted again, one more
> time.
>
> This time, the system ran chkdsk and spent a great deal of time "fixing"
> the hard drive. There were no File Tructuations, I didnt record the
> actual repair (is there a chkdsk log?). I see no FILE 0000 anywhere,
> but my system is running now quite slow. I ran several powerful
> anti-virus tools including Panda and Kaspersky, no malware was found.

Have you tried defrag?

Yousuf Khan
From: Folkert Rienstra on
"Michael Cecil" <macecil(a)gmail.com> wrote in message news:jcCdnXqh_7scvv7YnZ2dnUVZ_v2dnZ2d(a)comcast.com
> On Tue, 21 Nov 2006 10:38:16 -0500, Yousuf Khan <bbbl67(a)yahoo.com> wrote:
> > Sam wrote:
> > > I had my power supply fail on me last week. My system rebooted a few
> > > times then I realized what had happened. I replaced my PSU unit and XP
> > > loaded [almost] completely. Then my system rebooted again, one more
> > > time.
> > >
> > > This time, the system ran chkdsk and spent a great deal of time "fixing"
> > > the hard drive. There were no File Tructuations, I didnt record the
> > > actual repair (is there a chkdsk log?). I see no FILE 0000 anywhere,
> > > but my system is running now quite slow. I ran several powerful
> > > anti-virus tools including Panda and Kaspersky, no malware was found.
> >
> > Have you tried defrag?
>
> Yes, that's EXACTLY what you should do on an error-prone drive - NOT!.
>
> I think I would first save off any crucial data such as email address
> books, etc. Next, check the SMART status of the drive and run the HDD
> manufacturer's diagnostic tools on it.

> Then, if it's not dying

Which you can't be sure of if you don't do destructive tests.

> and you're certain that the PSU you got as a replacement is sufficient and
> reputable,

> I'd just do a format and reinstall of XP.

And a restore of your data, obviously.

> You could do a repair install and possibly keep your data intact, but you'd
> potentially be leaving other damaged files on the drive.

A surface scan should catch them.


From: Yousuf Khan on
Michael Cecil wrote:
>> Have you tried defrag?
>
> Yes, that's EXACTLY what you should do on an error-prone drive - NOT!.


He hasn't said that the drive is necessarily bad. He just said his power
supply failed, and then when he replaced it, the drive came back with
errors which were fixed by chkdsk. Those sort of errors are
understandable if the computer had shutdown suddenly. It doesn't
indicate a bad drive, just a problem that occurred because of a problem
elsewhere.

Yousuf Khan
From: Rod Speed on
Yousuf Khan <bbbl67(a)yahoo.com> wrote
> Michael Cecil wrote

>>> Have you tried defrag?

>> Yes, that's EXACTLY what you should do on an error-prone drive - NOT!.

> He hasn't said that the drive is necessarily bad. He just said his power supply failed, and then
> when he replaced it, the drive came back with errors which were fixed by chkdsk. Those sort of
> errors are understandable if the computer had shutdown suddenly. It doesn't indicate a bad drive,
> just a problem that occurred because of a problem elsewhere.

Its still a stupid thing to do when there is a real possibility
of the PSU failure damaging the drive. In spades when the
slowdown is very unlikely indeed to be due to fragmentation.

Its MUCH more likely that the slowdown is due to retrying
on bads and that possibility needs to be eliminated before
doing anything as aggressive as a defrag.


 |  Next  |  Last
Pages: 1 2 3 4
Prev: DeskStar 60GXP 40GB is now 33GB ?!
Next: WD800 connector