running chkdsk on hard drive.

[Kerry Brown]

Service pack 2 with everything updated.

Did you try the suggestion in the link about running vrfydsk.exe to see if
the problem was real?

 

[Johnnief]

Did you try the suggestion in the link about running vrfydsk.exe to
see if the problem was real?

Yep, it would not work. Would not create the shadow copy. I tried many
times and many ways. But I think I know the answer to my main problem
now. The idea that the errors may not be real was interesting.

===============insert==================
C:\Program Files\Windows Resource Kits\Tools>vrfydsk C: /V

Attempting to create shadow copy of
\\?\Volume{b6383666-947c-11da-80c5-0013d43a89d4}\.

Shadow copy creation failed on
\\?\Volume{b6383666-947c-11da-80c5-0013d43a89d4}\. Unexpected error.
(Error: 0xc0000005)


C:\Program Files\Windows Resource Kits\Tools>
===============end======================

The answer is that I think I should have listened to the first guy who
said there was nothing wrong.

Yesterday I started puting a system together from some old stuff around
and some borrowed stuff. My plan was to create a good system partition
ready to install on the other two machines. The system had WinXP SP1
installed on a borrowed 40 Gig hard drive (which caused other problems
on my network, see below) so after first making sure the machine worked
I fdisked the drive and installed XP Pro SP2.

So first thing I did after installing all of the current updates was,
yep, CHKDSK. Guess what it does the exact same thing as the other two
machines on a fresh install with none of my apps installed. CHKDSK after
CHKDSK leaves errors in the Event Viewer LOG file.

I wonder how many other people have actually checked their system to see
if they get the same results I have been getting. Go to the repair
console and do repeated CHKDSK /P, rebooting inbetween each one until it
shows no errors, now boot windows and then exit back to the repair
console and run chkdsk again. Bet you get errors. I went across the
street to a friends place and tried it on his machine and got the same
results.

I am concluding that the CHKDSK problem is not a problem at all. I don't
believe these are real errors. If you read the info about Vrfydsk that
Kerry pointed me to you will see what I mean. Most people never run
chkdsk multiple times to see these errors. Just another windows feature
I guess.

As for the other problem I had, I kept losing browsing on my network. I
could use network drives but could not drill down to my shares through
"My Network Places". I had the same problem a few weeks ago but it
started working again. I suspected this time that it was because of the
SP1 machine on my network. I had someones laptop with SP1 on my network
the first time it happened also, I am quite sure. This time it would not
work again even with the SP1 machine removed from the network. I found
an error in Event viewer related to browsing so I started searching.

===========Insert==============
C:\Documents and Settings\Johnnie>sc query browser

SERVICE_NAME: browser
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTD
OWN)
WIN32_EXIT_CODE : 1460 (0x5b4)
SERVICE_EXIT_CODE : 1460 (0x5b4)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
==================end=======================

Microsoft says they have a patch for this problem but it looks like I
would have to pay for it. Screw that.

So I went to Google and did some more searches on the error text.

================insert====================
The Computer Browser service terminated with the following error:
This operation returned because the timeout period expired.
==================end=====================

The URL is way too long but if your interested stick that whole thing
above here in Google on one line. Turns out a lot of people are having
this error.

In this URL http://www.mcse.ms/message1782755.html someone mentions it
happening after turning off the Firewall. Some girl there suggested
turning it back on and since mine is disabled I thought, why not.

Well turns out it was NOT turning the firewall on that solved the
problem but starting the firewall service did. I had disabled the
service since I was not using the firewall anyway, I have a hardware
firewall. Seems like the SP1 machine on the network was triggering a
problem if the firewall service is disabled. Now the error is gone and my
shares are all working again and the firewall is still disabled.

Thanks for the help everyone. Hopefully this will help someone else
sometime.

Johnnie

 

[chrisv]

The answer is that I think I should have listened to the first guy who
said there was nothing wrong.

Yesterday I started puting a system together from some old stuff
around and some borrowed stuff. My plan was to create a good system
partition ready to install on the other two machines. The system had
WinXP SP1 installed on a borrowed 40 Gig hard drive (which caused
other problems on my network, see below) so after first making sure
the machine worked I fdisked the drive and installed XP Pro SP2.

Why are you using an old DOS command with Windows XP? Maybe that's your
problem.

Move up to Windows NT based commands like diskpart.exe.

 

[Johnnief]

Why are you using an old DOS command with Windows XP? Maybe that's
your problem.

I don't have a problem, XP does. Did you check your system? I have
checked three others now and they all do the same thing as mine.

Move up to Windows NT based commands like diskpart.exe.

That is what I meant, sorry to confuse you. I used XP to partition the
drive on install. The point was that it was a new partition. It was
late, I was tired.

 

[relic]

I don't have a problem, XP does. Did you check your system? I have
checked three others now and they all do the same thing as mine.



That is what I meant, sorry to confuse you. I used XP to partition the
drive on install. The point was that it was a new partition. It was
late, I was tired.

 

[relic]

I don't have a problem, XP does. Did you check your system? I have
checked three others now and they all do the same thing as mine.

I have 10 disks attached, all NTFS, no problems with chkdsk, but I did some
time ago. My problem sounded the same as yours on the C: drive and it was
fixed (?) by doing a full format followed by a clean install. No 'problems'
since.

 

[Wesley Vogel]

Hi Johnnie,

The answer is that I think I should have listened to the first guy who
said there was nothing wrong.
Hmm.

CHKDSK after
CHKDSK leaves errors in the Event Viewer LOG file.

Those are not errors. It is houscleaning and houscleaning is going to
happen if you run chkdsk.exe. Think Merry Maids with brooms.

Cleaning up minor inconsistencies on the drive.

[[In the above error message, "minor inconsistencies" refers to a state
where redundant information stored in different places is "out of synch."
This is a natural and expected condition whenever there are open files on
the volume that have undergone modification. The redundant information is
not brought into synchronization until the files are closed. Typically, this
error message occurs when CHKDSK is run against the volume containing
Windows NT system files (including active user profiles and the pagefile).

WORKAROUND
You can usually safely ignore this error message even if the message appears
without there being open files, because it is only the redundant information
that is out of synchronization. The only side effect you may see as a result
of this message is an incorrect reading of free disk space or something
similar. ]]
http://support.microsoft.com/?kbid=109524

Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe reports only unused index and security descriptor entries that
were removed. ]]
[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]

Cleaning up 10 unused security descriptors.

[[When you delete a file or folder with permissions that you've set by hand
rather than allowed to be automatically inherited from its parent, the ACL
(Access Control List, the security descriptor) isn't deleted, but cached.
Running CHKDSK against these "dead" items cleans up the ACLs that are no
longer in use and frees up space. ]]
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In