Arvid,
The file system found an inconsistency with the file system. At that point
in time, it scheduled CHKSDK to run on next boot. You have no control over
that action. When CHKDSK ran on the drive, it attempted to repair the
inconsistencies with the file system. As a result, you have some data
missing - however, the file system is now in a consistent state and the
remainder of your data is still good.
"Does anyone seen this before and how can i prevent it from happening
again."
There is nothing "wrong" that happened here. Everything functioned as it
should have. The file system detected an error, attempted to repair/recover
and was successful for the majority of the data. In order to prevent this
from happening again, you would have to never have a file system
inconsistency occur (nobody can guarantee that this will not happen again),
configure your system to never run CHKDSK at boot (could result in losing a
drive if file system corruption isn't found/fixed), etc...
- Greg/Raxco Software
Microsoft MVP - Windows File System
"arvid" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I have a problem and i hope some can tell me what happend and what to
> do to prevent this from happening again.
>
> I have a file server with win2k SP3 ,the os is resides on C and the
> data on E, this hd is 250 GB (1 month old). Yesterday morning i got
> the message when i tried to open a file: File is corrupt and
> inaccessable, run chdsk on....
>
> The chdsk utility refused to run. The message here was that i didn't
> have enough rights even when i tried to run is as administrator. Then
> i rebooted teh machine, chdsk ran its self. On the screen appeared
> losts of messages that is was checking the filesystem and then that it
> was deleting corrupted segments and setting the security to default.
> When teh comp was booted up , 4GB was gone.
>
> Does anyone seen this before and how can i prevent it from happening
> again.
>
> Thnx in advance
>
> greetz Nash
|
Similar Threads
