Chkdsk discovered free space marked as allocated.......

  • Thread starter Thread starter Gordon J. Rattray
  • Start date Start date
G

Gordon J. Rattray

Hi there,

When I do a chkdsk c: in one machine with a 160 G HDD split into 2 X 80, the
C: drive keeps coming up with "chkdsk discovered free space marked as
allocated in the volume bitmap"

It says in order to correct this "Run chkdsk with the /F option to correct
these"

It goes through the routine on startup, and I've done this several times, it
still comes up with the above errors when I do a chkdsk....

So, it's keeping on doing it and I wonder how I can put a permanent fix on
this?

Thanks,

Gordon
 
Gordon J. Rattray said:
Hi there,

When I do a chkdsk c: in one machine with a 160 G HDD split into 2 X 80, the
C: drive keeps coming up with "chkdsk discovered free space marked as
allocated in the volume bitmap"

It says in order to correct this "Run chkdsk with the /F option to correct
these"

It goes through the routine on startup, and I've done this several times, it
still comes up with the above errors when I do a chkdsk....

So, it's keeping on doing it and I wonder how I can put a permanent fix on
this?

Thanks,

Gordon
Click to expand...

You need to do what it says:
- Click Start / Run
- Type chkdsk C: /F {Enter}
- Reboot the machine
 
Curious....what's the difference between running chkdsk in a command window
and the start | run routine?

Thanks,

Gordon
 
None, except that it's easier to see the screen output
while in a Command Prompt.
 
See the following link. Have a complete information regarding your problem.

http://support.microsoft.com/kb/303079

If re-formatting is the only solution then it will not so easy as you are
receiving this error on your C Drive and may be it is your Boot / System
partition. You will not be able to format this partition within through
Windows.

Backup your all data of C Drive to a removable media or to another
partition. Boot from Windows XP bootable CD and follow the instructions to
setup and reformat the partition.

Hope this information helps you, let us know.
 
Hi Raj,

Would backing up the partition to a ghost image work?

Like this? Backup to ghost image on another partition.... Pull hard drive
out and put in another machine....reformat the first "C:" partition....then
put back in original machine and install the ghost backup image.....

Is that going to work? Or is ghost going to carry with it all the formatting
parameters?

Thanks,

Gordon
 
Found this in "BlogSpot"...... it seems that's the issue with mine and I
should leave it alone?
Gordon

Correcting errors in the Volume Bitmap. Windows found problems with the file
system.
Issue:

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

Tis is a known issue and the error messages are not actually means that
there is problem in your system. You can safely ignore the error messages.
The reason you are seeing these errors appear is because when you run CHKDSK
in command prompt, it runs in "Read only" mode, and the state of the
computer is changing at the time you run the utility. A "read only" chkdsk
on an active NTFS volume will result in false positive errors, this is
normal.

Read-only CHKDSK will abort before it completes all three phases if it
encounters errors in earlier phases and is prone to falsely reporting errors
when in read-only mode. That is, CHKDSK may report that a disk is corrupted
even when there is no real corruption present. This can happen if NTFS
happens to modify areas of the disk on behalf of some program activity that
CHKDSK is examining at the same time.

To verify a volume correctly, the volume must be in a static state, and the
only
way to guarantee that state is to lock the volume. CHKDSK only locks the
volume
when it runs before entering Windows or in Recovery Console with /F or /R
(which
implies "F") is specified.

To verify this, you can restart your computer in Recovery Console and run
"CHKDSK /f" in there. See if you get any error messages. For more
information about how to use Recovery Console, please refer to the following
article:

Description of the Windows XP Recovery Console

http://support.microsoft.com/support/kb/articles/q314/0/58.asp
 
In this condition, what I will do is:

1. Backup every single data file of my C Drive to another partition.
2. Restart the PC.
3. Boot from Windows XP Bootable disc.
4. While Setting Up windows, delete the current C Drive partition and
re-create it.
5. Quick Format partition using NTFS.

That is all but only problem is that I have to reinstall every program after
windows installation complete.

Maybe the problem with you is because of large partition size and unknown
allocation size. If you like create a small size partition while reinstalling
say "30GB".

I only use C Drive to install Windows and other application. After
installing every software it occupay only 8 to 10GB space. I never save any
of my data on C Drive.

If you still don't want to reinstall everything then try this:

1. Click Start - Run - type REGEDIT and press enter.
2. Click F3 to find an entry called "BOOTEXECUTE"
3. After finding the entry, delete the entry.
4. Restart your PC and see if it again continue to run CHKDSK.

