How is CHKDSK supposed to finish?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On my other desktop computer, I installed a Vista update
today, then rebooted. The new start said I needed to
check C: for consistency, so I told it to go ahead.

CHKDSK ran normally at first, getting about 90% of
the way through stage 2 (verifying indexes). Then it
slowed down quite a bit, taking about as long for the
last 10% of stage 2 as the first 90%. Then it sat there
for at least 15 minutes with nothing changing on the
screen.

Finally, stage 3 ran. It reached these two lines:

CHKDSK is verifying security descriptors (stage 3 of 3)...
5542016 security descriptors processed.

Since then, it has just sat there with no further changes
on the screen, for around two hours. Should it have
gone on with the requested reboot? Or at least told the
user to reboot again? Or something else?

Should I now shut it down for another reboot?

Robert Miles
 
On my other desktop computer, I installed a Vista update
today, then rebooted. The new start said I needed to
check C: for consistency, so I told it to go ahead.

CHKDSK ran normally at first, getting about 90% of
the way through stage 2 (verifying indexes). Then it
slowed down quite a bit, taking about as long for the
last 10% of stage 2 as the first 90%. Then it sat there
for at least 15 minutes with nothing changing on the
screen.

Finally, stage 3 ran. It reached these two lines:

CHKDSK is verifying security descriptors (stage 3 of 3)...
5542016 security descriptors processed.

Since then, it has just sat there with no further changes
on the screen, for around two hours. Should it have
gone on with the requested reboot? Or at least told the
user to reboot again? Or something else?

Should I now shut it down for another reboot?
Click to expand...

That could be bad - restarting shoud not hurt anything unless there were
already problems.
 
On my other desktop computer, I installed a Vista update
today, then rebooted. The new start said I needed to
check C: for consistency, so I told it to go ahead.

CHKDSK ran normally at first, getting about 90% of
the way through stage 2 (verifying indexes). Then it
slowed down quite a bit, taking about as long for the
last 10% of stage 2 as the first 90%. Then it sat there
for at least 15 minutes with nothing changing on the
screen.

Finally, stage 3 ran. It reached these two lines:

CHKDSK is verifying security descriptors (stage 3 of 3)...
5542016 security descriptors processed.

Since then, it has just sat there with no further changes
on the screen, for around two hours. Should it have
gone on with the requested reboot? Or at least told the
user to reboot again? Or something else?

Should I now shut it down for another reboot?
Click to expand...

Reboot..............!
 
On my other desktop computer, I installed a Vista update
today, then rebooted. The new start said I needed to
check C: for consistency, so I told it to go ahead.

CHKDSK ran normally at first, getting about 90% of
the way through stage 2 (verifying indexes). Then it
slowed down quite a bit, taking about as long for the
last 10% of stage 2 as the first 90%. Then it sat there
for at least 15 minutes with nothing changing on the
screen.

Finally, stage 3 ran. It reached these two lines:

CHKDSK is verifying security descriptors (stage 3 of 3)...
5542016 security descriptors processed.

Since then, it has just sat there with no further changes
on the screen, for around two hours. Should it have
gone on with the requested reboot? Or at least told the
user to reboot again? Or something else?

Should I now shut it down for another reboot?

