Win XP Pro SP3+

Recently, after I defrag my disks, chkdsk sets itself to run, sometimes
with just three stages (verifying files, indexes, and security
descriptors) but not infrequently it runs 5 stages, adding verification
of file data and free space. That 5 stage whole process takes about 2
hours, which is a PITA. I am not sure how to get around it other than
to shut off the machine, restart, F8 and start with most recent
successful profile... I am not sure why it does that... I have not
checked the boxes in disk management that allow one the option of
running chkdsk--both are unchecked.

Is there some way of getting around this?

Thanks
Ken K

ken wrote:

> Win XP Pro SP3+

> Recently, after I defrag my disks, chkdsk sets itself to run,
> sometimes with just three stages (verifying files, indexes, and security descriptors) but not infrequently it runs 5
> stages, adding verification of file data and free space. That 5 stage whole process takes about 2 hours, which is a
> PITA.

Thats a hell of a long time, much longer than it should be.

There must be something very seriously wrong to take that long.

> I am not sure how to get around it other than to shut off the machine, restart, F8 and start with most recent
> successful profile...

The normal way to stop it running chkdsk at boot time is to let it complete that properly.

> I am not sure why it does that...

Because you havent let it complete.

> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.

> Is there some way of getting around this?

Work out why its taking so long and fix that.

Whats the detail on the cpu and drives ?

Rod Speed wrote:
> ken wrote:
>
>> Win XP Pro SP3+
>
>> Recently, after I defrag my disks, chkdsk sets itself to run,
>> sometimes with just three stages (verifying files, indexes, and security descriptors) but not infrequently it runs 5
>> stages, adding verification of file data and free space. That 5 stage whole process takes about 2 hours, which is a
>> PITA.
>
> Thats a hell of a long time, much longer than it should be.
>
> There must be something very seriously wrong to take that long.
>
>> I am not sure how to get around it other than to shut off the machine, restart, F8 and start with most recent
>> successful profile...
>
> The normal way to stop it running chkdsk at boot time is to let it complete that properly.
>
>> I am not sure why it does that...
>
> Because you havent let it complete.
>
>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.
>
>> Is there some way of getting around this?
>
> Work out why its taking so long and fix that.
>
> Whats the detail on the cpu and drives ?
>
>
Rod,

Actually, the reason that I know how long it takes is that I HAVE let it
run. Occasionally, it will run the 3 stage, then when it reboots, it
runs the 5 stage,then it may or may not boot into the F8 screen. If
not, then it will boot correctly.

Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago with
memtest and Intelram--passed with flying colors), no overclocking, all
set at default in BIOS, drives Hitachi 500gb and Samsung 1T for storage

Thanks
Ken K

ken wrote
> Rod Speed wrote
>> ken wrote

>>> Win XP Pro SP3+

>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>> sometimes with just three stages (verifying files, indexes, and
>>> security descriptors) but not infrequently it runs 5 stages, adding
>>> verification of file data and free space. That 5 stage whole
>>> process takes about 2 hours, which is a PITA.

>> Thats a hell of a long time, much longer than it should be.

>> There must be something very seriously wrong to take that long.

>>> I am not sure how to get around it other than to shut off the
>>> machine, restart, F8 and start with most recent successful profile...

>> The normal way to stop it running chkdsk at boot time is to let it
>> complete that properly.

>>> I am not sure why it does that...

>> Because you havent let it complete.

>>> I have not checked the boxes in disk management that allow one the
>>> option of running chkdsk--both are unchecked.

>>> Is there some way of getting around this?

>> Work out why its taking so long and fix that.

>> Whats the detail on the cpu and drives ?

> Actually, the reason that I know how long it takes is that I HAVE let
> it run. Occasionally, it will run the 3 stage, then when it reboots,
> it runs the 5 stage,then it may or may not boot into the F8 screen. If not, then it will boot correctly.

> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago with memtest and Intelram--passed with flying
> colors), no overclocking, all set at default in BIOS,

Thats a bizarre time to do a chkdsk with a system like that.

