Volmgrx internal error windows server

Была на днях очень интересная задачка на несколько часов. А именно обратился клиент с проблемой – не загружается Windows 10 после обновления и уходит в синий экран (BSOD).

Ну, думаю, делов-то минут на 15-20 – загружусь через доп. параметры, удалю сбойные обновления, запущу зловещий Windows 10 и поеду спокойно домой. Но не тут-то было. По приезду узнаю, что это сервер на котором хранятся все базы данных, а удаление сбойных обновлений и установленных компонентов никак проблему запуска не решают.

Загрузившись с LiveCD понимаю, что у меня данные на месте и будто просто не работает загрузчик Windows 10, в то же время зайдя в список устройств понимаю, что у меня Windows на RAID 1 массиве лежит. Бегу в BIOS, чтобы убедиться, что у меня действительно из 2-х хардов собран RAID 1 и вижу включенный режим для HDD – ACHI. Ну, думаю Волки – программный RAID 1 что-ли на недосервере собрали… И тут меня осенило – программный RAID массив каким-то образом после обновления Windows 10 просто на просто рассыпался…

Долгие попытки разных вариантов запуска наконец-то натолкнули меня на поиск в google именно ошибки BSOD “OLMGRX INTERNAL ERROR”. Кто что только на эту тему не пишет, но ни одного поста по делу я так и не нашел, ну думаю, Яша, настало твое время, и тут он меня кидает на англоязычный пост по данной проблеме, где как раз парень описывает такую же проблему с синим экраном как у меня и ошибкой “OLMGRX INTERNAL ERROR”.

Итак, теперь о решении этой проблемы:

Нам необходимо загрузиться в режиме восстановления Windows 10 – это после старта BIOS обычно кнопки F8 или F10.
Попав в режим восстановления Windows 10 топаем по следующему пути: Устранение неполадок> Дополнительные параметры> Командная строка.
Запустив CMD вбиваем команду diskpart (таким образом запуская дисковую утилиту) и следом пишем list volume (для просмотра всех томов, присутствующих в нашей системе).
Если мы видим что-то похожее на запись ниже – то это и есть наша проблема:

Volume ###	Ltr	Label	Fs	Type	Size		Status		Info
----------	---	------  ----	-----	----------	---------
Volume 0	C		NTFS	Mirror	465 GB		Failed Rd	
Volume 1	E		NTFS	Mirror	350 MB		Failed Rd	
Volume 2	D			DVD-ROM	   0 B		No Media

Нас интересует здесь именно “Статус“, если в списке есть “Failed Rd” вместо “Healthy“, либо виднеется на русском только кусок строки “Ошибка” вместо “Исправен” – то у нас однозначно проблема именно с программным RAID массивом.

Дальше все шаги вы делаете на свой страх и риск, ибо рейд мог рассыпаться не только из-за глюка Windows 10, но и просто, если один из хардов приказал “долго жить”. Поэтому правило № 1 – сделать резервные копии всех важных данных на сторонний носитель и правильно № 2 – если совсем не уверены в своих навыках, то сделать еще резервную копию своих резервных копий еще на один сторонний носитель

Итак, допустим мы уверены, что Windows 10 у нас стоит именно на диске C:\ и его Volume Info = Volume 0, тогда дальше в CMD пишем select volume 0 и следом вводим recover.

Теперь утилита DiskPart попытается восстановить все зеркальные разделы нашего RAID массива, расположенного на этом динамическом диске.

ВНИМАНИЕ! Первое сообщение которое я увидел – было о том, что все отлично и RAID массив восстановлен. Но это на самом деле не так, если повторно выполнить в CMD команду list volume – мы увидим, что поле Status (Статус) перешло в состояние Repair (Восстановление). Поэтому CMD мы ни в коем случае не закрываем ровно до того момента, пока запустив команду list volume еще не одну сотню раз (у меня RAID восстанавливался около 2-х часов) , мы не увидим на всех томах состояние Healthy или Исправен. Только после этого можно пробовать перезагружать ПК и радоваться, что все заработало.

Если случилось так, что после долгих мучений утилиты diskpart ваши тома так и не перешли в статус Healthy или Исправен – значит вам повезло меньше, чем мне, и проблема именно аппаратная у одного из дисков. После замены неисправного харда и повторения мучений выше, ваша проблема должна решится.

