Re: Windows bug?


If I copy 5-6 hours files with normal file names is OK ..in the moment when
I copy files with special characters in the file name _ - ~ the error appears.
I saw on google multiple problems with the same error ( index minor
inconsistencies) and most of them on AMD systems ( VIA 686B southbridge) like
my system.
SP2 has a new IDE driver for VIA chipset systems..


"seth" wrote:

> nothing to do with the os
> file system errors only
> article 885871 address an issue with dbcs on server 2003, not xp
> dbcs is having filenames with foreign character sets (chinese, japanese,
> korean, thai...)
>
>
> "anonymous" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:E5398C3A-FF81-4E89-8B16-7FF079F462DC@xxxxxxxxxxxxxxxx
> > The problem is :
> >
> > - on a Windows XP Professional with SP2 system appears the event id 55
> > error:
> >
> > "The file system structure on the disk is corrupt and unusable. Please run
> > the chkdsk utility on the volume \Device\HarddiskVolume..."
> >
> > This corruption appears only on files with long names or with special
> > characters _ - ~ in the name of the file.
> >
> > Chkdsk is running after the restarting of that workstation and is giving
> > me
> > the same output as in KB885871(correcting minor problems in in dex $I30...
> > Bellow i have few errors on that system
> >
> > 1) The error Event ID 55
> > Event Type: Error
> > Event Source: Ntfs
> > Event Category: Disk
> > Event ID: 55
> > Date: 9/18/2005
> > Time: 4:39:34 PM
> > User: N/A
> > Computer: WORKSTATION
> > Description:
> > The file system structure on the disk is corrupt and unusable. Please run
> > the chkdsk utility on the volume H:.
> >
> > For more information, see Help and Support Center at
> > Data:
> > 0000: 00 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: 18 00 00 00 00 00 00 00 ........
> > 0020: 00 00 00 00 00 00 00 00 ........
> >
> > 2) The output from chkdsk
> >
> > Event Type: Information
> > Event Source: Winlogon
> > Event Category: None
> > Event ID: 1001
> > Date: 9/18/2005
> > Time: 8:06:50 PM
> > User: N/A
> > Computer: WORKSTATION
> > Description:
> > Checking file system on H:
> > The type of the file system is NTFS.
> > Volume label is New Volume.
> >
> >
> > 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.
> > Index entry ASSOCVECTOR.H of index $I30 in file 0xfce6 points to unused
> > file
> > 0xfce8.
> > Deleting index entry ASSOCVECTOR.H in index $I30 of file 64742.
> > Index entry ASSOCV~1.H of index $I30 in file 0xfce6 points to unused file
> > 0xfce8.
> > Deleting index entry ASSOCV~1.H in index $I30 of file 64742.
> > Cleaning up 1 unused index entries from index $SII of file 0x9.
> > Cleaning up 1 unused index entries from index $SDH of file 0x9.
> > Cleaning up 1 unused security descriptors.
> > 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.
> >
> > 39070048 KB total disk space.
> > 2618672 KB in 28800 files.
> > 7572 KB in 1470 indexes.
> > 0 KB in bad sectors.
> > 162164 KB in use by the system.
> > 65536 KB occupied by the log file.
> > 36281640 KB available on disk.
> >
> > 4096 bytes in each allocation unit.
> > 9767512 total allocation units on disk.
> > 9070410 allocation units available on disk.
> >
> > Internal Info:
> > 20 73 01 00 49 76 00 00 c9 8a 00 00 00 00 00 00 s..Iv..........
> > 0a 00 00 00 00 00 00 00 0b 00 00 00 00 00 00 00 ................
> > f0 12 09 02 00 00 00 00 30 54 3f 12 00 00 00 00 ........0T?.....
> > b0 d6 c5 01 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 00 00 00 00 00 00 00 00 10 ec 00 1d 00 00 00 00 ................
> > 99 9e 36 00 00 00 00 00 f0 37 07 00 80 70 00 00 ..6......7...p..
> > 00 00 00 00 00 c0 d4 9f 00 00 00 00 be 05 00 00 ................
> >
> >
> > 3)Another output form chkdsk:(this output proves that is the same error as
> > in KB 885871 files with DBCS in the file name ( Unicode....)....contains
> > unicode NULL....
> >
> >
> > Event Type: Information
> > Event Source: Winlogon
> > Event Category: None
> > Event ID: 1001
> > Date: 9/18/2005
> > Time: 9:21:28 PM
> > User: N/A
> > Computer: WORKSTATION
> > Description:
> > Checking file system on F:
> > The type of the file system is NTFS.
> > Volume label is New Volume.
> >
> >
> > 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.
> > The attribute name for attribute of type 0xa0 and instance tag 0x3
> > contains unicode NULL.
> > a0 00 00 00 50 00 00 00 01 04 40 00 00 00 03 00 ....P.....@.....
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 48 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 H...............
> > 18 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 ................
> > a0 00 00 00 50 00 00 00 31 01 3a 16 2d 00 c3 e2 ....P...1.:.-...
> > b0 00 00 00 28 00 00 00 00 04 18 00 00 00 04 00 ....(...........
> > Deleting corrupt attribute record (160, )
> > from file record segment 129156.
> > The index bitmap for index $I30 in file 0x1f884 is invalid or missing.
> > Correcting error in index $I30 for file 129156.
> > The index bitmap $I30 is present but there is no corresponding
> > index allocation attribute in file 0x1f884.
> > Correcting error in index $I30 for file 129156.
> > The down pointer of current index entry with length 0x18 is invalid.
> > 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
> > ff ff ff ff ff ff ff ff 40 f2 53 bf 7b bc c5 01 ........@.S.{...
> > e0 af b2 bf 7b bc c5 01 e0 af b2 bf 7b bc c5 01 ....{.......{...
> > Sorting index $I30 in file 129156.
> > Cleaning up minor inconsistencies on the drive.
> > CHKDSK is recovering lost files.
> > Recovering orphaned file buttons.html (129157) into directory file 129156.
> > Recovering orphaned file BUTTON~1.HTM (129157) into directory file 129156.
> > Recovering orphaned file content.html (129158) into directory file 129156.
> > Recovering orphaned file CONTEN~1.HTM (129158) into directory file 129156.
> > Recovering orphaned file GENERI~1.SWF (129159) into directory file 129156.
> > Recovering orphaned file generic_summary.swf (129159) into directory file
> > 129156.
> > Recovering orphaned file index.html (129160) into directory file 129156.
> > Recovering orphaned file INDEX~1.HTM (129160) into directory file 129156.
> > Recovering orphaned file media.html (129161) into directory file 129156.
> > Recovering orphaned file MEDIA~1.HTM (129161) into directory file 129156.
> > Cleaning up 3 unused index entries from index $SII of file 0x9.
> > Cleaning up 3 unused index entries from index $SDH of file 0x9.
> > Cleaning up 3 unused security descriptors.
> > Correcting errors in the Volume Bitmap.
> > Windows has made corrections to the file system.
> >
> > 101482573 KB total disk space.
> > 92047044 KB in 135005 files.
> > 50044 KB in 12924 indexes.
> > 0 KB in bad sectors.
> > 217021 KB in use by the system.
> > 65536 KB occupied by the log file.
> > 9168464 KB available on disk.
> >
> > 4096 bytes in each allocation unit.
> > 25370643 total allocation units on disk.
> > 2292116 allocation units available on disk.
> >
> > Internal Info:
> > f0 41 02 00 e4 41 02 00 2a 52 03 00 00 00 00 00 .A...A..*R......
> > b0 04 00 00 00 00 00 00 0f 00 00 00 00 00 00 00 ................
> > 00 0e 8a 05 00 00 00 00 20 41 25 27 01 00 00 00 ........ A%'....
> > d0 f2 db 02 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 00 00 00 00 00 00 00 00 50 3c 1b 39 01 00 00 00 ........P<.9....
> > 99 9e 36 00 00 00 00 00 00 39 07 00 5d 0f 02 00 ..6......9..]...
> > 00 00 00 00 00 10 1b f2 15 00 00 00 7c 32 00 00 ............|2..
> > For more information, see Help and Support Center at
> >
> > This article applies only on Windows 2003 and the error was corrected with
> > SP1 Windows 2003.
> > The same problem is on this Windows XP workstation.The SP2 of Windows XP
> > has
> > appeared long before SP1 of Windows 2003 and there must be a patch to
> > resolve
> > this problem on XP operating system.
> >
> >
> > Thank you in advance,
> >
>
>
>
.