> drives Hitachi 500gb and Samsung 1T for storage

Presumably its checking both drives ?

Rod Speed wrote
> ken wrote
>> Rod Speed wrote
>>> ken wrote

>>>> Win XP Pro SP3+

>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>> sometimes with just three stages (verifying files, indexes, and
>>>> security descriptors) but not infrequently it runs 5 stages, adding
>>>> verification of file data and free space. That 5 stage whole
>>>> process takes about 2 hours, which is a PITA.

>>> Thats a hell of a long time, much longer than it should be.

>>> There must be something very seriously wrong to take that long.

>>>> I am not sure how to get around it other than to shut off the
>>>> machine, restart, F8 and start with most recent successful profile...

>>> The normal way to stop it running chkdsk at boot time is to let it
>>> complete that properly.

>>>> I am not sure why it does that...

>>> Because you havent let it complete.

>>>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.

>>>> Is there some way of getting around this?

>>> Work out why its taking so long and fix that.

>>> Whats the detail on the cpu and drives ?
>
>> Actually, the reason that I know how long it takes is that I HAVE let
>> it run. Occasionally, it will run the 3 stage, then when it reboots,
>> it runs the 5 stage,then it may or may not boot into the F8 screen.
>> If not, then it will boot correctly.

>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago
>> with memtest and Intelram--passed with flying colors), no
>> overclocking, all set at default in BIOS,

> Thats a bizarre time to do a chkdsk with a system like that.

>> drives Hitachi 500gb and Samsung 1T for storage

> Presumably its checking both drives ?

Presumably the reason for the very long time is because its
somehow decided to do the full scan. What did you defrag with ?

Rod Speed wrote:
> ken wrote
>> Rod Speed wrote
>>> ken wrote
>
>>>> Win XP Pro SP3+
>
>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>> sometimes with just three stages (verifying files, indexes, and
>>>> security descriptors) but not infrequently it runs 5 stages, adding
>>>> verification of file data and free space. That 5 stage whole
>>>> process takes about 2 hours, which is a PITA.
>
>>> Thats a hell of a long time, much longer than it should be.
>
>>> There must be something very seriously wrong to take that long.
>
>>>> I am not sure how to get around it other than to shut off the
>>>> machine, restart, F8 and start with most recent successful profile...
>
>>> The normal way to stop it running chkdsk at boot time is to let it
>>> complete that properly.
>
>>>> I am not sure why it does that...
>
>>> Because you havent let it complete.
>
>>>> I have not checked the boxes in disk management that allow one the
>>>> option of running chkdsk--both are unchecked.
>
>>>> Is there some way of getting around this?
>
>>> Work out why its taking so long and fix that.
>
>>> Whats the detail on the cpu and drives ?
>
>> Actually, the reason that I know how long it takes is that I HAVE let
>> it run. Occasionally, it will run the 3 stage, then when it reboots,
>> it runs the 5 stage,then it may or may not boot into the F8 screen. If not, then it will boot correctly.
>
>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago with memtest and Intelram--passed with flying
>> colors), no overclocking, all set at default in BIOS,
>
> Thats a bizarre time to do a chkdsk with a system like that.

That is what I thought...!

>> drives Hitachi 500gb and Samsung 1T for storage
>
> Presumably its checking both drives ?

I wish that was the case, but it only checks C: drive. One other little
bit of info that I recall probably does not mean much but is as follows:
I decided to move the data files for Thunderbird a week or so ago--this
was after I had noticed the slowdown and in preparation for a failing
drive and in preparation for mounting a drive with an image from 9/08.
After I had moved my data from the profiles folder and having used it
for a few days to convince myself that there was no problem, I deleted
the files from the profiles folder, but found two files that could not
be deleted because they were corrupted. One was a .gif file and the
other was a msgFilterRules.dat file. At that point I did, in fact,
check the boxes for chkdsk to try to recover the data, hoping that they
could be recovered so that I could delete them, but no luck. That was
after a defrag (by the way, you had asked which program I use and I just
use the Windows defrag program---do you recommend a different one?) I do
not recall if it was after that initial attempt at recovery or a few
days thereafter when after defragging, I got into the cycle that I
mentioned above of either the 3 stage or 5 stage chkdsk garbage. (I
have since mounted the image from 9/08 on a different drive and the two
files that I mentioned above were easily removed without problem, so
that they were corrupted after 9/08, FWIW... Perhaps I will just
continue using the 9/08 image, now that I have updated it with all of
the latest MS upgrades. It does run more quickly than the disk that
developed the problem, but I sure would like to understand what
happened.... I may just retire that SATA drive or use it to store film
..iso files...)