Robert Miles
Click to expand...
After waiting a few hours with no more changes on
the screen, I decided to reboot, but to the D: drive
instead. This ran CHKDSK also, but with many
more changes to the directory structure (at least 174000
so far, and still continuing. Most of the changes are
to file 9 (if it has a name instead of just a number, it
scrolled off the screen while I wasn't looking). Most
of the changes are in pairs:

Inserting an index entry with id nnnnnn into index xxxx of file 9.
Inserting an index entry with id nnnnnn into index yyyy of file 9.

where nnnnnn is a constantly increasing number and xxxx and
yyyy are probably $SDH and $SIA (scrolling too fast to be
sure).

The Vista update installed before this started was probably
KB2286198, with the usual non-specific description of a
security update.

Has anyone else installing this update on a 64-bit version
of Vista seen similar problems?

Restoring from a backup is not much of an option - there
have been NO successful backups completed in the last
4 months, despite many tries.

Robert Miles
 
After waiting a few hours with no more changes on
the screen, I decided to reboot, but to the D: drive
instead. This ran CHKDSK also, but with many
more changes to the directory structure (at least 174000
so far, and still continuing. Most of the changes are
to file 9 (if it has a name instead of just a number, it
scrolled off the screen while I wasn't looking). Most
of the changes are in pairs:

Inserting an index entry with id nnnnnn into index xxxx of file 9.
Inserting an index entry with id nnnnnn into index yyyy of file 9.

where nnnnnn is a constantly increasing number and xxxx and
yyyy are probably $SDH and $SIA (scrolling too fast to be
sure).

The Vista update installed before this started was probably
KB2286198, with the usual non-specific description of a
security update.

Has anyone else installing this update on a 64-bit version
of Vista seen similar problems?

Restoring from a backup is not much of an option - there
have been NO successful backups completed in the last
4 months, despite many tries.
Click to expand...

What about backups of *your* stuff - even if you had to drag n drop?

This actually sounds like a bad hard drive - not software.
 
After waiting a few hours with no more changes on
the screen, I decided to reboot, but to the D: drive
instead. This ran CHKDSK also, but with many
more changes to the directory structure (at least 174000
so far, and still continuing. Most of the changes are
to file 9 (if it has a name instead of just a number, it
scrolled off the screen while I wasn't looking). Most
of the changes are in pairs:

Inserting an index entry with id nnnnnn into index xxxx of file 9.
Inserting an index entry with id nnnnnn into index yyyy of file 9.

where nnnnnn is a constantly increasing number and xxxx and
yyyy are probably $SDH and $SIA (scrolling too fast to be
sure).

The Vista update installed before this started was probably
KB2286198, with the usual non-specific description of a
security update.
Click to expand...

That is the last run update and should not have caused any problems,
unless you didn't let it finish properly.
Check your update records and see if it finished successfully.
If it did, you should be all right, but if it didn't, you'll have to work on
finishing it properly.
I have no idea what that #9 file is all about.
It very well could be an intrusion.
You probably know how to handle that.
Best of luck,

Harry.
 
Shenan Stanley said:
What about backups of *your* stuff - even if you had to drag n drop?

This actually sounds like a bad hard drive - not software.
Click to expand...

Backups to where? Backups to the DVD drives have
failed repeatedly, and I don't have any more hard drives.
Every time I start the backup program, it insists on a full
backup first, which would take at least 3 DVD+RWs,
but it never reaches the third one.

Backups of how much? Various programs have given
me estimates between 5500000 and 10800000 files,
mostly small *.nws files.

The CHKDSK run finally finished (apparantly) with
these last 4 lines:

Inserting an index entry with Id 345176 into index $SII of file 9.
Inserting an index entry with Id 345176 into index $SDH of file 9.
5542016 security descriptors processed.
Cleaning up 338308 unused index entries from index $SII of file 9.

Looks to me more like it decided just one file (file 9) was
messed up, but one so large it took several hours correcting it.

I finally rebooted to C: again; CHKDSK is running again.
It started stage 1 by deleting what it called several corrupt
entries in file 9; it's now continuing stage 1 more normally,
over 4340000 more files with no errors shown.

Robert Miles
 
webster72n said:
That is the last run update and should not have caused any problems,
unless you didn't let it finish properly.
Check your update records and see if it finished successfully.
If it did, you should be all right, but if it didn't, you'll have to work
on
finishing it properly.
I have no idea what that #9 file is all about.
It very well could be an intrusion.
You probably know how to handle that.
Best of luck,

Harry.
Click to expand...

I won't be able to see the update records again until the current
CHKDSK run finishes and lets me finish the reboot. Now says
it's 68% complete, and has reached the slow part of stage 2
again after reporting a few stage 2 problems with file 9 and
just one other file.

Robert Miles
 
Backups to where? Backups to the DVD drives have
failed repeatedly, and I don't have any more hard drives.
Every time I start the backup program, it insists on a full
backup first, which would take at least 3 DVD+RWs,
but it never reaches the third one.

Backups of how much? Various programs have given
me estimates between 5500000 and 10800000 files,
mostly small *.nws files.

The CHKDSK run finally finished (apparantly) with
these last 4 lines:

Inserting an index entry with Id 345176 into index $SII of file 9.
Inserting an index entry with Id 345176 into index $SDH of file 9.
5542016 security descriptors processed.
Cleaning up 338308 unused index entries from index $SII of file 9.

Looks to me more like it decided just one file (file 9) was
messed up, but one so large it took several hours correcting it.

I finally rebooted to C: again; CHKDSK is running again.
It started stage 1 by deleting what it called several corrupt
entries in file 9; it's now continuing stage 1 more normally,
over 4340000 more files with no errors shown.
Click to expand...

I'd still suspect the hardware. I recommend downloading and using the hard
drive manufacturer's (the actual drive) diagnostics utility - available
usually for download from their web page.

As for backups - get an external (USB) hard drive - I recommend the Seagate
Replica (500GB) - no muss/no fuss - it will backup *everything*.

As for my question about backing up your stuff - it seems you misunderstood
what *your stuff* is. Stuff you created/saved. Your pictures, your music,
your documents, your Internet Favorites, your email, your contacts... Stuff
you saved yourself, organized yourself, etc. The operating system and such
should already be 'backed up' by the simple fact you have the installation
media.

I doubt you need to backup the NWS files.
 
Shenan Stanley said:
(e-mail address removed) wrote: [snip]
I finally rebooted to C: again; CHKDSK is running again.
It started stage 1 by deleting what it called several corrupt
entries in file 9; it's now continuing stage 1 more normally,
over 4340000 more files with no errors shown.
Click to expand...

I'd still suspect the hardware. I recommend downloading and using the
hard drive manufacturer's (the actual drive) diagnostics utility -
available usually for download from their web page.

As for backups - get an external (USB) hard drive - I recommend the
Seagate Replica (500GB) - no muss/no fuss - it will backup *everything*.

As for my question about backing up your stuff - it seems you
misunderstood what *your stuff* is. Stuff you created/saved. Your
pictures, your music, your documents, your Internet Favorites, your email,
your contacts... Stuff you saved yourself, organized yourself, etc. The
operating system and such should already be 'backed up' by the simple fact
you have the installation media.

I doubt you need to backup the NWS files.
Click to expand...
I downloaded and started running the manufacturer's
diagnostic software months ago, if it didn't come
already installed. Running it indicates that one part
of it is imcompatible with the antivirus software I'm
using - the diagnostic software assumes that nothing
is doing much on the hard drive, and sets timeouts
accordingly, but the antivirus software sees this as idle
time when it can start a full scan which keeps the hard
drive rather busy. Before I found this, the hard drive
had already been replaced - causing more problems
than before since the full backup did not contain
some of the files I still needed.

When I'm about 1.5 years behind in reading the
newsgroups files, I do need a record of which ones
I've read, and how I've organized the others, even
those I could download again with a suitable list
of which ones.

The machine finally finished the reboot, after I
let it doing nothing visible on the screen for around
6 hours, after the CHKDSK run which took about
4 hours. The updates record said that update was
successful - but I would have preferred a much
more appropriate estimate of how long it would take.

Robert Miles
 
Back
Top