chkdsk /F x: hangs

CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry MICROS~1 in index $I30 of file 25760.
76 percent complete. (393738 of 402366 index entries processed)

It's been at 76 percent and at 393738 index entries for hours. What
should I infer from this? Obviously, the drive has issues, but I
don't understand why CHKDSK is hanging at that spot. If the spot were
bad, shouldn't it go onto the next spot? If all subsequent spots were
bad, shouldn't it continue on until the end and say something to that
effect?

On Feb 1, 10:54*pm, yawnmoth <terra1...@yahoo.com> wrote:
> CHKDSK is verifying indexes (stage 2 of 3)...
> Deleting index entry MICROS~1 in index $I30 of file 25760.
> 76 percent complete. (393738 of 402366 index entries processed)
>
> It's been at 76 percent and at 393738 index entries for hours. *What
> should I infer from this? *Obviously, the drive has issues, but I
> don't understand why CHKDSK is hanging at that spot. *If the spot were
> bad, shouldn't it go onto the next spot? *If all subsequent spots were
> bad, shouldn't it continue on until the end and say something to that
> effect?

Ok... this is weird. I just did Select All on the text and Copy
and... it then started right back up. Moved to Step 3 and then a few
moments later, it finished.

Of course, I still can't access the disk. When I try, I get this
error:

X:\ is not accessible.

Access is denied.

Any ideas?

yawnmoth wrote:

> On Feb 1, 10:54*pm, yawnmoth <terra1...@yahoo.com> wrote:
>> CHKDSK is verifying indexes (stage 2 of 3)...
>> Deleting index entry MICROS~1 in index $I30 of file 25760.
>> 76 percent complete. (393738 of 402366 index entries processed)
>>
>> It's been at 76 percent and at 393738 index entries for hours. *What
>> should I infer from this? *Obviously, the drive has issues, but I
>> don't understand why CHKDSK is hanging at that spot. *If the spot were
>> bad, shouldn't it go onto the next spot? *If all subsequent spots were
>> bad, shouldn't it continue on until the end and say something to that
>> effect?

Not necessarily. If the drive is failing - and that's certainly what it
sounds like - it's common that Chkdsk can't continue.
>
> Ok... this is weird. I just did Select All on the text and Copy
> and... it then started right back up. Moved to Step 3 and then a few
> moments later, it finished.

Have no idea to what text you're referring.
>
> Of course, I still can't access the disk. When I try, I get this
> error:
>
> X:\ is not accessible.
>
> Access is denied.

From where are you trying to access this drive? Is this an external or
internal drive?
>
> Any ideas?

It sounds like your drive has failed. Replace it. If you want confirmation,
run a diagnostic utility from the hard drive mftr. (or use SeaTools For
DOS). If you get physical errors or that diagnostic utility won't finish,
then the drive is bad.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ

On Feb 2, 7:09*am, Malke <ma...@invalid.invalid> wrote:
> yawnmothwrote:
>
> > Ok... *this is weird. *I just did Select All on the text and Copy
> > and... *it then started right back up. *Moved to Step 3 and then a few
> > moments later, it finished.
>
> Have no idea to what text you're referring.

The diagnostic text in the cmd.exe window that appeared when I typed
in "chkdsk /F x:".

> > Of course, I still can't access the disk. *When I try, I get this
> > error:
>
> > X:\ is not accessible.
>
> > Access is denied.
>
> From where are you trying to access this drive? Is this an external or
> internal drive?

External. It's a SATA drive being accessed via a SATA<->USB adapter.

yawnmoth wrote:

> On Feb 2, 7:09*am, Malke <ma...@invalid.invalid> wrote:

>> Have no idea to what text you're referring.
>
> The diagnostic text in the cmd.exe window that appeared when I typed
> in "chkdsk /F x:".
>
>> > Of course, I still can't access the disk. *When I try, I get this
>> > error:
>>
>> > X:\ is not accessible.
>>
>> > Access is denied.
>>
>> From where are you trying to access this drive? Is this an external or
>> internal drive?
>
> External. It's a SATA drive being accessed via a SATA<->USB adapter.

If the drive is in an OEM enclosure, like a Western Digital MyBook, contact
that OEM's tech support. If it's a drive that you installed in an external
enclosure yourself, put it in another external enclosure or attach to the
computer with an adapter (or even install it internally temporarily if
that's an option) to make sure the enclosure itself isn't the problem.
Otherwise my advice is the same - it sounds like your drive is on its way
to Hard Drive Heaven.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ

"yawnmoth" <> wrote in message
news:fa397a04-46d6-4990-9eaf-...
On Feb 2, 7:09 am, Malke <ma...@invalid.invalid> wrote:
> yawnmothwrote:
>
> > Ok... this is weird. I just did Select All on the text and Copy
> > and... it then started right back up. Moved to Step 3 and then a few
> > moments later, it finished.
>
> Have no idea to what text you're referring.

The diagnostic text in the cmd.exe window that appeared when I typed
in "chkdsk /F x:".

> > Of course, I still can't access the disk. When I try, I get this
> > error:
>
> > X:\ is not accessible.
>
> > Access is denied.
>
> From where are you trying to access this drive? Is this an external or
> internal drive?

External. It's a SATA drive being accessed via a SATA<->USB adapter.

===================

I had to do exactly this last week on my Vista laptop drive.

How valuable is the data on the drive? I was able to recover most if not
all of the files - before running chkdsk /F - via R-Studio. Try the free
demo version; if it can't access the drive or find and list the files, it is
very badly damaged and you likely won't be able to recover it yourself.

http://www.r-studio.com/

HTH
-pk