chkdsk and norton give me the same error on both of my PCs?

[ty1er]

just to let you know that i havent experienced any system weirdness... out of the blue i just felt like running chkdsk.


I just find it kinda weird that both of my PCs would give me the same errors.

When i run CHKDSK i receive this error:

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of
Security descriptor verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.




When i run Norton Disk Doctor i receive this error:

Security Descriptors...........Error

(after running Norton 3 times in a row, on the 3rd time it didnt report the error. kinda wierd.)



Restarting PC with CHKDSK or Norton running Does not fix the problem with either PC.

Is this something to worry about? Or is this normal under WinXPsp2? something to do with SP2?

I just want to know if i should be worring about this or not.

thanks

-ty1er/

 

[Nothinman]

Are you running chkdsk on a mounted volume? If so you really shouldn't do that because the in memory structures may not be in sync with what's on disk because of caching.

 

[Anubis08]

Did you run both tests on both computers?

 

[bsobel]

Originally posted by: Nothinman
Are you running chkdsk on a mounted volume? If so you really shouldn't do that because the in memory structures may not be in sync with what's on disk because of caching.

What your seeing is normal since the drive is not locked. Try using volchk instead of chkdsk, it creates a snapshot and then runs chkdsk against that. It's in the XP/2k3 resource kit.

Bill

 

[ty1er]

Originally posted by: Nothinman
Are you running chkdsk on a mounted volume? If so you really shouldn't do that because the in memory structures may not be in sync with what's on disk because of caching.

Nope, just a standard IDE HD. also, i have notice that it only happens on the system partition (c: drive)

Did you run both tests on both computers?

yes. and they had the same out come.

What your seeing is normal since the drive is not locked. Try using volchk instead of chkdsk, it creates a snapshot and then runs chkdsk against that. It's in the XP/2k3 resource kit.

ill give that a shot.

and now i can sleep well tonight

What your seeing is normal since the drive is not locked.

 

[bsobel]

Originally posted by: ty1er

Originally posted by: Nothinman
Are you running chkdsk on a mounted volume? If so you really shouldn't do that because the in memory structures may not be in sync with what's on disk because of caching.

Nope, just a standard IDE HD. also, i have notice that it only happens on the system partition (c: drive)

Just to clarify, I think you misunderstood the question. Your running on a mounted volume. By definition the system partition (your c: drive) is a mounted volume. You can have chkdsk dismount a volume (when dismounted the drive isn't available to the system), however you can't do that to the system volume (since if you did your OS would be missing 😉), that must be checked during startup (when the system can ensure that no writers are going to change the file system).

Bill

 

[ty1er]

Just to clarify, I think you misunderstood the question. Your running on a mounted volume. By definition the system partition (your c: drive) is a mounted volume. You can have chkdsk dismount a volume (when dismounted the drive isn't available to the system), however you can't do that to the system volume (since if you did your OS would be missing ), that must be checked during startup (when the system can ensure that no writers are going to change the file system).

ok, its time for me to go to sleep............

thanks bsobel for correcting my statment.

When i read the word Mounted from Nothinman post, for some odd reason in my head Mounted = Removeable. doh....... time to get some ZZZZZZZzzzzzzzz

thanks again 🙂

 

[dunkster]

If you suspect HD problems, try the diagnostic utilities offered by the maker of your HD for your HD model.

My Windows installation was running just fine with no known problems, but when creating a backup image of my OS partition, the image repeatedly failed byte-for-byte image verification test. WD Data Lifeguard diagnostic found and fixed the problem - an unreliable read/write site in the area occupied by my OS partition.

These utilities run sequential read/writes over the entire HD surface, note any unreliable sites, attempt repair by copying data from the bad site to a known-good site and lock-out the bad site from further access. I suggest that these utilities are better-suited for HD analysis/repair than either chkdsk or NDD, since they have better control of read-sensitivity for your specific HD and are thus better suited for reliably salvaging your data.

Hope this helps!

 

[bsobel]

Originally posted by: dunkster
If you suspect HD problems, try the diagnostic utilities offered by the maker of your HD for your HD model.

While not bad advice, it's not related to the question posed (which as been answered)

Bill

 

[frankswildnight]

From the "Wish I saw this thread 2 Weeks Ago" desk. I just formatted hds on two machines and reinstalled Windows. The good news is, I haven't formatted the other two machines that showed the bitmap volume errors yet. What started it on my end was one of my machines had crashed unable to read the drive. The hd probably needed replacing there, and I did. It prompted me to run chkdsk on all the other machines and I found errors on them all. Strangely enough, Microsoft escalated support told me to reinstall Windows, and so did Dell Support. Also, after installing a Lotta Files (SP2 would be considered a Lotta Files) my MFT was badly fragmented. I've been using Diskeeper Pro to defrag it. MS Escalated Support told me Diskeeper Pro was ruining my hard drives. Anyone have any opinions on that? From what I can tell, Diskeeper Pro is the only app that will defrag a MFT.

 

[jpcoolnuke]

I'm barging into this thread because I have exactly (exactly!) the same problem you are having. Volume bitmap errors in chkdsk that neither chkdsk /f or /r fixes, and it's occuring on both of my computers. Norton Disk Doctor reports "Not Fixed" on the Security Descriptor check, but if I run it several times, it is okay sometimes and not others.

Have you found out anything yet??

 

[bsobel]

Originally posted by: jpcoolnuke
I'm barging into this thread because I have exactly (exactly!) the same problem you are having. Volume bitmap errors in chkdsk that neither chkdsk /f or /r fixes, and it's occuring on both of my computers. Norton Disk Doctor reports "Not Fixed" on the Security Descriptor check, but if I run it several times, it is okay sometimes and not others. Have you found out anything yet??

Seriously, did you read the thread? I already answered the question "What your seeing is normal since the drive is not locked. Try using volchk instead of chkdsk, it creates a snapshot and then runs chkdsk against that. It's in the XP/2k3 resource kit."

Bill

 

[jpcoolnuke]

Well, thanks for the reply, I guess. I had gone through the thread, and don't recall any further response to the volchk suggestion, so I didn't know if that really was the final answer. I'll have to go look for the resource kit (which I expect has to be purchased) to get a copy of volchk. The explanation that the volume is not locked doesn't clear up much for me. That sounds like everyone should be finding chkdsk returning errors, but that doesn't appear to be the case based on what I've seen in newsgroups and the MS Knowledge Base.

 

[bsobel]

Originally posted by: jpcoolnuke
Well, thanks for the reply, I guess. I had gone through the thread, and don't recall any further response to the volchk suggestion, so I didn't know if that really was the final answer. I'll have to go look for the resource kit (which I expect has to be purchased) to get a copy of volchk. The explanation that the volume is not locked doesn't clear up much for me. That sounds like everyone should be finding chkdsk returning errors, but that doesn't appear to be the case based on what I've seen in newsgroups and the MS Knowledge Base.

Again, the behaviour your seeing is perfectly normal and does not indicate any problems. It's very common for users to see these minor errors when running chkdsk or NDD since your system continues to run and is changing the file system while your checking it. The more active your file system, the more minor inconsistancies you will see. The only way to avoid this is to lock the drive (which you can't do to the boot volume) or do the check against a snapshow (which ensures the tools view of the file system is consistent).

Bill