Rod Speed wrote:
> Rod Speed wrote
>> ken wrote
>>> Rod Speed wrote
>>>> ken wrote
>
>>>>> Win XP Pro SP3+
>
>>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>>> sometimes with just three stages (verifying files, indexes, and
>>>>> security descriptors) but not infrequently it runs 5 stages, adding
>>>>> verification of file data and free space. That 5 stage whole
>>>>> process takes about 2 hours, which is a PITA.
>
>>>> Thats a hell of a long time, much longer than it should be.
>
>>>> There must be something very seriously wrong to take that long.
>
>>>>> I am not sure how to get around it other than to shut off the
>>>>> machine, restart, F8 and start with most recent successful profile...
>
>>>> The normal way to stop it running chkdsk at boot time is to let it
>>>> complete that properly.
>
>>>>> I am not sure why it does that...
>
>>>> Because you havent let it complete.
>
>>>>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.
>
>>>>> Is there some way of getting around this?
>
>>>> Work out why its taking so long and fix that.
>
>>>> Whats the detail on the cpu and drives ?
>>> Actually, the reason that I know how long it takes is that I HAVE let
>>> it run. Occasionally, it will run the 3 stage, then when it reboots,
>>> it runs the 5 stage,then it may or may not boot into the F8 screen.
>>> If not, then it will boot correctly.
>
>>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago
>>> with memtest and Intelram--passed with flying colors), no
>>> overclocking, all set at default in BIOS,
>
>> Thats a bizarre time to do a chkdsk with a system like that.
>
>>> drives Hitachi 500gb and Samsung 1T for storage
>
>> Presumably its checking both drives ?
>
> Presumably the reason for the very long time is because its
> somehow decided to do the full scan. What did you defrag with ?
>
>
The short (3 stage) scan only takes about 10 minutes. The 5 stage scan
is the long one, now down to about 1 hour after removing all of my temp
files. I use Windows defrag. What do you use for defragging?

ken wrote
> Rod Speed wrote
>> Rod Speed wrote
>>> ken wrote
>>>> Rod Speed wrote
>>>>> ken wrote

>>>>>> Win XP Pro SP3+

>>>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>>>> sometimes with just three stages (verifying files, indexes, and
>>>>>> security descriptors) but not infrequently it runs 5 stages, adding verification of file data and free space.
>>>>>> That 5 stage whole
>>>>>> process takes about 2 hours, which is a PITA.

>>>>> Thats a hell of a long time, much longer than it should be.

>>>>> There must be something very seriously wrong to take that long.

>>>>>> I am not sure how to get around it other than to shut off the
>>>>>> machine, restart, F8 and start with most recent successful profile...

>>>>> The normal way to stop it running chkdsk at boot time is to let it
>>>>> complete that properly.

>>>>>> I am not sure why it does that...

>>>>> Because you havent let it complete.

>>>>>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.

>>>>>> Is there some way of getting around this?

>>>>> Work out why its taking so long and fix that.

>>>>> Whats the detail on the cpu and drives ?
>>>> Actually, the reason that I know how long it takes is that I HAVE
>>>> let it run. Occasionally, it will run the 3 stage, then when it
>>>> reboots, it runs the 5 stage,then it may or may not boot into the
>>>> F8 screen. If not, then it will boot correctly.

>>>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>>>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago with memtest and Intelram--passed with flying
>>>> colors), no overclocking, all set at default in BIOS,

>>> Thats a bizarre time to do a chkdsk with a system like that.

