Ru-Board.club
← Вернуться в раздел «Программы»

» Ошибки в структуре NTFS !

Автор: hrs
Дата сообщения: 09.02.2003 15:33
С недавних пор (примерно два месяца назад) при работе в Windows XP Pro стали возникать ошибки в структуре NTFS. В результате система при перезагрузке автоматически запускает CHKDSK и после исправления ошибок пропадают несколько файлов. Чаще всего удаляются файлы из папки \Windows\System32 преимущественно dll-ки, но иногда и файлы с другими расширениями. Естественно, после некоторых особо "удачных" исправлений NTFS система просто отказывается загружаться ... Приходиться загружаться с другого винта под рабочей Win XP и в ручную восстанавливать удаленные файлы, основываясь на данных листинга выполнения команды CHKDSK. Привожу пример такого листинга:
---------------------------------------------------------------
Тип события: Уведомление
Источник события: Winlogon
Категория события: Отсутствует
Код события: 1001
Дата: 06.02.2003
Время: 22:33:59
Пользователь: Н/Д
Компьютер: HRS-WORKSTATION
Описание:
Checking file system on D:
The type of the file system is NTFS.
Volume label is Локальный диск.


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 segment number 0x3fc00000000 in file 0x7e4 is incorrect.
Correcting a minor error in file 2020.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x53bcf for possibly 0x53 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x53bcf for possibly 0x53 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7e4 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2020.
The segment number 0x3fd00000000 in file 0x7e5 is incorrect.
Correcting a minor error in file 2021.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4d90a for possibly 0x41 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x4d90a for possibly 0x41 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7e5 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2021.
The segment number 0x3fe00000000 in file 0x7e6 is incorrect.
Correcting a minor error in file 2022.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x27d6 for possibly 0xe clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x27d6 for possibly 0xe clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7e6 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2022.
The segment number 0x3ff00000000 in file 0x7e7 is incorrect.
Correcting a minor error in file 2023.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x38d9a for possibly 0x7e clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x38d9a for possibly 0x7e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x7e7 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2023.
The segment number 0x162000000000 in file 0x1b3c is incorrect.
Correcting a minor error in file 6972.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x92ff6 for possibly 0x2d clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x92ff6 for possibly 0x2d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1b3c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 6972.
The segment number 0x162100000000 in file 0x1b3d is incorrect.
Correcting a minor error in file 6973.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3bf4b for possibly 0x36 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3bf4b for possibly 0x36 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1b3d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 6973.
The segment number 0x162200000000 in file 0x1b3e is incorrect.
Correcting a minor error in file 6974.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x38fc for possibly 0x3 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x38fc for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1b3e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 6974.
The segment number 0x162300000000 in file 0x1b3f is incorrect.
Correcting a minor error in file 6975.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x45dfb for possibly 0x7f clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x45dfb for possibly 0x7f clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1b3f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 6975.
The object id in file 0x1b3f already existed in the object
id index in file 0x19.
d0 bf 2f 3e f0 1f d7 11 96 4b b3 58 7f ff a0 47 ../>.....K.X...G
3f 1b 00 00 00 00 00 00 60 3e 07 00 03 00 00 00 ?.......`>......
Deleting duplicate object id from file record segment 6975.
The file reference 0x30000000007e4 of index entry ole2disp.dll of index $I30
with parent 0x1f is not the same as 0x290000000007e4.
Deleting index entry ole2disp.dll in index $I30 of file 31.
The file reference 0x20000000007e5 of index entry ole2nls.dll of index $I30
with parent 0x1f is not the same as 0x40000000007e5.
Deleting index entry ole2nls.dll in index $I30 of file 31.
Unable to locate the file name attribute of index entry oleacc.dll
of index $I30 with parent 0x1f in file 0x7e6.
Deleting index entry oleacc.dll in index $I30 of file 31.
Unable to locate the file name attribute of index entry oleaccrc.dll
of index $I30 with parent 0x1f in file 0x7e7.
Deleting index entry oleaccrc.dll in index $I30 of file 31.
The file reference 0x3000000001b3f of index entry printui.dll of index $I30
with parent 0x1f is not the same as 0x4000000001b3f.
Deleting index entry printui.dll in index $I30 of file 31.
The file reference 0x1000000001b3d of index entry Windows Update.lnk of index $I30
with parent 0xd36 is not the same as 0x4000000001b3d.
Deleting index entry Windows Update.lnk in index $I30 of file 3382.
The file reference 0x1000000001b3d of index entry WINDOW~1.LNK of index $I30
with parent 0xd36 is not the same as 0x4000000001b3d.
Deleting index entry WINDOW~1.LNK in index $I30 of file 3382.
The file reference 0x1000000001b3e of index entry WINDOW~2.LNK of index $I30
with parent 0xd36 is not the same as 0x4000000001b3e.
Deleting index entry WINDOW~2.LNK in index $I30 of file 3382.
The file reference 0x1000000001b3e of index entry Каталог Windows.lnk of index $I30
with parent 0xd36 is not the same as 0x4000000001b3e.
Deleting index entry Каталог Windows.lnk in index $I30 of file 3382.
The file reference 0x1000000001b3c of index entry desktop.ini of index $I30
with parent 0x1b3b is not the same as 0x6cff000000001b3c.
Deleting index entry desktop.ini in index $I30 of file 6971.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 17 unused index entries from index $SII of file 0x9.
Cleaning up 17 unused index entries from index $SDH of file 0x9.
Cleaning up 17 unused security descriptors.
Inserting data attribute into file 2020.
Inserting data attribute into file 2021.
Inserting data attribute into file 2022.
Inserting data attribute into file 2023.
Inserting data attribute into file 6972.
Inserting data attribute into file 6973.
Inserting data attribute into file 6974.
Inserting data attribute into file 6975.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

4996183 KB total disk space.
3472196 KB in 19476 files.
5488 KB in 1327 indexes.
0 KB in bad sectors.
51963 KB in use by the system.
27040 KB occupied by the log file.
1466536 KB available on disk.

4096 bytes in each allocation unit.
1249045 total allocation units on disk.
366634 allocation units available on disk.

Internal Info:
87 5e 00 00 53 51 00 00 13 62 00 00 00 00 00 00 .^..SQ...b......
ae 00 00 00 00 00 00 00 89 01 00 00 00 00 00 00 ................
b0 e1 a1 02 00 00 00 00 40 96 68 12 00 00 00 00 ........@.h.....
e0 f1 73 04 00 00 00 00 00 00 00 00 00 00 00 00 ..s.............
00 00 00 00 00 00 00 00 a0 45 39 21 00 00 00 00 .........E9!....
99 9e 36 00 00 00 00 00 14 4c 00 00 00 00 00 00 ..6......L......
00 10 ed d3 00 00 00 00 2f 05 00 00 00 00 00 00 ......../.......

Windows has finished checking your disk.
Please wait while your computer restarts.
--------------------------------------------
Ошибки возникают не регулярно: от двух раз в день до одного раза в месяц...
Конфигурация машины: AMD K6-2+ 550 Mhz (VIA MVP3)/256 Mb RAM / TNT2 Pro TV-out/ SB Live ! Value / AverTV Studio, также стоит два винта: 20 и 10 Mb. Каждый винт разбит на два раздела: 1. FAT32 (Win98) 2. NTFS (WinXP Pro).
При этом ошибки возникают только на разделах NTFS указанных винтов при работе в обоих копиях WinXP.
Не один из антивирусов никакой заразы на комьютере не обнаружил, как и Ad-Aware.

Так вот, до сих пор не могу понять с чем связано возникновение данных ошибок:
или оборудование, или баг какой-то из программ, или что другое ?

Может кто сталкивался с такой проблемой или может что-нибудь подсказать...

Автор: Widok
Дата сообщения: 09.02.2003 15:55
hrs
прежде чем создать свою тему надо проверить наличие уже созданных:
http://forum.ru-board.com/forums.cgi?action=filter&forum=5&filterby=topictitle&word=ntfs
и спрашивать в одной из ранее созданной.

Страницы: 1

Предыдущая тема: Школьный Дневник


Форум Ru-Board.club — поднят 15-09-2016 числа. Цель - сохранить наследие старого Ru-Board, истории становления российского интернета. Сделано для людей.