I had the exact same problem on my external storage device.
To fix it, I ran the Windows Recovery Console. Boot from
your Windows CD-ROM and choose 'R' to repair, then 'C' to
run the console. Choose the appropriate winnt installation
and then type in the admin password for your computer.
Then I ran these tools in order:
chkdsk /p /r
fixboot c:
map
fixmbr \device\harddisk0
Note: the /r option for chkdsk is very thorough in
checking for errors; it may take a long time.
I assume your windows installation is on the c: volume.
The map command will show you a list of volumes on your
hard drive. Make a note of which one is causing the
trouble for you. In my case, it was \device\harddisk0.
For more information, visit this web site:
http://support.microsoft.com/default.aspx
scid=http://support.microsoft.com:80/support/kb/articles/Q2
29/7/16.ASP&NoWebContent=1
>-----Original Message-----
>It's actually Windows XP, but there is no
`file_system`forum for
>Windows XP, so postying the message here.
>
>Anyone seen the following and got an explanation, apart
from faulty
>hardware thich has been tested and checks out.
>
>Turn on the computer, log on and the following error is
logged.
>
> Event Type: Error
> Event Source: Ntfs
> Event Category: Disk
> Event ID: 55
> Date: 22/08/2003
> Time: 14:16:40
> User: N/A
> Computer: BABYLON5
> Description:
> The file system structure on the disk is corrupt and
unusable. Please run the chkdsk utility on the volume C:.
>
> Data:
> 0000: 05 00 00 00 02 00 4e 00 ......N.
> 0008: 02 00 00 00 37 00 04 c0 ....7..À
> 0010: 00 00 00 00 32 00 00 c0 ....2..À
> 0018: 40 00 00 00 00 00 00 00 @.......
> 0020: 00 00 00 00 00 00 00 00 ........
>
>.... Very shorttly followed by an informational
message ...
>
> Event Type: Information
> Event Source: Application Popup
> Event Category: None
> Event ID: 26
> Date: 22/08/2003
> Time: 14:16:40
> User: N/A
> Computer: BABYLON5
> Description:
> Application popup: Windows - Corrupt File : The file or
directory \$Mft is corrupt and unreadable. Please run the
Chkdsk utility.
>
>.... I schedule Chkdsk and restart the computer and get
the following:
>
> Event Type: Information
> Event Source: Winlogon
> Event Category: None
> Event ID: 1001
> Date: 22/08/2003
> Time: 14:26:01
> User: N/A
> Computer: BABYLON5
> Description:
> Checking file system on C:
> The type of the file system is NTFS.
> Volume label is FIXED DISK.
>
>
> One of your disks needs to be checked for consistency.
You
> may cancel the disk check, but it is strongly recommended
> that you continue.
> Windows will now check the disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 190 unused index entries from index $SII of
file 0x9.
> Cleaning up 190 unused index entries from index $SDH of
file 0x9.
> Cleaning up 190 unused security descriptors.
> CHKDSK is verifying Usn Journal...
> Usn Journal verification completed.
>
> 120624020 KB total disk space.
> 36454155 KB in 153499 files.
> 59588 KB in 11249 indexes.
> 0 KB in bad sectors.
> 304252 KB in use by the system.
> 65536 KB occupied by the log file.
> 83806025 KB available on disk.
>
> 512 bytes in each allocation unit.
> 241248041 total allocation units on disk.
> 167612050 allocation units available on disk.
>
> Internal Info:
> a2 08 03 00 96 83 02 00 a3 30 03 00 00 00 00
00 .........0......
> 80 06 00 00 00 00 00 00 65 02 00 00 00 00 00
00 ........e.......
> 70 a6 3a 14 00 00 00 00 b0 1a 19 43 00 00 00 00
p.:........C....
> d0 03 14 0d 00 00 00 00 00 00 00 00 00 00 00
00 ................
> 00 00 00 00 00 00 00 00 f0 2a d2 70 00 00 00
00 .........*.p....
> 99 9e 36 00 00 00 00 00 9b 57 02 00 00 00 00
00 ..6......W......
> 00 2c fc b0 08 00 00 00 f1 2b 00 00 00 00 00
00 .,.......+......
>
> Windows has finished checking your disk.
> Please wait while your computer restarts.
>
>.... the computer proceeds to restart, start to load up,
get the
>Windows XP logo, screen goes blank, computer restarts
again and right
>at this moment, everything appears to be working quite
fine.
>
>I am a little perplexed to see that Chkdsk has not found
the fault.
>
>I do also have a faint recollection that it's advisable
to run CHKDSK
>periodically even if there is no error on the file system
as Chkdsk
>does some sort of internal housekeeping on the master
file table? If
>anyone knows if this is connect, can I be filled in with
the details?
>
>So, anyone got any clues to this mystery?
>.
>
Similar Threads