Если данная статья вам облегчила жизнь и помогла решить проблему, в качестве благодарности сойдет спасибо в комментариях, либо же можете поддержать проект небольшой копеечкой.

5
2
Голосов

Рейтинг записи

О себе:

Системное администрирование, подключение и настройка оборудования, планирование и монтаж локальных сетей, внедрение и настройка 1С Розница.

Источник

If your Windows 10 system suddenly stopped booting and show the following error message :

VOLMGRX INTERNAL ERROR

It most likely mean that your software RAID volume has failed. It may indicate a hardware underlying issue, such as a failed drive or the mirror just broke and is no longer in sync.

To find out, either use the Troubleshoot option from the startup menu or boot with the installation media in recovery mode to access the same menu and chose the following options :

Troubleshoot > Advanced options > Command Prompt

Enter into the disk utility using the following command :

diskpart

Then have a look at the volumes present on your system :

list volume

If your situation match the one we are covering into this article, you should see something similar to this output :

Volume ###	Ltr	Label	Fs	Type	Size		Status		Info
----------	---	------  ----	-----	----------	-------		---------
Volume 0	C		NTFS	Mirror	465 GB		Failed Rd	
Volume 1	E		NTFS	Mirror	350 MB		Failed Rd	
Volume 2	D			DVD-ROM	   0 B		No Media

Pay special attention to the “Status” column, look for “Failed Rd” (Failed Raid).

If you see the following on your system, attempt to initiate a rebuild as followed :

select volume 0
recover

DiskPart will now attempt to rebuild all mirrored partition located on that dynamic disk. Running the “list volume” command again, you should see the state (you yon’t see the rebuild percentage though).

Leave it synchronize until full completion, you may run the command “list volume” periodically for update. Once you’ll see all volumes as “Healthy” (see example below), reboot your computer.

Volume ###	Ltr	Label	Fs	Type	Size		Status		Info
----------	---	------  ----	-----	----------	-------		---------
Volume 0	C		NTFS	Mirror	465 GB		Healthy		
Volume 1	E		NTFS	Mirror	350 MB		Healthy		
Volume 2	D			DVD-ROM	   0 B		No Media

NOTE : Il the software RAID volume(s) fail to rebuild, have a look at your hardware. Most likely a failing drive could be the root cause.

Источник

Remove From My Forums

Question
Hi,

We have a Windows Server 2012 which is stuck in a boot loop. After rebooting and selecting Disable automatic restart on system failure, the message that appears is something like Your PC ran into a problem and is collecting some error info — volmgrx
internal_error. I have tried safe more, last known good configuration but to no avail.

After a failed boot, we can select Windows Server — secondary plex in the option list and the server will boot fine — I’m guessing this is the second mirrored disk. This issue seemed to start after Windows Updates were done (but not too sure).

Can anyone point me in the right direction of fixing this. Can’t see anything obvious in Event Viewer.

Many thanks.

Answers

It could be a broken mirror.

Try this:

1. Startup with recovery and select advanced options
2. open cmd prompt
3. diskpart
4. list volume (C volume shows status as «failed rd»)
5. select volume XX
6. recover

This post is provided AS IS with no warranties or guarantees, and confers no rights.
~~~
Questo post non fornisce garanzie e non conferisce diritti
- Marked as answer by
  
  Friday, May 8, 2015 7:06 AM

Источник

Posted by legzyl 2015-12-14T05:51:50Z

Can’t boot up Server 2012 again all i see error «VOLMGRX internal_error all effort seems not working at the moment. Booting up the plex wont work

Spec

Server 2012 R2
Mirrored Hard Drive
All back-ups are in the Server

20 Replies

All backups are in the server?

This isn’t the first time it has happened?

Why did you not start backing up externally after the first time?

How did you fix it last time?

Was this post helpful?
thumb_up
thumb_down
First Time it is

Was this post helpful?
thumb_up
thumb_down
I moved this from Spiceworks Support to Windows Server.

Also, check this and see if it helps with that error:
- https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window
Be sure to keep backups and images of important systems.

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
Why would backup to the server, this creates an issue when you need to restore like now.

I dont understand your comment about plex

Was this post helpful?
thumb_up
thumb_down
You backed up the server to itself?

Why would you do that?

Rod-IT wrote:

I dont understand your comment about plex

I think he means the two disks in RAID 1, calling each disk in a RAID set a plex is an older storage term I’ve not heard in years. what is a plex — NetApp Community Opens a new window

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
The backups are not image backup but backup of files which are mirrored into other drives.

