Link to home
Create AccountLog in
Avatar of epichero22
epichero22Flag for United States of America

asked on

Is "Correcting Errors in the Volume Bitmap" something to worry about?

Here is the result of running a chkdsk on my drive in read-only mode:

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 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal 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.

 156199994 KB total disk space.
  29493764 KB in 87018 files.
     26968 KB in 10107 indexes.
         0 KB in bad sectors.
    264586 KB in use by the system.
     65536 KB occupied by the log file.
 126414676 KB available on disk.

      4096 bytes in each allocation unit.
  39049998 total allocation units on disk.
  31603669 allocation units available on disk.

Open in new window

After, I ran it with the /r switch and rebooted the computer.  I wasn't there to see what the results were but I re-ran chkdsk again and it gave me this same message.
Avatar of skarai
Flag of United States of America image

From what  I can see it's not a problem since your drive is showing 0 KB in bad secotors. A thing to do might be to partition the drive into smaller chunks and use a different block size than the default 4 KB - how about 64 KB - especially in case you are storing very large files.
Is this the first boot up after an unexpected shutdown? Cexk your sytem log for disk related errors.
Avatar of dbrunton
I'll disagree.

See and the section with the heading NTFS File System Corruption.

It makes a suggestion as how to fix - chkdsk /f
Apparently I should have been more explicit in my answer - Windows telling you about making corrections is nothing to worry about - you will still need to allow windows to make the correction though (which it already told you in the above print out by specifying the /f switch during the next chkdsk run.)
Avatar of ocanada_techguy
Flag of Canada image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of epichero22


My attitude towards chkdsk results was always to replace a hard drive at the first sign of worries such as this one.  I figured that some proactive maintenance was better than having to deal with the chance of a total failure, which chkdsk could warn you of.  Would that be a good practice?
When you cant say for sure that the hw is still good - and you have the means to replace a suspect piece I would replace it.
Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account

Not to digress, but since you brought it up, what software do you use for imaging?
An old copy of Norton Ghost.  The experts at EE tend to recommend Acronis True Image.

For just cloning disks Ghost will do the job but BootIt is also very good.