Hope this information helps you, let us know.
 
Found this in "BlogSpot"...... it seems that's the issue with mine and I
should leave it alone?
Gordon

**********************************************************
Correcting errors in the Volume Bitmap. Windows found problems with the file
system.
Issue:

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

Tis is a known issue and the error messages are not actually means that
there is problem in your system. You can safely ignore the error messages.
The reason you are seeing these errors appear is because when you run CHKDSK
in command prompt, it runs in "Read only" mode, and the state of the
computer is changing at the time you run the utility. A "read only" chkdsk
on an active NTFS volume will result in false positive errors, this is
normal.

Read-only CHKDSK will abort before it completes all three phases if it
encounters errors in earlier phases and is prone to falsely reporting errors
when in read-only mode. That is, CHKDSK may report that a disk is corrupted
even when there is no real corruption present. This can happen if NTFS
happens to modify areas of the disk on behalf of some program activity that
CHKDSK is examining at the same time.

To verify a volume correctly, the volume must be in a static state, and the
only
way to guarantee that state is to lock the volume. CHKDSK only locks the
volume
when it runs before entering Windows or in Recovery Console with /F or /R
(which
implies "F") is specified.

To verify this, you can restart your computer in Recovery Console and run
"CHKDSK /f" in there. See if you get any error messages. For more
information about how to use Recovery Console, please refer to the following
article:

Description of the Windows XP Recovery Console

http://support.microsoft.com/support/kb/articles/q314/0/58.asp

*********************************************
 
You should try it once:

1. Click Start - Run - type REGEDIT and press enter.
2. Click F3 to find an entry called "BOOTEXECUTE"
3. After finding the entry, delete the entry.
4. Restart your PC and see if it again continue to run CHKDSK.

See if this one helps you and ignore the error on boot, let us know.
 
Gordon said:
Found this in "BlogSpot"...... it seems that's the issue with mine and I
should leave it alone?
Gordon

Correcting errors in the Volume Bitmap. Windows found problems with the file
system.
Issue:

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

Tis is a known issue and the error messages are not actually means that
there is problem in your system. You can safely ignore the error messages.
The reason you are seeing these errors appear is because when you run CHKDSK
in command prompt, it runs in "Read only" mode, and the state of the
computer is changing at the time you run the utility. A "read only" chkdsk
on an active NTFS volume will result in false positive errors, this is
normal.

Read-only CHKDSK will abort before it completes all three phases if it
encounters errors in earlier phases and is prone to falsely reporting errors
when in read-only mode. That is, CHKDSK may report that a disk is corrupted
even when there is no real corruption present. This can happen if NTFS
happens to modify areas of the disk on behalf of some program activity that
CHKDSK is examining at the same time.

To verify a volume correctly, the volume must be in a static state, and the
only
way to guarantee that state is to lock the volume. CHKDSK only locks the
volume
when it runs before entering Windows or in Recovery Console with /F or /R
(which
implies "F") is specified.

To verify this, you can restart your computer in Recovery Console and run
"CHKDSK /f" in there. See if you get any error messages. For more
information about how to use Recovery Console, please refer to the following
article:

Description of the Windows XP Recovery Console

http://support.microsoft.com/support/kb/articles/q314/0/58.asp


news:%[email protected]...
Click to expand...
[deleted]
Getting the message "Correcting errors in the Volume Bitmap ... etc"
after a complete restart (rather than waking up from Hibernate) is my
experience also. If I immediately run chkdsk again (without
restarting), the message is usually no longer there. "Gordon J.
Rattray's" advice seems to be quite correct. I have learnt to ignore
the chkdsk error message.
 
RajKohli said:
You should try it once:

1. Click Start - Run - type REGEDIT and press enter.
2. Click F3 to find an entry called "BOOTEXECUTE"
3. After finding the entry, delete the entry.
4. Restart your PC and see if it again continue to run CHKDSK.

See if this one helps you and ignore the error on boot, let us know.
Click to expand...

I tried it out of curiosity, and found four entries of "BOOTEXECUTE"
at different places. Since I don't have any trouble with chkdsk, I
didn't delete any one of them, but if I do get trouble, which one(s)
should I delete? Is it safe to delete them?.
 
To disable CHKDSK in windows 2000 and XP do the following

1. Run the Registry Editor (regedt32.exe) or regedit

2. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:

\SYSTEM\CurrentControlSet\Control\Session Manager

3. Change the BootExecute entry to:

autocheck autochk *

Exit your registry, you may need to restart or log out of Windows for the
change to take effect.
 
Here is some more information regarding the same. Check it out and let me know.

Windows: On & Off
Enable or disable Scandisk/Chkdsk on system reboot

If you disable the automatic execution of Scandisk (Win98, ME) or Chkdsk
(Win2K, XP), you should run it manually about every two weeks to maintain the
integrity of your PC's file system

Windows XP

Start>Run>chkntfs /x <drive> [drive] [drive]
For example, if you want to disable Chkdsk from running on drive C: chkntfs
/x c:
Chkntfs works by modifying the BootExecute value in the Registry.
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager
The default value is BootExecute:REG_MULTI_SZ:autocheck autochk *
Chkdsk /f /r is unaffected by chkntfs and can be run to check volumes
manually on the next system reboot.


Windows 98/ME

Start>Run>Msconfig>Advanced>Disable Scandisk after bad shutdown Win98:
If you prefer to play with the Msdos. sys file:
Add AutoScan=0 to the [Options] section.
WinMe: If you prefer to play with the Registry:
Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem]
Value Name: DisableScandiskOnBoot
Data Type: REG_BINARY
Value Data: 01


--------------------------------------------------------------------------------


Warm boot (9x)

Go to the Start Menu and click on shut down. Then make sure that in the
selection box the Restart option is selected, then hold down the shift key
and press Restart.


--------------------------------------------------------------------------------


Restart the computer from a shortcut

c:\windows\rundll.exe user.exe, exitwindowsexec
c:\windows\rundll.exe shell32.dll, SHExitWindowsEX 2


--------------------------------------------------------------------------------


Shutdown Problems

Windows XP
Control Panel>Power Options>APM
Check Enable Advanced Power Management support

Windows 9x

Msconfig>Advanced>Disable Fast Shutdown.
The exit windows .wav file can also cause this.
Windows 98 SE: Article and Patch (Microsoft site)
If your computer still won't shut down properly, check this page.


--------------------------------------------------------------------------------


Run programs at shutdown

The start command allows you to run DOS and Windows programs from a batch
file. The /w switch allows the program to finish running before the next
program starts running. For example, if you want to run scandisk before
shutting down, you need the following batch file: @echo off start /w
c:\windows\scandskw.exe /a /n start
c:\windows\rundll32.exec:\windows\system\shell32.dll,shexitwindowsex 1
Create a shortcut to your batch file, then click it when you want to shutdown.


--------------------------------------------------------------------------------


Shut down programs when shutting down windows

[HKEY_CURRENT_USER\Control Panel\Desktop] Create the string value
AutoEndTasks, value = 1. Reboot.


--------------------------------------------------------------------------------


Invalid directory

If a directory is left open at shutdown, and is deleted from DOS, and
Windows is no longer saving Explorer folder settings, you will get a message
about an invalid directory when you boot up. Simply re-enable the save option
and reboot.
(TweakUI's Explorer tab). You can also get this message if a reference to a
non-existent folder exists in the startup folder, or is referenced in the
registry. Check startup with msconfig. If that reveals nothing, search the
registry for the folder name and delete the entries.


--------------------------------------------------------------------------------


Change Windows Logo (9x)

Win9x logo files must be 30x400-256 colors. When viewed during startup,
Windows stretches them to 640x400, so keep that in mind if you're designing
your own logos, else it will throw the aspect ratio off. The default image is
in oi.sys. The startup logo file (logo.sys) goes in the root directory. If
your drive is compressed, logo.sys needs to be placed in the host drive.
The shutdown logo files go in the windows directory:
The Please Wait logo is in the logow.sys
The Shutdown logo is in the logos.sys


--------------------------------------------------------------------------------


Disable or Enable Windows XP Auto Updates

To modify your autoupdate settings for Windows XP, use the following steps.
Click on START.
Click on either CONTROL PANEL or SETTINGS, then CONTROL PANEL (depending on
how your desktop is configured).
If you are using Category View, click on PERFORMANCE & MAINTENANCE, then the
SYSTEM icon.
If you are using Classic View, simply click on SYSTEM.
Click on the AUTOMATIC UPDATES tab.
Click on the KEEP MY COMPUTER UP TO DATE option to either turn on or off
autoupdates. If you turn autoupdates on, you will then be able to choose from
the three autoupdate options mentioned previously.
Simply click on the radio button next to the option you want to select.
Click on APPLY, and then click on OK.
 
Back
Top