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?

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

"Michael Cecil" <macecil@gmail.comwrote in message @comcast.com
Tue, 21 Nov 2006 10:38:16 -0500, Yousuf Khan <bbbl67@yahoo.comwrote:
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 - NT!.

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.

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

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

Yousuf Khan <bbbl67@yahoo.comwrote
Michael Cecil wrote

Have you tried defrag?

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

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.

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4shb71Fvl4s2U1@mid.individual.net
Yousuf Khan <bbbl67@yahoo.comwrote
>Michael Cecil wrote
>
Have you tried defrag?

Yes, that's EXACTLY what you should do on an error-prone drive - NT!.
>
>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.

If chkdsk found/fixed lots of errors you need to keep running it until
you get a clear run. Chkdsk does not fix all errors on one pass. If you keep
getting a small number of errors, that would suggest that the drive is
failing.
Mike.

"Yousuf Khan" <bbbl67@yahoo.comwrote in message news:456349c8$1@news.bnb-lp.com
Michael Cecil wrote:
Have you tried defrag?

Yes, that's EXACTLY what you should do on an error-prone drive - NT!.
--
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 under-
standable if the computer had shutdown suddenly. It doesn't indicate a
bad drive, just a problem that occurred because of a problem elsewhere.

Right, obviously the power supply massively fragmented the drive.

Yousuf Khan

I am running chkdisk again as I write using Partition Magic. I am
getting the same errors again while checking the Indexes (stage 2/3):
Deleting an Index Entry from $0 of file 25 (and it's still doing it
after quite some time). It finally rested deleting the same files $0 of
file 25 .Then, I got another error: "An unspecified error occurred".
Remember, this is a chkdsk through full XP, not in Dos mode but within
the CMD shell.

I think maybe I should start backing up my stuff and reformat the
partition? But, if I copy any bad files back then when I copy them back
to the reformatted drive then they may still be bad? if I do a
chkdsk of the other drive where I back the files up to then it should be
ok?

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4shb71Fvl4s2U1@mid.individual.net

: 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.

I have the log from my EVENTVIEWER. I seen that from several weeks ago
that I had some issues unknown to memakes me think if my drive is
going bad or if these errors are normal. This is my current log:

Checking file system on C:
The type of the file system is NTFS.
Volume label is MX XP.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
CHKDSK is verifying Usn Journal
Usn Journal verification completed.
122993636 KB total disk space.
72676428 KB in 170437 files.
76028 KB in 9720 indexes.
0 KB in bad sectors.
295948 KB in use by the system.
65536 KB occupied by the log file.
49945232 KB available on disk.
4096 bytes in each allocation unit.
30748409 total allocation units on disk.
12486308 allocation units available on disk.
Internal Info:
e0 4a 03 00 c9 bf 02 00 b3 35 04 00 00 00 00 00 .J5
98 28 01 00 01 00 00 00 7a 06 00 00 00 00 00 00 .(z
30 ba 1c 37 00 00 00 00 a0 66 4b 18 01 00 00 00 07fK
c0 98 0e 3f 00 00 00 00 00 00 00 00 00 00 00 00 ?
00 00 00 00 00 00 00 00 70 86 b2 aa 01 00 00 00 p
99 9e 36 00 00 00 00 00 f0 3e 07 00 c5 99 02 00 6>
00 00 00 00 00 30 d1 53 11 00 00 00 f8 25 00 00 0.S%

Sam <none@none.comwrote:
"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4shb71Fvl4s2U1@mid.individual.net
>
>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.
>
>
I have the log from my EVENTVIEWER. I seen that from several weeks
ago that I had some issues unknown to memakes me think if my
drive is going bad or if these errors are normal. This is my current
log:

Checking file system on C:
The type of the file system is NTFS.
Volume label is MX XP.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
CHKDSK is verifying Usn Journal
Usn Journal verification completed.
122993636 KB total disk space.
72676428 KB in 170437 files.
76028 KB in 9720 indexes.
0 KB in bad sectors.
295948 KB in use by the system.
65536 KB occupied by the log file.
49945232 KB available on disk.
4096 bytes in each allocation unit.
30748409 total allocation units on disk.
12486308 allocation units available on disk.
Internal Info:
e0 4a 03 00 c9 bf 02 00 b3 35 04 00 00 00 00 00 .J5
98 28 01 00 01 00 00 00 7a 06 00 00 00 00 00 00 .(z
30 ba 1c 37 00 00 00 00 a0 66 4b 18 01 00 00 00 07fK
c0 98 0e 3f 00 00 00 00 00 00 00 00 00 00 00 00 ?
00 00 00 00 00 00 00 00 70 86 b2 aa 01 00 00 00 p
99 9e 36 00 00 00 00 00 f0 3e 07 00 c5 99 02 00 6>
00 00 00 00 00 30 d1 53 11 00 00 00 f8 25 00 00 0.S%

Post the Everest SMART report for the drive.

"Sam" <none@none.comwrote in message
news:dYQ8h.346443$5R2.80291@pd7urf3no
>I am running chkdisk again as I write using Partition Magic. I am
getting the same errors again while checking the Indexes (stage 2/3):
Deleting an Index Entry from $0 of file 25 (and it's still doing it
after quite some time). It finally rested deleting the same files $0 of
file 25 .Then, I got another error: "An unspecified error occurred".
Remember, this is a chkdsk through full XP, not in Dos mode but within
the CMD shell.

I think maybe I should start backing up my stuff and reformat the
partition? But, if I copy any bad files back then when I copy them back
to the reformatted drive then they may still be bad? if I do a
chkdsk of the other drive where I back the files up to then it should be
ok?

You need to run chkdsk <drive>: /f to fix errors, or better, chkdsk
<drive>: /r to check the entire drive at boot. Chkdsk only runs in read-only
mode, which reports, but does NT fix!
Mike.

"Michael Hawes" <michael.hawes1remove@tiscali.co.ukwrote in message news:456388b6$3_4@mk-nntp-2.news.uk.tiscali.com
"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4shb71Fvl4s2U1@mid.individual.net
Yousuf Khan <bbbl67@yahoo.comwrote
Michael Cecil wrote

Have you tried defrag?

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

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.

If chkdsk found/fixed lots of errors you need to keep running it until
you get a clear run. Chkdsk does not fix all errors on one pass. If you keep
getting a small number of errors,

that would suggest that the drive is failing.

Not if the drive has badly written sectors with missing/wrong ECC.

Mike.

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4sjjqoF101vhjU1@mid.individual.net
:
: Post the Everest SMART report for the drive.
:
Thanks, will do.

"Michael Hawes" <michael.hawes1remove@tiscali.co.ukwrote in message
news:4564dcc0$1_1@
:
: : You need to run chkdsk <drive>: /f to fix errors, or better,
chkdsk
: <drive>: /r to check the entire drive at boot. Chkdsk only runs in
read-only
: mode, which reports, but does NT fix!

I ran it again, a few times. It appears to have fixed them. I also ran
it on my notebook too. I was surprised I found some errors there as
well. However, in running chkdsk 2 on my desktop where I am having
problems, chkdsk is taking a LNG time, unlike my notebook or any other
partition that I check. So, it seems that that partition is in fact
slower than what it should be.

I will take Ron's advice and run EverSMART and post my results within a
few days.

Thanks

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4sjjqoF101vhjU1@mid.individual.net
: :
: Post the Everest SMART report for the drive.
:

Boythat was fast. Here is the log:

[ EVEREST Home Edition (c) 2003-2005 Lavalys,
Inc. ]

Version EVEREST v2.20.405
Homepage
http://www.lavalys.com/
Report Type Report Wizard
Computer ECS
Generator Sam
System Microsoft Windows XP
Professional 5.1.2600 (WinXP Retail)
Date 2006-11-22
Time 20:20

[
SMART ]

[ Maxtor 6L250R0 (L598P9BG) ]

03 Spin Up Time 63 178 178 23707
K: Value is normal
04 Start/Stop Count 0 253 253 477
K: Always passing
05 Reallocated Sector Count 63 253 253 0
K: Value is normal
06 Read Channel Margin 100 253 253 0
K: Value is normal
07 Seek Error Rate 0 253 252 0
K: Always passing
08 Seek Time Performance 187 248 238 36076
K: Value is normal
09 P Time Count 0 248 248 42758
K: Always passing
0A Spin Retry Count 157 253 252 0
K: Value is normal
0B Calibration Retry Count 223 253 252 0
K: Value is normal
0C Power Cycle Count 0 252 252 473
K: Always passing
C0 P Retract Count 0 253 253 0
K: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
K: Always passing
C2 Temperature 0 32 253 33
K: Always passing
C3 Hardware ECC Recovered 0 253 252 1760
K: Always passing
C4 Reallocation Event Count 0 253 253 0
K: Always passing
C5 Current Pending Sector Count 0 253 253 0
K: Always passing
C6 Line Uncorrectable Sector Count 0 253 253 0
K: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 48594
K: Always passing
C8 Write Error Rate 0 253 252 0
K: Always passing
C9 <vendor-specific0 253 252 0
K: Always passing
CA <vendor-specific0 253 252 0
K: Always passing
CB <vendor-specific180 253 252 0
K: Value is normal
CC <vendor-specific0 253 252 0
K: Always passing
CD <vendor-specific0 253 252 0
K: Always passing
CF <vendor-specific0 253 252 0
K: Always passing
D0 <vendor-specific0 253 252 0
K: Always passing
D1 <vendor-specific0 235 235 224
K: Always passing
D2 <vendor-specific0 253 252 0
K: Always passing
D3 <vendor-specific0 253 252 0
K: Always passing
D4 <vendor-specific0 253 249 0
K: Always passing

[ WDC WD2000JB-00GVA0 (WD-WCAL81550730) ]

01 Raw Read Error Rate 51 200 200 0
K: Value is normal
03 Spin Up Time 21 123 112 6350
K: Value is normal
04 Start/Stop Count 40 99 99 1283
K: Value is normal
05 Reallocated Sector Count 140 200 200 0
K: Value is normal
07 Seek Error Rate 51 200 200 0
K: Value is normal
09 P Time Count 0 95 95 4168
K: Always passing
0A Spin Retry Count 51 100 100 0
K: Value is normal
0B Calibration Retry Count 51 100 100 0
K: Value is normal
0C Power Cycle Count 0 99 99 1234
K: Always passing
C2 Temperature 0 117 99 33
K: Always passing
C4 Reallocation Event Count 0 200 200 0
K: Always passing
C5 Current Pending Sector Count 0 200 200 0
K: Always passing
C6 Line Uncorrectable Sector Count 0 200 200 0
K: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 2
K: Always passing
C8 Write Error Rate 51 200 200 0
K: Value is normal

[ Debug -
PCI ]

B00 D00 F00: VIA VT8751(A) ProSavage P4M266(A) Chipset - System
Controller

00: 06 11 48 31 06 00 30 22 00 00 00 06 00 08 00 00
10: 08 00 00 E0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 00 00
30: 00 00 00 00 A0 00 00 00 00 00 00 00 00 00 00 00
40: 00 18 88 80 82 44 00 00 18 99 88 80 82 44 00 00
50: C8 9E C7 88 40 05 30 30 EE 00 10 20 30 30 30 30
60: 0A AA 02 20 20 D9 40 20 41 3D 32 50 44 05 00 00
70: 02 C8 00 01 31 01 50 00 01 00 00 00 00 00 00 00
80: 0F 65 00 00 00 70 00 00 03 00 10 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 02 C0 20 00 07 02 00 1F 04 03 00 00 2D 92 04 00
B0: 78 AC 10 9B 40 00 88 FE 68 00 00 00 00 00 00 80
C0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 78 38 12 00
E0: 00 00 42 1A 00 00 89 00 40 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 80 00 00 00 00 00 00 00 00 00

B00 D01 F00: VIA AGP Controller

00: 06 11 91 B0 07 01 30 22 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 F0 00 00 00
20: E0 DD E0 DF C0 CD C0 DD 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0C 00
40: 83 47 00 44 24 72 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 02 02 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

B00 D09 F00: Rockwell/Conexant SoftK56 Voice/Data/Fax/SpeakerPhone
Modem

00: 7A 12 15 20 07 01 90 02 01 00 80 07 00 20 00 00
10: 00 00 FF DF 01 EC 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 7A 12 15 20
30: 00 00 00 00 40 00 00 00 00 00 00 00 0A 01 00 00
40: 01 00 32 C8 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

B00 D0B F00: Texas Instruments TSB12LV26 HCI-Lynx IEEE1394 Host
Controller

00: 4C 10 20 80 16 01 10 02 00 10 00 0C 08 20 00 00
10: 00 F8 FE DF 00 80 FE DF 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 21 14 00 00
30: 00 00 00 00 44 00 00 00 00 00 00 00 0B 01 03 04
40: 00 00 00 00 01 00 11 40 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 21 14 00 00 00 00 01 01

B00 D10 F00: VIA VT83C572 PCI-USB Controller

00: 06 11 38 30 17 00 10 02 80 00 03 0C 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 E0 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 01 00 00
40: 40 12 03 00 00 00 00 00 00 0B 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 C2 FF 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

B00 D10 F01: VIA VT83C572 PCI-USB Controller

00: 06 11 38 30 17 00 10 02 80 00 03 0C 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 E4 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 0A 02 00 00
40: 40 12 03 00 00 00 00 00 00 0B 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 C2 FF 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

B00 D10 F02: VIA VT83C572 PCI-USB Controller

00: 06 11 38 30 17 00 10 02 80 00 03 0C 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 E8 00 00 00 00 00 00 00 00 00 00 06 11 38 30
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 03 00 00
40: 40 12 03 00 00 00 00 00 00 0B 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 C2 FF 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

B00 D10 F03: VIA USB 2.0 Enhanced Host Controller

00: 06 11 04 31 17 00 10 02 82 20 03 0C 08 20 00 00
10: 00 F7 FE DF 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 04 31
30: 00 00 00 00 80 00 00 00 00 00 00 00 0B 04 00 00
40: 00 00 03 00 00 00 00 00 A0 20 00 09 00 00 00 00
50: 00 5A 04 80 00 00 00 00 04 0B 88 88 53 88 00 00
60: 20 20 01 00 00 00 00 00 01 00 00 00 00 00 00 C0
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 01 00 C2 FF 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00

B00 D11 F00: VIA VT8233A/VT8235 PCI-ISA Bridge

00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 00 00
30: 00 00 00 00 C0 00 00 00 00 00 00 00 00 00 00 00
40: 44 00 F8 00 00 00 00 00 8C 20 00 00 44 00 08 08
50: 81 1D 09 00 00 50 5A B0 23 80 FF 00 00 00 04 08
60: 00 00 00 00 10 00 02 04 00 00 00 00 00 00 00 00
70: 06 11 00 00 00 00 00 00 00 00 00 00 20 00 00 00
80: 20 84 59 00 9A 10 00 00 01 08 00 00 00 18 00 00
90: 00 00 08 00 B0 C4 0F 00 00 42 1B 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 01 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00

B00 D11 F01: VIA VT82C571 IDE Controller

00: 06 11 71 05 07 00 90 02 06 8A 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 FC 00 00 00 00 00 00 00 00 00 00 06 11 71 05
30: 00 00 00 00 C0 00 00 00 00 00 00 00 FF 01 00 00
40: 0B F2 09 35 18 1C C0 00 11 20 20 20 FF 00 B6 B6
50: 07 E6 F1 17 0C 00 00 00 A8 A8 A8 A8 00 00 00 00
60: 00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00
70: 02 01 00 00 00 00 00 00 02 01 00 00 00 00 00 00
80: F8 DE B3 03 00 00 00 00 08 95 BA 03 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 06 00 71 05 06 11 71 05 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 07 00 00 00 00 00 00 00 00 00

B00 D11 F05: VIA AC'97 Enhanced Audio Controller

00: 06 11 59 30 01 00 10 02 50 00 01 04 00 00 00 00
10: 01 DC 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 83 0A
30: 00 00 00 00 C0 00 00 00 00 00 00 00 05 03 00 00
40: 01 CC 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
D0: 01 00 02 06 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

B00 D12 F00: VIA 10/100 Fast Ethernet Adapter

00: 06 11 65 30 17 01 10 02 74 00 00 02 08 20 00 00
10: 01 D8 00 00 00 F6 FE DF 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 02 01
30: 00 00 00 00 40 00 00 00 00 00 00 00 05 01 03 08
40: 01 00 02 FE 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 80 04 00 00 00 00 00 00 00 00 00 00 00 02
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

B01 D00 F00: nVIDIA GeForce FX 5200 Video Adapter

00: DE 10 22 03 07 00 B0 02 A1 00 00 03 00 F8 00 00
10: 00 00 00 DE 08 00 00 D0 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 05 01
40: 00 00 00 00 02 00 30 00 17 02 00 1F 04 03 00 1F
50: 01 00 00 00 01 00 00 00 CE D6 23 00 0F 00 00 00
60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[ Debug - Video
BIS ]

C000:0000 U.z.K7400.L.w.VIDE IBM VGA
Compatible03/26/03
C000:0040 ?.0~.
"PMIDl.o
C000:0080 3NV&x.
4PNF.E.E
C000:00C0 ^RxX.`0W:p.p.q
qPqPq.p
C000:0100
bmph.Zh
C000:0140
Jf.~
C000:0180

C000:01C0
`m`m`m`m`m`m
C000:0200
`m`m`m
C000:0240
`m`m`
C000:0280 qPCIR"zGeForce FX 5200
BIS
C000:02C0
4.34.20.18.
C000:0300 07 Copyright (C) 1996-2003 NVIDIA
Corp
C000:0340 Board -
p162-1nz
C000:0380 .Chip Rev
`a.
C000:03C0
/men.Z.$.qt.N.Yxz.f`:p

The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.

I just ran Hardware Tune on the C Partition and I am getting 2.5 MB/sec
while on my other Maxtor Partition I am getting around 56 MB/sec. My
DMA is enabled to 5 on my Primary IDE channel. Something is definitely
not right.

"Sam" <none@none.comwrote in message news:jUa9h.350219$5R2.203615@pd7urf3no
I just ran Hardware Tune on the C Partition and I am getting 2.5 MB/sec
while on my other Maxtor Partition I am getting around 56 MB/sec.

So your C: partiton on the Maxtor is slow but your D: on the Maxtor is fine.
Yeah, that makes sense.

My DMA is enabled to 5 on my Primary IDE channel. Something is definitely
not right.

"Sam" <none@none.comwrote in message news:fl99h.347012$1T2.302400@pd7urf2no
"Rod Speed" <rod.speed.aaa@gmail.comwrote in message news:4sjjqoF101vhjU1@mid.individual.net

Post the Everest SMART report for the drive.

--
Boythat was fast.

Yeah, and as usual you broke it as you couldn't be bothered to setup
your newclient to show it properly.

Here is the log:

[ EVEREST Home Edition (c) 2003-2005 Lavalys, Inc. ]

Version EVEREST v2.20.405 Homepage http://www.lavalys.com/
Report Type Report Wizard
Computer ECS
Generator Sam
System Microsoft Windows XP Professional 5.1.2600 (WinXP Retail)
Date 2006-11-22
Time 20:20
--
[ SMART ]

[ Maxtor 6L250R0 (L598P9BG) ]

03 Spin Up Time 63 178 178 23707 K: Value is normal
04 Start/Stop Count 0 253 253 477 K: Always passing
05 Reallocated Sector Count 63 253 253 0 K: Value is normal
06 Read Channel Margin 100 253 253 0 K: Value is normal
07 Seek Error Rate 0 253 252 0 K: Always passing
08 Seek Time Performance 187 248 238 36076 K: Value is normal
09 P Time Count 0 248 248 42758 K: Always passing
0A Spin Retry Count 157 253 252 0 K: Value is normal
0B Calibration Retry Count 223 253 252 0 K: Value is normal
0C Power Cycle Count 0 252 252 473 K: Always passing
C0 P Retract Count 0 253 253 0 K: Always passing
C1 Load/Unload Cycle Count 0 253 253 0 K: Always passing
C2 Temperature 0 32 253 33 K: Always passing
C3 Hardware ECC Recovered 0 253 252 1760 K: Always passing
C4 Reallocation Event Count 0 253 253 0 K: Always passing
C5 Current Pending Sector Count 0 253 253 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 253 253 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 48594 K: Always passing
C8 Write Error Rate 0 253 252 0 K: Always passing
C9 <vendor-specific0 253 252 0 K: Always passing
CA <vendor-specific0 253 252 0 K: Always passing
CB <vendor-specific180 253 252 0 K: Value is normal
CC <vendor-specific0 253 252 0 K: Always passing
CD <vendor-specific0 253 252 0 K: Always passing
CF <vendor-specific0 253 252 0 K: Always passing
D0 <vendor-specific0 253 252 0 K: Always passing
D1 <vendor-specific0 235 235 224 K: Always passing
D2 <vendor-specific0 253 252 0 K: Always passing
D3 <vendor-specific0 253 252 0 K: Always passing
D4 <vendor-specific0 253 249 0 K: Always passing

Apart from the somewhat high (at least the drive thinks it is) CRC error rate, it is fine.
There are also some ECC recovered errors but that didn't even make a dent in the normalized values.
You could check it's power supply and data cable.

[ WDC WD2000JB-00GVA0 (WD-WCAL81550730) ]

01 Raw Read Error Rate 51 200 200 0 K: Value is normal
03 Spin Up Time 21 123 112 6350 K: Value is normal
04 Start/Stop Count 40 99 99 1283 K: Value is normal
05 Reallocated Sector Count 140 200 200 0 K: Value is normal
07 Seek Error Rate 51 200 200 0 K: Value is normal
09 P Time Count 0 95 95 4168 K: Always passing
0A Spin Retry Count 51 100 100 0 K: Value is normal
0B Calibration Retry Count 51 100 100 0 K: Value is normal
0C Power Cycle Count 0 99 99 1234 K: Always passing
C2 Temperature 0 117 99 33 K: Always passing
C4 Reallocation Event Count 0 200 200 0 K: Always passing
C5 Current Pending Sector Count 0 200 200 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 200 200 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 2 K: Always passing
C8 Write Error Rate 51 200 200 0 K: Value is normal

This one is absolutely fine according to S.M.A.R.T.

[snip rest of bull****]

"Folkert Rienstra" <see_reply-to@myweb.nlwrote in message
news:4565c547$0$97249$892e7fe2@
: "Sam" <none@none.comwrote in message
news:jUa9h.350219$5R2.203615@pd7urf3no
: I just ran Hardware Tune on the C Partition and I am getting 2.5
MB/sec
: while on my other Maxtor Partition I am getting around 56 MB/sec.
:
: So your C: partiton on the Maxtor is slow but your D: on the Maxtor is
fine.
: Yeah, that makes sense.
:
: My DMA is enabled to 5 on my Primary IDE channel. Something is
definitely
: not right.

My mistakeI thought the HD Utility was looking at the other
partition, but in fact it was looking at the other drive. So, N My
Maxtor is 2.5 MB/s while my WD is 56 MB/s.

Does this make sense now?

"Cl.M" <retour@contactprospect.comwrote in message
news:4565d50e$0$509$426a74cc@news.free.fr
: "Sam" <none@none.coma dans le message de news:
: Ziv8h.343523$5R2.314957@pd7urf3no
:
: Just wondering if I have to kill my partition and reload Windows?
:
: Have you first tried "chkdsk c: /r"? It will detect and fence off bad
: sectors if there are any.
:
: --
: clmasse on free F-country
: Free technical support at : http://www.protonic.com/
:
:

I ran everything including Maxtor's Utility PowerMax in both both quick
and extended test mode. My Maxtor passed everthing.

Sam <none@none.comwrote
Rod Speed <rod.speed.aaa@gmail.comwrote

>Post the Everest SMART report for the drive.
>

Boythat was fast. Here is the log:

The drive is fine, the cable should be replaced. More comments interleaved below.

[ EVEREST Home Edition (c) 2003-2005 Lavalys,
Inc. ]

Version EVEREST v2.20.405
Homepage
http://www.lavalys.com/
Report Type Report Wizard
Computer ECS
Generator Sam
System Microsoft Windows XP
Professional 5.1.2600 (WinXP Retail)
Date 2006-11-22
Time 20:20
--
[
SMART
]

[ Maxtor 6L250R0 (L598P9BG) ]

03 Spin Up Time 63 178 178 23707
K: Value is normal
04 Start/Stop Count 0 253 253 477
K: Always passing
05 Reallocated Sector Count 63 253 253 0
K: Value is normal
06 Read Channel Margin 100 253 253 0
K: Value is normal
07 Seek Error Rate 0 253 252 0
K: Always passing
08 Seek Time Performance 187 248 238 36076
K: Value is normal
09 P Time Count 0 248 248 42758
K: Always passing
0A Spin Retry Count 157 253 252 0
K: Value is normal
0B Calibration Retry Count 223 253 252 0
K: Value is normal
0C Power Cycle Count 0 252 252 473
K: Always passing
C0 P Retract Count 0 253 253 0
K: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
K: Always passing
C2 Temperature 0 32 253 33
K: Always passing
C3 Hardware ECC Recovered 0 253 252 1760
K: Always passing
C4 Reallocation Event Count 0 253 253 0
K: Always passing
C5 Current Pending Sector Count 0 253 253 0
K: Always passing
C6 Line Uncorrectable Sector Count 0 253 253 0
K: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 48594
K: Always passing

Thats a high level of errors on the cable to the drive.

Try replacing the cable and dont use round cables,
use proper flat 80 wire ribbon cables.

Check that the S is using the DMA for the drive, it may well have
turned that off with that high an error rate. Check in the Device Manager.

C8 Write Error Rate 0 253 252 0
K: Always passing
C9 <vendor-specific0 253 252 0
K: Always passing
CA <vendor-specific0 253 252 0
K: Always passing
CB <vendor-specific180 253 252 0
K: Value is normal
CC <vendor-specific0 253 252 0
K: Always passing
CD <vendor-specific0 253 252 0
K: Always passing
CF <vendor-specific0 253 252 0
K: Always passing
D0 <vendor-specific0 253 252 0
K: Always passing
D1 <vendor-specific0 235 235 224
K: Always passing
D2 <vendor-specific0 253 252 0
K: Always passing
D3 <vendor-specific0 253 252 0
K: Always passing
D4 <vendor-specific0 253 249 0
K: Always passing

[ WDC WD2000JB-00GVA0 (WD-WCAL81550730) ]

01 Raw Read Error Rate 51 200 200 0
K: Value is normal
03 Spin Up Time 21 123 112 6350
K: Value is normal
04 Start/Stop Count 40 99 99 1283
K: Value is normal
05 Reallocated Sector Count 140 200 200 0
K: Value is normal
07 Seek Error Rate 51 200 200 0
K: Value is normal
09 P Time Count 0 95 95 4168
K: Always passing
0A Spin Retry Count 51 100 100 0
K: Value is normal
0B Calibration Retry Count 51 100 100 0
K: Value is normal
0C Power Cycle Count 0 99 99 1234
K: Always passing
C2 Temperature 0 117 99 33
K: Always passing
C4 Reallocation Event Count 0 200 200 0
K: Always passing
C5 Current Pending Sector Count 0 200 200 0
K: Always passing
C6 Line Uncorrectable Sector Count 0 200 200 0
K: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 2
K: Always passing
C8 Write Error Rate 51 200 200 0
K: Value is normal

Sam <none@none.comwrote:

I just ran Hardware Tune on the C Partition and I am getting 2.5 MB/sec
while on my other Maxtor Partition I am getting around 56 MB/sec.

Looks like the S has turned the DMA off on
the drive with the high CRC error rate on the cable.

My DMA is enabled to 5 on my Primary IDE channel.

Where are you getting that from exactly ?

Check that DMA is being used in the Device Manager.

Something is definitely not right.

Yeah, looks like you have a bad cable and DMA has been turned off.

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4smarnF10j679U1@mid.individual.net
:
: Yeah, looks like you have a bad cable and DMA has been turned off.

Bingo! I thought this was the case, but when I ran other hard drive
utilities it said UDMA 5. Then, when I ran Drive Fitness Test (DFT) it
showed DMA 0. I compared that with my WD which was 5. I checked my IDE
channel settings through MY CMPUTER more carefully this time and only
PI was enabled.

I then did a search on Maxtor's site about DMA and not being able to
turn it on. Apparently, if there are more than 6 CRC errors then the
DMA is lowered:

"Windows XP downgrades the Ultra DMA transfer mode after receiving more
than six CRC errors. Whenever possible, the operating system will step
down one UDMA mode at a time (from UDMA mode 4 to UDMA mode 3, and so
on

Should I be concerned about the errors that I have had? Should I do a
reformat?

"Rod Speed" <rod.speed.aaa@gmail.comwrote in message
news:4smam7F10a5s0U1@mid.individual.net
:
:
: Thats a high level of errors on the cable to the drive.

Where are you seeing the Errors on the cable?

: Try replacing the cable and dont use round cables,
: use proper flat 80 wire ribbon cables.

I am not sure I can tell the difference. At the moment, I am using
rectangular cables that are flat. The cable is a little kinked because
of the location of the IDE channel and because I am using the same cable
for the second WD drive. The CD RM is on it's own IDE channel.

: Check that the S is using the DMA for the drive, it may well have
: turned that off with that high an error rate. Check in the Device
Manager.

Yes, it was. See my last post.

Rod,
I think I know where you see the CRC error rate: C7?

Both my WD and my Maxtor are connected. But, my WD is fine but Maxtor is high:

SMART

[ Maxtor 6L250R0 (L598P9BG) ]

ID Attribute Description Threshold Value Worst Data Status
03 Spin Up Time 63 178 178 24913 K: Value is normal
04 Start/Stop Count 0 253 253 481 K: Always passing
05 Reallocated Sector Count 63 253 253 0 K: Value is normal
06 Read Channel Margin 100 253 253 0 K: Value is normal
07 Seek Error Rate 0 253 252 0 K: Always passing
08 Seek Time Performance 187 247 238 57736 K: Value is normal
09 P Time Count 0 248 248 43539 K: Always passing
0A Spin Retry Count 157 253 252 0 K: Value is normal
0B Calibration Retry Count 223 253 252 0 K: Value is normal
0C Power Cycle Count 0 252 252 476 K: Always passing
C0 P Retract Count 0 253 253 0 K: Always passing
C1 Load/Unload Cycle Count 0 253 253 0 K: Always passing
C2 Temperature 0 32 253 31 K: Always passing
C3 Hardware ECC Recovered 0 253 252 2674 K: Always passing
C4 Reallocation Event Count 0 253 253 0 K: Always passing
C5 Current Pending Sector Count 0 253 253 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 253 253 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 49992 K: Always passing
C8 Write Error Rate 0 253 252 0 K: Always passing
C9 <vendor-specific0 253 252 0 K: Always passing
CA <vendor-specific0 253 252 0 K: Always passing
CB <vendor-specific180 253 252 0 K: Value is normal
CC <vendor-specific0 253 252 0 K: Always passing
CD <vendor-specific0 253 252 0 K: Always passing
CF <vendor-specific0 253 252 0 K: Always passing
D0 <vendor-specific0 253 252 0 K: Always passing
D1 <vendor-specific0 235 235 224 K: Always passing
D2 <vendor-specific0 253 252 0 K: Always passing
D3 <vendor-specific0 253 252 0 K: Always passing
D4 <vendor-specific0 253 249 0 K: Always passing

[ WDC WD2000JB-00GVA0 (WD-WCAL81550730) ]

ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 51 200 200 0 K: Value is normal
03 Spin Up Time 21 126 112 6225 K: Value is normal
04 Start/Stop Count 40 99 99 1287 K: Value is normal
05 Reallocated Sector Count 140 200 200 0 K: Value is normal
07 Seek Error Rate 51 200 200 0 K: Value is normal
09 P Time Count 0 95 95 4184 K: Always passing
0A Spin Retry Count 51 100 100 0 K: Value is normal
0B Calibration Retry Count 51 100 100 0 K: Value is normal
0C Power Cycle Count 0 99 99 1237 K: Always passing
C2 Temperature 0 119 99 31 K: Always passing
C4 Reallocation Event Count 0 200 200 0 K: Always passing
C5 Current Pending Sector Count 0 200 200 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 200 200 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 2 K: Always passing
C8 Write Error Rate 51 200 200 0 K: Value is normal

Sam <none@none.comwrote
Rod Speed <rod.speed.aaa@gmail.comwrote
>Sam <none@none.comwrote

C7 Ultra ATA CRC Error Rate 0 1 1 48594 K: Always passing

>Thats a high level of errors on the cable to the drive.

Where are you seeing the Errors on the cable?

That entry I put that comment directly under, for that reason.

>Try replacing the cable and dont use round cables,
>use proper flat 80 wire ribbon cables.

I am not sure I can tell the difference.

The round cables are round. Novel concept what |-)

At the moment, I am using rectangular cables that are flat.

K, you arent using a round cable.

The cable is a little kinked because of the location of the IDE channel
and because I am using the same cable for the second WD drive.

Its unlikely to be that. They usually get damaged by reefing
the off the drive connector by yanking on the ribbon itself.

The CD RM is on it's own IDE channel.

>Check that the S is using the DMA for the drive, it may well have
>turned that off with that high an error rate. Check in the Device Manager.

Yes, it was. See my last post.

Correct
"Sam" <none@none.comwrote in message news:NGt9h.362972$R63.339737@pd7urf1no
Rod,
I think I know where you see the CRC error rate: C7?

Both my WD and my Maxtor are connected. But, my WD is fine but Maxtor is high:

SMART

[ Maxtor 6L250R0 (L598P9BG) ]

ID Attribute Description Threshold Value Worst Data Status
03 Spin Up Time 63 178 178 24913 K: Value is normal
04 Start/Stop Count 0 253 253 481 K: Always passing
05 Reallocated Sector Count 63 253 253 0 K: Value is normal
06 Read Channel Margin 100 253 253 0 K: Value is normal
07 Seek Error Rate 0 253 252 0 K: Always passing
08 Seek Time Performance 187 247 238 57736 K: Value is normal
09 P Time Count 0 248 248 43539 K: Always passing
0A Spin Retry Count 157 253 252 0 K: Value is normal
0B Calibration Retry Count 223 253 252 0 K: Value is normal
0C Power Cycle Count 0 252 252 476 K: Always passing
C0 P Retract Count 0 253 253 0 K: Always passing
C1 Load/Unload Cycle Count 0 253 253 0 K: Always passing
C2 Temperature 0 32 253 31 K: Always passing
C3 Hardware ECC Recovered 0 253 252 2674 K: Always passing
C4 Reallocation Event Count 0 253 253 0 K: Always passing
C5 Current Pending Sector Count 0 253 253 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 253 253 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 1 1 49992 K: Always passing
C8 Write Error Rate 0 253 252 0 K: Always passing
C9 <vendor-specific0 253 252 0 K: Always passing
CA <vendor-specific0 253 252 0 K: Always passing
CB <vendor-specific180 253 252 0 K: Value is normal
CC <vendor-specific0 253 252 0 K: Always passing
CD <vendor-specific0 253 252 0 K: Always passing
CF <vendor-specific0 253 252 0 K: Always passing
D0 <vendor-specific0 253 252 0 K: Always passing
D1 <vendor-specific0 235 235 224 K: Always passing
D2 <vendor-specific0 253 252 0 K: Always passing
D3 <vendor-specific0 253 252 0 K: Always passing
D4 <vendor-specific0 253 249 0 K: Always passing

[ WDC WD2000JB-00GVA0 (WD-WCAL81550730) ]

ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 51 200 200 0 K: Value is normal
03 Spin Up Time 21 126 112 6225 K: Value is normal
04 Start/Stop Count 40 99 99 1287 K: Value is normal
05 Reallocated Sector Count 140 200 200 0 K: Value is normal
07 Seek Error Rate 51 200 200 0 K: Value is normal
09 P Time Count 0 95 95 4184 K: Always passing
0A Spin Retry Count 51 100 100 0 K: Value is normal
0B Calibration Retry Count 51 100 100 0 K: Value is normal
0C Power Cycle Count 0 99 99 1237 K: Always passing
C2 Temperature 0 119 99 31 K: Always passing
C4 Reallocation Event Count 0 200 200 0 K: Always passing
C5 Current Pending Sector Count 0 200 200 0 K: Always passing
C6 Line Uncorrectable Sector Count 0 200 200 0 K: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 2 K: Always passing
C8 Write Error Rate 51 200 200 0 K: Value is normal

Sam <none@none.comwrote
Rod Speed <rod.speed.aaa@gmail.comwrote

>Yeah, looks like you have a bad cable and DMA has been turned off.

Bingo! I thought this was the case, but when I ran other hard drive
utilities it said UDMA 5. Then, when I ran Drive Fitness Test (DFT)
it showed DMA 0. I compared that with my WD which was 5.
I checked my IDE channel settings through MY CMPUTER
more carefully this time and only PI was enabled.

Yeah, thats the reason for your chkdsk errors too.

I then did a search on Maxtor's site about DMA and
not being able to turn it on. Apparently, if there are
more than 6 CRC errors then the DMA is lowered:

"Windows XP downgrades the Ultra DMA transfer mode after receiving more
than six CRC errors. Whenever possible, the operating system will step down
one UDMA mode at a time (from UDMA mode 4 to UDMA mode 3, and so on

Correct. And dont forget to do the fix at the bottom of that, it wont
turn DMA back on auto once you have replaced the bad cable.

Should I be concerned about the errors that I have had?

Should be fine once you can run chkdsk without any
more errors being reported once you have replaced
the bad cable and things appear to be working fine.

Should I do a reformat?

I wouldnt unless it doesnt appear to be behaving properly with the new cable.