>>>> drives Hitachi 500gb and Samsung 1T for storage

>>> Presumably its checking both drives ?

>> Presumably the reason for the very long time is because its
>> somehow decided to do the full scan. What did you defrag with ?

> The short (3 stage) scan only takes about 10 minutes.

Thats a bit on the higher side for whats presumably the 500MB drive.

> The 5 stage scan is the long one,

Yeah, thats normal. It isnt normal to see that done at boot time tho.

> now down to about 1 hour after removing all of my temp files.

> I use Windows defrag. What do you use for defragging?

I dont defrag anymore. It isnt necessary on modern systems.
The short story is that modern drives seek so fast now that
a few extra seeks with access to long files isnt even visible
anymore and the only long files that are read in their entirety
anymore are media files, particularly video files, and the rate
of access to those is entirely determined by the replay rate.

So defragging is a complete waste of time now except in the sense
that if you're stupid enough to not have full backups, it can make
recovery a bit more viable if the files dont have high write levels.

ken wrote
> Rod Speed wrote
>> ken wrote
>>> Rod Speed wrote
>>>> ken wrote

>>>>> Win XP Pro SP3+

>>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>>> sometimes with just three stages (verifying files, indexes, and security descriptors) but not infrequently it runs
>>>>> 5 stages,
>>>>> adding verification of file data and free space. That 5 stage
>>>>> whole process takes about 2 hours, which is a PITA.

>>>> Thats a hell of a long time, much longer than it should be.

>>>> There must be something very seriously wrong to take that long.

>>>>> I am not sure how to get around it other than to shut off the
>>>>> machine, restart, F8 and start with most recent successful profile...

>>>> The normal way to stop it running chkdsk at boot time is to let it
>>>> complete that properly.

>>>>> I am not sure why it does that...

>>>> Because you havent let it complete.

>>>>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.

>>>>> Is there some way of getting around this?

>>>> Work out why its taking so long and fix that.

>>>> Whats the detail on the cpu and drives ?

>>> Actually, the reason that I know how long it takes is that I HAVE
>>> let it run. Occasionally, it will run the 3 stage, then when it reboots, it runs the 5 stage,then it may or may not
>>> boot into the F8 screen.
>>> If not, then it will boot correctly.

>>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago
>>> with memtest and Intelram--passed with flying colors), no
>>> overclocking, all set at default in BIOS,

>> Thats a bizarre time to do a chkdsk with a system like that.

> That is what I thought...!

>>> drives Hitachi 500gb and Samsung 1T for storage

>> Presumably its checking both drives ?

> I wish that was the case, but it only checks C: drive.

And thats presumably the 500GB drive ?

> One other little bit of info that I recall probably does not mean much but is as follows: I decided to move the data
> files for Thunderbird a week or so ago--this was after I had noticed the slowdown and in
> preparation for a failing drive and in preparation for mounting a
> drive with an image from 9/08. After I had moved my data from the
> profiles folder and having used it for a few days to convince myself
> that there was no problem, I deleted the files from the profiles folder, but found two files that could not be deleted
> because they were corrupted.

That may well indicate that one drive does have a problem.

> One was a .gif file and the other was a msgFilterRules.dat file. At that point I did, in fact, check the boxes for
> chkdsk to try to recover the data, hoping that they could be recovered so that I could delete them, but no luck. That
> was after a defrag (by the way, you had asked which program I use and I just use the Windows defrag program---do you
> recommend a different one?)

I recommend not defragging anymore, see the other post.

> I do not recall if it was after that initial attempt at recovery or a few days thereafter when after defragging, I got
> into the cycle that I mentioned above of either the 3 stage or 5 stage chkdsk garbage.

I guess its possible that one drive is dying and its
that thats triggered the full chkdsk runs at boot time.

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