The term plex comes from a Raid configuration,

My Server has four Hard drives, the primary drive c: is mirrored to another disk so that when the O.S in C: failed it can use another drive to boot

Was this post helpful?
thumb_up
thumb_down
legzyl wrote:

My Server has four Hard drives, the primary drive c: is mirrored to another disk so that when the O.S in C: failed it can use another drive to boot

That’s not how RAID works.

If the OS becomes corrupt, the damage is mirrored to the other drive. RAID will only protect you against disk failures not against OS corruption, bad patches or anything of that nature.

Was this post helpful?
thumb_up
thumb_down
Rod-IT wrote:

It must be an ancient term, I’ve never heard of it.

Try this

https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window

Tried it before coming here i was stuck at the administrative password because it wouldn’t accept the password am using, tried both the local and domain administrative password but no avail

Was this post helpful?
thumb_up
thumb_down
Is the server a domain controller?

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
Is this the same server you have another post on, the one running Hyper-V with the DC being the hyper-v host?

http://community.spiceworks.com/topic/1341417-dhcp-roles-on-virtual-server?page=1#entry-5316951

What changed or did you do prior to this crash?

legzyl wrote:

The backups are not image backup but backup of files which are mirrored into other drives.

They are either backups or mirrors based on the RAID array, if they are mirrors due to the RAID array, calling them backups is wrong.

Was this post helpful?
thumb_up
thumb_down
legzyl wrote:

Rod-IT wrote:

It must be an ancient term, I’ve never heard of it.

Try this

https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window

Tried it before coming here i was stuck at the administrative password because it wouldn’t accept the password am using, tried both the local and domain administrative password but no avail

Reset the local admin password then.

Was this post helpful?
thumb_up
thumb_down
Rod-IT wrote:

Is this the same server you have another post on, the one running Hyper-V with the DC being the hyper-v host?

http://community.spiceworks.com/topic/1341417-dhcp-roles-on-virtual-server?page=1#entry-5316951

What changed or did you do prior to this crash?

Yes the very Same Server, but no modification was made before the crash

Was this post helpful?
thumb_up
thumb_down
JoeWilliams wrote:

Reset the local admin password then.

Please how do i do that cos i can’t log into the server

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
JoeWilliams wrote:

legzyl wrote:

Rod-IT wrote:

It must be an ancient term, I’ve never heard of it.

Try this

https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window

Tried it before coming here i was stuck at the administrative password because it wouldn’t accept the password am using, tried both the local and domain administrative password but no avail

Reset the local admin password then.

This is not going to be possible since the machine in question is a DC as well as the Hyper-V host.

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
Is your RAID array showing any errors?

Where are your physical backups?

Was this post helpful?
thumb_up
thumb_down
Rod-IT wrote:

JoeWilliams wrote:

legzyl wrote:

Rod-IT wrote:

It must be an ancient term, I’ve never heard of it.

Try this

https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window

Tried it before coming here i was stuck at the administrative password because it wouldn’t accept the password am using, tried both the local and domain administrative password but no avail

Reset the local admin password then.

This is not going to be possible since the machine in question is a DC as well as the Hyper-V host.

Oh, heck. I’m assuming the OP has also lost the DSRM password then.

Was this post helpful?
thumb_up
thumb_down
pure capsaicin

Windows Server Expert
- check
  251
  Best Answers
- thumb_up
  562
  Helpful Votes
JoeWilliams wrote:

Rod-IT wrote:

JoeWilliams wrote:

legzyl wrote:

Rod-IT wrote:

It must be an ancient term, I’ve never heard of it.

Try this

https://social.technet.microsoft.com/Forums/windowsserver/en-US/684c0faa-6b16-4da4-acca-2699dd552918… Opens a new window

Tried it before coming here i was stuck at the administrative password because it wouldn’t accept the password am using, tried both the local and domain administrative password but no avail

Reset the local admin password then.

This is not going to be possible since the machine in question is a DC as well as the Hyper-V host.

Oh, heck. I’m assuming the OP has also lost the DSRM password then.

I am going to guess this too, or they don’t know how to recover using this.

Given the OPs other post looks like they are using their DC as a Hyper-V host as well, it only adds to the issue.

Was this post helpful?
thumb_up
thumb_down
This is how our plan for a recovery scenario in cases like this.

