Hi,
One of our main windows 2008 r2 file servers (HP Proliant ML350 G6) seems to have a dirty d: drive.
After every reboot, chkdsk runs on drive «d:» and stops with an unspecified error
(696e647863686b2e dee) when checking indexes. After the error it continues to boot and start normally into windows. The d: drive looks ok, but when I run chkdsk in windows the chkdsk runs and stops at the same point without
warning or anything else. The gui stops and exits, period. No message nothing.
When I check the d: drive with «fsutil dirty query d:», the disk is marked as «dirty» ….
The HP advanced Proliant diagnostic tools did not show any problems with the hardisks, I’m running latest HP drivers and firmwares on the server. Last but not least I don’t have any special warnings/errors etc in the event viewer.
Here is the output of chkdsk f.ex. in safe mode I did a few hours ago, the output/error is always identical:
C:>chkdsk d: /R /F /X
The type of the file system is NTFS.
Volume label is DATA.
CHKDSK is verifying files (stage 1 of 5)…
184832 file records processed.
File verification completed.
15624 large file records processed.
0 bad file records processed.
0 EA records processed.
5 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)…
10 percent complete. (182686 of 212928 index entries processed)
An unspecified error occurred (696e647863686b2e dee).
—————————
As of now, I have disabled the boot-time check on drive d: (with «chkntfs d: /x»), but I would prefer to restore it when the problem is fixed.
I tried a lot of chkdsk and safe mode combinations, nothing helped. I don’t have any clues … so your help is really welcome.
Thanks a lot!
KInd regards,
Didier
-
Edited by
Friday, March 28, 2014 6:37 AM
it is a Proliant G6 not G7
Hi,
One of our main windows 2008 r2 file servers (HP Proliant ML350 G6) seems to have a dirty d: drive.
After every reboot, chkdsk runs on drive «d:» and stops with an unspecified error
(696e647863686b2e dee) when checking indexes. After the error it continues to boot and start normally into windows. The d: drive looks ok, but when I run chkdsk in windows the chkdsk runs and stops at the same point without
warning or anything else. The gui stops and exits, period. No message nothing.
When I check the d: drive with «fsutil dirty query d:», the disk is marked as «dirty» ….
The HP advanced Proliant diagnostic tools did not show any problems with the hardisks, I’m running latest HP drivers and firmwares on the server. Last but not least I don’t have any special warnings/errors etc in the event viewer.
Here is the output of chkdsk f.ex. in safe mode I did a few hours ago, the output/error is always identical:
C:>chkdsk d: /R /F /X
The type of the file system is NTFS.
Volume label is DATA.
CHKDSK is verifying files (stage 1 of 5)…
184832 file records processed.
File verification completed.
15624 large file records processed.
0 bad file records processed.
0 EA records processed.
5 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)…
10 percent complete. (182686 of 212928 index entries processed)
An unspecified error occurred (696e647863686b2e dee).
—————————
As of now, I have disabled the boot-time check on drive d: (with «chkntfs d: /x»), but I would prefer to restore it when the problem is fixed.
I tried a lot of chkdsk and safe mode combinations, nothing helped. I don’t have any clues … so your help is really welcome.
Thanks a lot!
KInd regards,
Didier
-
Edited by
Friday, March 28, 2014 6:37 AM
it is a Proliant G6 not G7

- Remove From My Forums
-
Вопрос
-
My system will no longer boot. When it doesn’t hang on the windows logo it goes to CHKDSK and I get the error message I wrote in the title.
I’ve tried to start from last known good settings but no luck.I’m on Windows 7 (64 bit I think) I don’t know the rest of the specs off the top of my head and I can’t get into the computer. I know it says lenovo think center at startup.
Все ответы
-
Allright so I let the CHKDSK error sit for half an hour or so and the system finally booted on. I’m scared to do a system recovery so I’m going to try and make a repair disk in case the hard drive is failing.
system specs
Windows 7 Home Premium Service Pack 1
intel core 2 duo cpu e8400
64 bit
-
Id have to have the installation disc to do a repair install. I’ve done those on XP but I bought this computer used. I don’t have the disc.
-
If it was OEM then you may have to work that out with the pc vendor.
Regards, Dave Patrick ….
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter ManagementDisclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.
-
Предложено в качестве ответа
5 июля 2016 г. 9:11
-
Предложено в качестве ответа
-
Hi surrealkiller,
>>Id have to have the installation disc to do a repair install. I’ve done those on XP but I bought this computer used. I don’t have the disc
You’d better backup the current system in case data lose.
Then downloading the OS from the following site:https://www.microsoft.com/en-us/software-download/windows7 Updating the latest windows updates.
Note: You need to know the product key of your current system.
If it was an OEM OS, you’d better ask the reseller or vendor.
Best regards,
Andy_Pan
-
-
April 18 2013, 11:39
- Армия
- Компьютеры
- Техника
- Cancel
Диск не форматируется, не растет кокос …
Захотел один мой знакомый диск разделить. Дело хорошее, полезное.
На ноутбуке Windows 7 — значит можно воспользоваться средствами самой ОС. Выделил свободное место.
И тут началось — раздел создается, отформатировать — никак.
В ход пошла тяжелая артиллерия — сторонние утилиты, загрузочные диски. Отформатировать получилось.
Но вот в Windows проверка диска не проходит — обрывается на полпути, ругается на неизвестные ошибки.
То же и со сторонними утилитами — проверка начинается и тут же заканчивается.
А chkdsk показал вот такую бяку:
…
72% выполнено. (обработано записей индекса: 255 из 258)
Возникла неопределенная ошибка (696e647863686b2e dee).
Ларчик открылся просто.
Причиной такого поведения оказалась 8-я версия DrWeb, а именно настройка Низкоуровневый доступ к диску (у DrWeb 8 — правая кнопка мыши в трее — Административный режим — «Инструменты» — «Настройки» — закладка «Основные» — пункт «Превентивная защита» — кнопка «Пользовательский» — на «Низкоуровневый доступ к диску» поставить «Спрашивать» (желательно) или «Разрешить»).

В DrWeb 7 эта настройка находится в «Дополнительно» и, по-умолчанию, не запрещает доступ.
И всё!
Как говорится — RTFM.
При запуске проверки диска, DrWeb спросит Вас — разрешить проверку или нет — разрешаем и видим благополучное завершение проверки.
Кстати, здесь же можно разрешить правку HOSTS-файла. Но это уже другая история …
.