> (I have since mounted the image from 9/08 on a different drive and the two files that I mentioned above were easily
> removed without problem, so that they were corrupted after 9/08, FWIW...

> Perhaps I will just continue using the 9/08 image, now that
> I have updated it with all of the latest MS upgrades. It does run more quickly than the disk that developed the
> problem, but I sure would like to understand what happened....

Its still running chkdsk at boot time ?

I agree about understanding whats going on, I never ignore stuff like that and hope for the best.

> I may just retire that SATA drive or use it to store film .iso files...)

The Everest SMART report should give some evidence on the health of the drive.
Be sure to do that on that drive.

Rod Speed wrote:
> ken wrote
>> Rod Speed wrote
>>> ken wrote
>>>> Rod Speed wrote
>>>>> ken wrote
>
>>>>>> Win XP Pro SP3+
>
>>>>>> Recently, after I defrag my disks, chkdsk sets itself to run,
>>>>>> sometimes with just three stages (verifying files, indexes, and security descriptors) but not infrequently it runs
>>>>>> 5 stages,
>>>>>> adding verification of file data and free space. That 5 stage
>>>>>> whole process takes about 2 hours, which is a PITA.
>
>>>>> Thats a hell of a long time, much longer than it should be.
>
>>>>> There must be something very seriously wrong to take that long.
>
>>>>>> I am not sure how to get around it other than to shut off the
>>>>>> machine, restart, F8 and start with most recent successful profile...
>
>>>>> The normal way to stop it running chkdsk at boot time is to let it
>>>>> complete that properly.
>
>>>>>> I am not sure why it does that...
>
>>>>> Because you havent let it complete.
>
>>>>>> I have not checked the boxes in disk management that allow one the option of running chkdsk--both are unchecked.
>
>>>>>> Is there some way of getting around this?
>
>>>>> Work out why its taking so long and fix that.
>
>>>>> Whats the detail on the cpu and drives ?
>
>>>> Actually, the reason that I know how long it takes is that I HAVE
>>>> let it run. Occasionally, it will run the 3 stage, then when it reboots, it runs the 5 stage,then it may or may not
>>>> boot into the F8 screen.
>>>> If not, then it will boot correctly.
>
>>>> Specs: Intel DP35DP mb (BIOS is the most recent, 12/2/08), Intel
>>>> Core2Duo E8400 (3 gHz), Corsair 2 x 2GB DDR2 RAM (tested 2 days ago
>>>> with memtest and Intelram--passed with flying colors), no
>>>> overclocking, all set at default in BIOS,
>
>>> Thats a bizarre time to do a chkdsk with a system like that.
>
>> That is what I thought...!
>
>>>> drives Hitachi 500gb and Samsung 1T for storage
>
>>> Presumably its checking both drives ?
>
>> I wish that was the case, but it only checks C: drive.
>
> And thats presumably the 500GB drive ?
>
>> One other little bit of info that I recall probably does not mean much but is as follows: I decided to move the data
>> files for Thunderbird a week or so ago--this was after I had noticed the slowdown and in
>> preparation for a failing drive and in preparation for mounting a
>> drive with an image from 9/08. After I had moved my data from the
>> profiles folder and having used it for a few days to convince myself
>> that there was no problem, I deleted the files from the profiles folder, but found two files that could not be deleted
>> because they were corrupted.
>
> That may well indicate that one drive does have a problem.
>
>> One was a .gif file and the other was a msgFilterRules.dat file. At that point I did, in fact, check the boxes for
>> chkdsk to try to recover the data, hoping that they could be recovered so that I could delete them, but no luck. That
>> was after a defrag (by the way, you had asked which program I use and I just use the Windows defrag program---do you
>> recommend a different one?)
>
> I recommend not defragging anymore, see the other post.
>
>> I do not recall if it was after that initial attempt at recovery or a few days thereafter when after defragging, I got
>> into the cycle that I mentioned above of either the 3 stage or 5 stage chkdsk garbage.
>
> I guess its possible that one drive is dying and its
> that thats triggered the full chkdsk runs at boot time.
>
> Post the Everest SMART report for the drives.
> http://www.majorgeeks.com/download.php?det=4181
>
>> (I have since mounted the image from 9/08 on a different drive and the two files that I mentioned above were easily
>> removed without problem, so that they were corrupted after 9/08, FWIW...
>
>> Perhaps I will just continue using the 9/08 image, now that
>> I have updated it with all of the latest MS upgrades. It does run more quickly than the disk that developed the
>> problem, but I sure would like to understand what happened....
>
> Its still running chkdsk at boot time ?
>
> I agree about understanding whats going on, I never ignore stuff like that and hope for the best.
>
>> I may just retire that SATA drive or use it to store film .iso files...)
>
> The Everest SMART report should give some evidence on the health of the drive.
> Be sure to do that on that drive.
>
>

