T
Tim.T
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
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