L
lukthemighty
CHKDSK DISCOVERED FREE SPACE MARKED AS ALLOCATED IN THE VOLUME BITMAP
0r
CORRECTING ERRORS IN THE VOLUME BITMAP
I’m taking these messageswen I run chkdsk without parameters from
cmd, but not always.
I’ve run chkdsk c: /r from the recovery console, also with f and r
from a bartpe boot cd. Of course I also did through windows with the
restart that is required, twice, one from "properties-tools" right
clicling c: on my computer
and by cmd.
I get no problems on results. "the voume is clean" or "there are no
problems with the file system"
I"ve heard tat chkdsk without parameters on the actine partition is
not to trust because it can’t lock the partition, but till now I had
not seen this message to my computer, but only to others.
I also take the message "SOME FILES ON THIS VOLUME COULD NOT BE
DEFRAGMENTED. CHECK THE LIST."
The defrag process seems to be done normally without problems, it does
not stop letting c: unpartitioned. But the list with not defragmented
files is empty.
I know for page file and other files that cannot be defragmented, but
I was never getting this message and I’v never seen this even on
heavily fragmented drives.
I have two primary partitions c with windows and other software
installed and with data only. I’m taking tese messages when i work
on c. I hano other real problem.
Through to search i read about corrupted disk and emergency situation
and others saying it’s no problem.
The problem appeared afterI I installed the last KB90... updates. no
other change was made. Iread about kb902400 problems to some users but
these are very different. I do not have such problems.
I have cheched for "alliens" with AVG, ADWARE, SPYBOT. All updated, I
found nothing.
It has passed almost a week and no problems.
First of all Iwant to know if my data on d are in danger???
Do i need to reformat c to fix this or to do a full and clear
reinstall?
Or it should not bother me at all?
(I ’ve seen pcs with such defrag problems and maybe worst, working
well for a long time till format was needed for different-alternative
reasons. The chkdsk bothers me more as I have not seen sth like this
till now)
0r
CORRECTING ERRORS IN THE VOLUME BITMAP
I’m taking these messageswen I run chkdsk without parameters from
cmd, but not always.
I’ve run chkdsk c: /r from the recovery console, also with f and r
from a bartpe boot cd. Of course I also did through windows with the
restart that is required, twice, one from "properties-tools" right
clicling c: on my computer
and by cmd.
I get no problems on results. "the voume is clean" or "there are no
problems with the file system"
I"ve heard tat chkdsk without parameters on the actine partition is
not to trust because it can’t lock the partition, but till now I had
not seen this message to my computer, but only to others.
I also take the message "SOME FILES ON THIS VOLUME COULD NOT BE
DEFRAGMENTED. CHECK THE LIST."
The defrag process seems to be done normally without problems, it does
not stop letting c: unpartitioned. But the list with not defragmented
files is empty.
I know for page file and other files that cannot be defragmented, but
I was never getting this message and I’v never seen this even on
heavily fragmented drives.
I have two primary partitions c with windows and other software
installed and with data only. I’m taking tese messages when i work
on c. I hano other real problem.
Through to search i read about corrupted disk and emergency situation
and others saying it’s no problem.
The problem appeared afterI I installed the last KB90... updates. no
other change was made. Iread about kb902400 problems to some users but
these are very different. I do not have such problems.
I have cheched for "alliens" with AVG, ADWARE, SPYBOT. All updated, I
found nothing.
It has passed almost a week and no problems.
First of all Iwant to know if my data on d are in danger???
Do i need to reformat c to fix this or to do a full and clear
reinstall?
Or it should not bother me at all?
(I ’ve seen pcs with such defrag problems and maybe worst, working
well for a long time till format was needed for different-alternative
reasons. The chkdsk bothers me more as I have not seen sth like this
till now)