My drive has 6 partitions and all are NTFS. I executed a batch file on the
drive to run chkdsk as part of regular drive maintenence (probably pointless
on NTFS drives, I know). As it started to scan C:, it suddenly hanged. It
got past stage 1, but no further. I tried "chkdsk c: /v" and "chkdsk c:" but
it still hanged. The other partitions did the same. Even when I ran Scandisk
it got about 80% through Phase 2, then said "Cannot complete scan on drive".

My PC boots up ok, and I have no problems accessing or reading the drive. My
PC is over a year old with the drive already in it when I bought it. The
drive's working temperature varies between 34-39C and it's the only drive I
have, with plenty of fans, so I doubt it's over-heating. It's a Samsung
drive, and when I usually run the extensive Samsung drive tools for an hour
and a half, it reports 100% healthy. No errors, no bad sectors, nothing.
I've already ran it 3 times; I might run it again to be sure.

I recently switched from the generic Windows IDE controller drivers to my
chipset's own nVidia IDE drivers - would this cause the symptoms? If I
recall, I never had this issue when using the Windows IDE drivers. For now
chkdsk seems unuseable and I have no other way of scanning my drive for
errors, should I be concerned?

Tim

Most of the OEM disk utilities simply work fair in windows explorer,the
MS-DOS
utility is what works best,all OEMs have one...Also,for CHKDSK,go to
run,type:
CLEANMGR /SAGESET Choose the files to clean,after return to run,type:
CLEANMGR /SAGERUN (This works in cmd also),after,return to run,type:cmd
In cmd type:CHKDSK C: After continue with CHKDSK but replace C: with
D:,E:,etc
This is only read only.To access all volumes,install xp cd,boot to
cd,recovery,
select 1 For C: Press enter for password,type:CHKDSK C: /p continue with
other
volumes.

"Tim.T" wrote:

> My drive has 6 partitions and all are NTFS. I executed a batch file on the
> drive to run chkdsk as part of regular drive maintenence (probably pointless
> on NTFS drives, I know). As it started to scan C:, it suddenly hanged. It
> got past stage 1, but no further. I tried "chkdsk c: /v" and "chkdsk c:" but
> it still hanged. The other partitions did the same. Even when I ran Scandisk
> it got about 80% through Phase 2, then said "Cannot complete scan on drive".
>
> My PC boots up ok, and I have no problems accessing or reading the drive. My
> PC is over a year old with the drive already in it when I bought it. The
> drive's working temperature varies between 34-39C and it's the only drive I
> have, with plenty of fans, so I doubt it's over-heating. It's a Samsung
> drive, and when I usually run the extensive Samsung drive tools for an hour
> and a half, it reports 100% healthy. No errors, no bad sectors, nothing.
> I've already ran it 3 times; I might run it again to be sure.
>
> I recently switched from the generic Windows IDE controller drivers to my
> chipset's own nVidia IDE drivers - would this cause the symptoms? If I
> recall, I never had this issue when using the Windows IDE drivers. For now
> chkdsk seems unuseable and I have no other way of scanning my drive for
> errors, should I be concerned?
>
> Tim
>
>
>

Andrew E. wrote:
> Most of the OEM disk utilities simply work fair in windows explorer,the
> MS-DOS
> utility is what works best,all OEMs have one...Also,for CHKDSK,go to
> run,type:

(snip Andrew's insane troll rantings)

>
> "Tim.T" wrote:
>
>> My drive has 6 partitions and all are NTFS. I executed a batch file on the
>> drive to run chkdsk as part of regular drive maintenence (probably pointless
>> on NTFS drives, I know). As it started to scan C:, it suddenly hanged. It
>> got past stage 1, but no further. I tried "chkdsk c: /v" and "chkdsk c:" but
>> it still hanged. The other partitions did the same. Even when I ran Scandisk
>> it got about 80% through Phase 2, then said "Cannot complete scan on drive".
>>
>> My PC boots up ok, and I have no problems accessing or reading the drive. My
>> PC is over a year old with the drive already in it when I bought it. The
>> drive's working temperature varies between 34-39C and it's the only drive I
>> have, with plenty of fans, so I doubt it's over-heating. It's a Samsung
>> drive, and when I usually run the extensive Samsung drive tools for an hour
>> and a half, it reports 100% healthy. No errors, no bad sectors, nothing.
>> I've already ran it 3 times; I might run it again to be sure.
>>
>> I recently switched from the generic Windows IDE controller drivers to my
>> chipset's own nVidia IDE drivers - would this cause the symptoms? If I
>> recall, I never had this issue when using the Windows IDE drivers. For now
>> chkdsk seems unuseable and I have no other way of scanning my drive for
>> errors, should I be concerned?

It is far more likely that your batch file is written incorrectly. Try
scanning your drives one at a time and see if that works to narrow down
the troubleshooting.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Andrew

You are one unbelievable ******. Instead of posting in these newsgroups try the following.

Lurk and read and learn. Do this for a few years then come back and try to post. Hopefully by that time you have collected enough knowledge to answer correctly.

For now go away on a long sabbatical and practice how not to troll
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Andrew E." <(E-Mail Removed)> wrote in message news:32798A54-EF81-4A6C-874C-(E-Mail Removed)...
> Most of the OEM disk utilities simply work fair in windows explorer,the
> MS-DOS
> utility is what works best,all OEMs have one...Also,for CHKDSK,go to
> run,type:
> CLEANMGR /SAGESET Choose the files to clean,after return to run,type:
> CLEANMGR /SAGERUN (This works in cmd also),after,return to run,type:cmd
> In cmd type:CHKDSK C: After continue with CHKDSK but replace C: with
> D:,E:,etc
> This is only read only.To access all volumes,install xp cd,boot to
> cd,recovery,
> select 1 For C: Press enter for password,type:CHKDSK C: /p continue with
> other
> volumes.
>
> "Tim.T" wrote:
>
>> My drive has 6 partitions and all are NTFS. I executed a batch file on the
>> drive to run chkdsk as part of regular drive maintenence (probably pointless
>> on NTFS drives, I know). As it started to scan C:, it suddenly hanged. It
>> got past stage 1, but no further. I tried "chkdsk c: /v" and "chkdsk c:" but
>> it still hanged. The other partitions did the same. Even when I ran Scandisk
>> it got about 80% through Phase 2, then said "Cannot complete scan on drive".
>>
>> My PC boots up ok, and I have no problems accessing or reading the drive. My
>> PC is over a year old with the drive already in it when I bought it. The
>> drive's working temperature varies between 34-39C and it's the only drive I
>> have, with plenty of fans, so I doubt it's over-heating. It's a Samsung
>> drive, and when I usually run the extensive Samsung drive tools for an hour
>> and a half, it reports 100% healthy. No errors, no bad sectors, nothing.
>> I've already ran it 3 times; I might run it again to be sure.
>>
>> I recently switched from the generic Windows IDE controller drivers to my
>> chipset's own nVidia IDE drivers - would this cause the symptoms? If I
>> recall, I never had this issue when using the Windows IDE drivers. For now
>> chkdsk seems unuseable and I have no other way of scanning my drive for
>> errors, should I be concerned?
>>
>> Tim
>>
>>
>>