1. First, get access to the server. Do this by installing hyper-v core onto a USB stick and boot to it. (We have a USB prepared for this and inserted into the internal USB slot on every server.)

2. After you boot to the hyper-v core, attempt to access the drives. If the array isn’t destroyed, you should see the drives and their contents.

3. Transfer the disk contents you need to another device via network or to another direct-connected device.

4. Restore or recover as needed.

Was this post helpful?
thumb_up
thumb_down
Sorry for replying to this post late, it was due to some issue i have at work which prompt me to long break.

And Thank you all for your contribution

Below is What was done on the Server

We had to get an empty hard drive install Server 2012 on it like @Robert5205 as said

On completing the installation we where able have access to the Virtualized hyper-V drive on the previous damaged OS

Then had to reconfigure a New Hyper-V Server and use the virtualized drive as the storage location.

Still lost some files though.

Was this post helpful?
thumb_up
thumb_down

Read these next…

Which network diagram (SAN to LAN) would you say is correct?

Networking

Which is best practice and why? Is it done one way over the other to avoid potential issues or is it just good housekeeping . . . or both?Edit for context . . . To the left — 3-node Hyper-V failover cluster connected to shared dual-controller storage via …
What kind of logs, data, or tooling do you have that need better visibility?

Windows

Hey,
I was part of a mass lay off awhile back, I am looking for work and
solutions to keep me busy while I continue to apply for jobs. Before I
was laid off I put together a small app that aggregated a lot of data
from GitLab with a simple sea…
Snap! — Keyboard Hat, Emotional AI, US High-Speed Trains, Astronaut Wears Prada

Spiceworks Originals

Your daily dose of tech news, in brief.

Welcome to the Snap!

Flashback: October 6, 1942: Photocopying Patented (Read more HERE.)

Bonus Flashback: October 6, 1992: US-Russia Human Spaceflight Agreement (Read more HERE.)

You need to hear…
Time Clocks

Hardware

We’re looking for a solution that would allow clients who participate in certain services to punch in and punch out on a time clock with a PIN versus fingerprint or prox card. We’d prefer the solution to be entirely local versus cloud based. We did look…
Alternative to Sophos central

Security

Hi there, I am a Sophos partner and currently have clients that run Sophos Essentials on their work machines — and it looks like our licenses are due for expiry soon. Would you guys suggest any alternative vendors that offer the same functionality as Soph…

Источник

Информация о файле	Описание
Размер файла:	302 kB
Дата и время изменения файла:	2017:03:18 18:18:56+00:00
Дата и время изменения индексного дескриптора файлов:	2017:11:05 07:07:54+00:00
Тип файла:	Win32 EXE
Тип MIME:	application/octet-stream
Предупреждение!	Possibly corrupt Version resource
Тип компьютера:	Intel 386 or later, and compatibles
Метка времени:	1984:11:08 01:40:19+00:00
Тип PE:	PE32
Версия компоновщика:	14.10
Размер кода:	279552
Размер инициализированных данных:	19968
Размер неинициализированных данных:	0
Точка входа:	0x48000
Версия ОС:	10.0
Версия образа:	10.0
Версия подсистемы:	10.0
Подсистема:	Native
Номер версии файла:	10.0.15063.0
Номер версии продукта:	10.0.15063.0
Маска флагов файлов:	0x003f
Флаги файлов:	(none)
Файловая ОС:	Windows NT 32-bit
Тип объектного файла:	Driver
Подтип файла:	7
Код языка:	English (U.S.)
Набор символов:	Unicode
Наименование компании:	Microsoft Corporation
Описание файла:	Volume Manager Extension Driver
Версия файла:	10.0.15063.0 (WinBuild.160101.0800)
Внутреннее имя:	volmgrx.sys
Авторское право:	© Microsoft Corporation. All rights reserved.
Оригинальное имя файла:	volmgrx.sys
Название продукта:	Microsoft® Windows® Operating System
Версия продукта:	10.0.15063.0

^✻ Фрагменты данных файлов предоставлены участником Exiftool (Phil Harvey) и распространяются под лицензией Perl Artistic.

Источник

Question

Answers

20 Replies

Read these next…

Which network diagram (SAN to LAN) would you say is correct?

What kind of logs, data, or tooling do you have that need better visibility?

Snap! — Keyboard Hat, Emotional AI, US High-Speed Trains, Astronaut Wears Prada

Time Clocks

Alternative to Sophos central