chkdsk : NTFS on Vista x64

Vista x64 RTM ultimate, using a dynamic disk.

Not seen quite such an extensive chkdsk for a while... this is on a new
400Gb sata II disk (not run surface check though)

Comments welcome. Note that I was running vista, and noticed some NTFS
errors in the log. However next boot was sadly to XP, since I needed to run
Carbonite (backup) and do some work stuff (VPN) so the chkdsk was run under
XP SP2...

It looks rather messy... and looks like some MFT issues (eek).

The worst thing is, who knows what's lost ........ bit of a confidence hit.

Checking file system on G:
The type of the file system is NTFS.

The volume is dirty.
The attribute of type 0x80 and instance tag 0x0 in file 0x336b
has allocated length of 0x431f0000 instead of 0x431c5000.
Deleted corrupt attribute list entry
with type code 128 in file 13163.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x900000000cf9f. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 53151.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x700000000cfa3. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 53155.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x300000000cfad. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 53165.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x900000000cfae. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 53166.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x600000000d003. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 53251.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x200000000d86a. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 55402.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x9000000029f04. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 171780.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1c000000029f14. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 171796.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x3000000029f15. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 171797.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x5000000029f29. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 171817.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1c000000029f2d. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 171821.
Unable to locate the file name attribute of index entry
{9d4644d9-852b-4e6d-aa5c-2c4bc749eda5}
of index $I30 with parent 0xdcef in file 0x10621.
Deleting index entry {9d4644d9-852b-4e6d-aa5c-2c4bc749eda5} in index $I30
of file 56559.
Unable to locate the file name attribute of index entry {9D464~1
of index $I30 with parent 0xdcef in file 0x10621.
Deleting index entry {9D464~1 in index $I30 of file 56559.
Unable to locate the file name attribute of index entry shared.xml
of index $I30 with parent 0x106f6 in file 0x29f9d.
Deleting index entry shared.xml in index $I30 of file 67318.
Unable to locate the file name attribute of index entry 73547409d01
of index $I30 with parent 0x2a712 in file 0x2a03e.
Deleting index entry 73547409d01 in index $I30 of file 173842.
Unable to locate the file name attribute of index entry 735474~1
of index $I30 with parent 0x2a712 in file 0x2a03e.
Deleting index entry 735474~1 in index $I30 of file 173842.
Cleaning up minor inconsistencies on the drive.
Cleaning up 1349 unused index entries from index $SII of file 0x9.
Cleaning up 1349 unused index entries from index $SDH of file 0x9.
Cleaning up 1349 unused security descriptors.
Inserting data attribute into file 13163.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
The upcase file content is incorrect.
Correcting errors in the uppercase file.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

122879999 KB total disk space.
78340212 KB in 162502 files.
70652 KB in 19881 indexes.
0 KB in bad sectors.
294879 KB in use by the system.
65536 KB occupied by the log file.
44174256 KB available on disk.

4096 bytes in each allocation unit.
30719999 total allocation units on disk.
11043564 allocation units available on disk.

Internal Info:
00 ca 02 00 7a c8 02 00 0d 7e 04 00 00 00 00 00 ....z....~......
fb 00 00 00 5e 00 00 00 38 07 00 00 00 00 00 00 ....^...8.......
02 26 75 0d 00 00 00 00 64 b2 4a 62 00 00 00 00 .&u.....d.Jb....
82 51 c8 18 00 00 00 00 00 00 00 00 00 00 00 00 .Q..............
00 00 00 00 00 00 00 00 e8 b0 1b 8c 00 00 00 00 ................
40 3d 7c a6 00 00 00 00 c0 36 07 00 c6 7a 02 00 @=|......6...z..
00 00 00 00 00 d0 81 ad 12 00 00 00 a9 4d 00 00 .............M..


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Hello,

Did you format this partition using Acronis?


--
- JB

Windows Vista Support Faq
http://www.jimmah.com/vista/

Jimmy Brush wrote:
> Hello,
>
> Did you format this partition using Acronis?
>
>
No, abosolutely clean with Vista x64 RTM.

It's working ok, I'm hoping it was just some files in progress when the
power went off (not that I remember that). Possibly a defrag?
Can only see 1 file mentioned, so it;s difficult to know...

You can also check your event log - if it is filled with warnings from ntfs
and your disk driver you may be looking at an imminent drive failure.


--
- JB

Windows Vista Support Faq
http://www.jimmah.com/vista/

I have the same problem and the only way to get chkdsk c: /f to work i
to chang BIOS to boot from the Vista recovery CD, go to repair windows
and open the command prompt from there to run Chkdsk. It will run an
fix the corrupt files. Change BIOS back to boot from C: drive an
restart. This doesn't fix the Chkdsk not running after a restart whe
scheduled to but it will fix the corrupt files without having t
re-install window

--
Matt1399

Hello Matt,
Here is the link to a tutorial which will fix chkdsk not runnig at restart.

http://www.vistax64.com/tutorials/13...sta.html?ltr=C

----------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------
"Matt1399" <> wrote in message
news:...
>
> I have the same problem and the only way to get chkdsk c: /f to work is
> to chang BIOS to boot from the Vista recovery CD, go to repair windows,
> and open the command prompt from there to run Chkdsk. It will run and
> fix the corrupt files. Change BIOS back to boot from C: drive and
> restart. This doesn't fix the Chkdsk not running after a restart when
> scheduled to but it will fix the corrupt files without having to
> re-install windows
>
>
> --
> Matt1399