Here is the info on my C: drive (I was mistaken--I had thought I was
using a newer 500 GB hdd, but this is a 250 GB hdd vintage 2004) The
SMART info follows the description. (There is so much info I decided
that it was not necessary to post the info about the other two drives in
my system.)

[ HDS722525VLSA80 (VNRJ3EC6CM8M5M) ]

ATA Device Properties:
Model ID HDS722525VLSA80
Serial Number VNRJ3EC6CM8M5M
Revision V36OA60A
Parameters 484521
cylinders, 16 heads, 63 sectors per track, 512 bytes per sector
LBA Sectors 488397168
Buffer 7938 KB (Dual
Ported, Read Ahead)
Multiple Sectors 16
ECC Bytes 4
Max. PIO Transfer Mode PIO 4
Max. UDMA Transfer Mode UDMA 5 (ATA-100)
Active UDMA Transfer Mode UDMA 5 (ATA-100)
Unformatted Capacity 238475 MB

ATA Device Features:
SMART Supported
Security Mode Supported
Power Management Supported
Advanced Power Management Supported
Write Cache Supported
Host Protected Area Supported
Power-Up In Standby Supported
Automatic Acoustic Management Supported
48-bit LBA Supported
Device Configuration Overlay Supported

ATA Device Physical Info:
Manufacturer Hitachi
Hard Disk Family Deskstar 7K250
Form Factor 3.5"
Formatted Capacity 250 GB
Disks 3
Recording Surfaces 6
Physical Dimensions 146 x 101.6 x
25.4 mm
Max. Weight 640 g
Average Rotational Latency 4.17 ms
Rotational Speed 7200 RPM
Max. Internal Data Rate 757 Mbit/s
Average Seek 8.5 ms
Track-To-Track Seek 1.1 ms
Full Seek 15.1 ms
Interface SATA
Buffer-to-Host Data Rate 150 MB/s
Buffer Size 8 MB

ATA Device Manufacturer:
Company Name Hitachi Global
Storage Technologies
Product Information
http://www.hgst.com/products


[ HDS722525VLSA80 (VNRJ3EC6CM8M5M) ]

01 Raw Read Error Rate 60 94 94 851981
OK: Value is normal
02 Throughput Performance 50 100 100 0
OK: Value is normal
03 Spin Up Time 24 168 168 12124390
OK: Value is normal
04 Start/Stop Count 0 100 100 780
OK: Always passing
05 Reallocated Sector Count 5 100 100 0
OK: Value is normal
07 Seek Error Rate 67 100 100 0
OK: Value is normal
08 Seek Time Performance 20 100 100 0
OK: Value is normal
09 Power-On Time Count 0 95 95 35189
OK: Always passing
0A Spin Retry Count 60 100 100 0
OK: Value is normal
0C Power Cycle Count 0 100 100 406
OK: Always passing
C0 Power-Off Retract Count 50 99 99 2235
OK: Value is normal
C1 Load/Unload Cycle Count 50 99 99 2235
OK: Value is normal
C2 Temperature 0 137 137 20, 40
OK: Always passing
C4 Reallocation Event Count 0 100 100 0
OK: Always passing
C5 Current Pending Sector Count 0 100 100 1
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 1
OK: Always passing


It appears to look fine to me. As I say, I think I will pull it out of
service and replace it with a more reliable and faster drive. Any
recommendations? I know you are partial to Hitachi and Samsung from
recent posts. Is there any additional info you would like from the
Everest program?

Ken K