how to see chhdsk reports

  • Thread starter Thread starter Beyond X
  • Start date Start date
B

Beyond X

When the chkdsk command is applied to a drive (e.g. CHKDSK :C in RNN), I
believe it should retun a report about the status of the drive (or
partition). But it only shows a momentary message to tell the operation
was complete. Where is the report? How can I find it?
 
Thanks for reply.
I find no items labeled 1001 in the eventviewer/application. Instead I
see Event 2 and 3. Both are crypt32 under Source. I tried two other
computers, but the results are similar. Can you suggest what I can do now?
 
Beyond said:
When the chkdsk command is applied to a drive (e.g. CHKDSK :C in RNN), I
believe it should retun a report about the status of the drive (or
partition). But it only shows a momentary message to tell the operation
was complete. Where is the report? How can I find it?
Click to expand...

Start/ Run/ Type eventvwr / OK
In the Event Viewer Console, Click the 'Application Log' link, look
under the 'Event' header for 1001 (or click the Event header to sort the
list numerically), and double click or right-click/ Properties.

Mohan...
 
Yes, there are a number of headers accumulated over a time, perhaps more
than 100 in this particular computer. I found quite a few 1001s stamped
with old dates. Those have nothing to do with CHKDSK messages.

I happened to need disk information to solve a different problem, so I
posted a question in another NG (12/13 in
microsoft.public.windowsxp.general). Paul taught me how to see CHKDSK
message by using CHKDSK in the command subwindow (instead of RUN or
Properties).
I am still thankful to your thought and time to help me out.
 
If the dirty bit is set when the computer restarts, chkdsk runs to verify
the consistency of the volume. When Autochk runs against a volume at boot
time it records its output to a file called Bootex.log in the root of the
volume being checked. The Winlogon service then moves the contents of each
Bootex.log file to the Application Event log. One event log message for each
volume checked is recorded. So check the application event log for details.

If you get an error something to the effect "cannot open volume for direct
access" There is some system/boot start device that is reading/writing to
the drive before chkdsk can get a lock on the drive. Some anti-virus
applications do this.

After backup you can also run;
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Beyond said:
Thanks for reply.
I find no items labeled 1001 in the eventviewer/application. Instead I
see Event 2 and 3. Both are crypt32 under Source. I tried two other
computers, but the results are similar. Can you suggest what I can do now?
Click to expand...

In the log displayed on the right pane when you click Application log,
there would be many entries, with multiple header description:
Type/Date/Time/Source/Category/Event/User/Computer
Look for 1001 under the header Event, and double-click.

Mohan...
 
Beyond said:
Yes, there are a number of headers accumulated over a time, perhaps more
than 100 in this particular computer. I found quite a few 1001s stamped
with old dates. Those have nothing to do with CHKDSK messages.

I happened to need disk information to solve a different problem, so I
posted a question in another NG (12/13 in
microsoft.public.windowsxp.general). Paul taught me how to see CHKDSK
message by using CHKDSK in the command subwindow (instead of RUN or
Properties).
I am still thankful to your thought and time to help me out.
Click to expand...

Didn't know you were running "chkdsk drive:" through Start/Run (that
closes the DOS Window after checking and hence unable to see the
results). No log also gets created since that not being an Event, and
won't appear in the Application log referred. Same thing for a Drive's
Properties/ Tools/ Check now...

Checking the normal way through a Command prompt (Start/ Run/ cmd)
"naturally" displays results till the DOS Window is closed (except for
C: since run after a Reboot before Windows starts).

I thought you needed to see the results of C: and mentioned Event
Viewer/ Application Log. I normally see Event IDs 1001 display chkdsk
results. Try another ID's properties under the Date run, if it varies
for you.

chkdsk drive: /F as we know automatically Fixes errors.

Mohan...
 
Back
Top