Event id 2012 windows server 2012 r2
Event id 2012 windows server 2012 r2
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I can’t get event ID 2013 (Low Disk Space) to appear in my event log on my Windows 2012 R2 server. Does anyone know the reason for this? I’ve searched the internet high and low and many people recommend adding DiskSpaceThreshold and LowDiskSpaceMinimum values to the registry. I’ve followed this advice and tried to trigger the event by almost filling a disk on my server but to no avail. The event ID 2013 just won’t appear.
It’s seems ridiculous to me that when I look at my event logs they are full of thousands of entries for things I don’t really care about (most of it is completely incomprehensible) and yet the most obvious log entries that might be remotely useful to the administrator aren’t generated by default. The status of disks in a server is a case in point. Surely every server administrator on the planet would like to be warned in advance that a particular disk is running low on space? So, why is the obvious so hard to achieve in practice?
Are DiskSpaceThreshold and LowDiskSpaceMinimum no longer valid entries on a Windows 2012 R2 server? If this is the case, what is the official solution? Do these entries require a server reboot in order to be recognised? I’m loathed to just try a reboot without knowing the answer to these questions as my server is running Hyper-V and so a reboot would have big consequences in my environment. I’m guessing that there is a different/better way of doing this in Windows Server 2012 R2? Unfortunately a few hours of searching the internet has not revealed the answer.
Ultimately my goal is to create tasks which send email to my SharePoint server when specific events occur on my servers. This allows me to create a dashboard in SharePoint which is able to give the viewer a good overview of the health of our servers in real time. The concept works well and I’ve been able to generate alert email for things like the failure of a power supply in a server. Of course the solution only works if an event appears in the System log in the first place.
So, to sum up: How do I make the elusive Event ID 2013 appear in my Event Log? It can’t be that hard can it? Thanks in advance for your time.
Event id 2012 windows server 2012 r2
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
During backup operations, on my Windows Server 2012 R2 (Hyper-v role installed) I find this warning in Event Log:
Event ID 51: An error was detected on device \Device\Harddisk5\DR43 during a paging operation.
How could I solve this issue? or Could I safely ignore this message?
Just for information, before latest OS Update Rollup installation, we also found the event below:
Event ID 157: Disk 5 has been surprise removed.
All replies
Event 157 is most often caused when something disrupts the system’s communication with a disk, such as a SAN fabric error or a SCSI bus problem. The errors can also be caused by a disk that fails, or when a user unplugs a disk while the system is running. You needs to verify the heath of the disk subsystem.
You could also refer to the article below to know more information about the event 51:
thanks for the reply.
The problem is that we cannot find Disk 5 reported in the event.
Below you can find an output of diskpart:
My opinion is that Disk 5 is the volume mounted during backup operations.
Sorry for the delay.
no fix or workaround provided from Microsoft?
This only ever occurs during backup operations.
It is driving me crazy, trying to keep clean event logs and stopping our monitoring software from generating critical alerts both to our operations centre and, more embarrassingly, to our clients.
Much as I love Microsoft bashing this bad is on us system admins.
Disk warning 51 at the end of a Windows Server Backup is caused by disk caching. It is a legitimate warning because your backups may not be viable due to the last part of the data never getting flushed to disk. Solution: Backup target disks should be dedicated and caching should be turned OF F.
I suppose some will argue that Windows Server Backup should flush all caches before it dismounts its virtual disk target(s). But, come on guys, competent admins should have turned caching off on the backup target disks when we set them up. Caching only adds another thing that can go wrong and does not appreciably improve performance for any application that «moves a LOT of data» because the cache is quickly filled and stays that way.
So turn caching off on all your backup target disks. You will likely get a one-time disk warning 34 when you do but the event 51s at the end of your backups should stop.
Hyper-v Server 2012R2: опыт установки и настройки
В этой статье я хочу поделиться своим опытом установки и настройки гипервизора Hyper-V Server 2012R2 от компании Microsoft. Итак, приступим. Дано: 2 сервера и iscsi СХД.
1. Подготовка образа
Обратную сборку распакованного дистрибутива в загрузочный iso можно выполнить например программой Ultraiso, открыв в ней исходный образ и добавив в папку Sources файл install.wim из папки D:\W2012\x64\dvd\sources и сохранить полученный образ. Опять же все описанные выше манипуляции можно и не проводить, обновленный образ ускорит развертывание сервера Hyper-V
2. Установка
Если исходный диск для установки сервера превышает в размере 2Тб, то для того чтобы иметь возможность использовать все возможное пространство диска необходимо перед началом установки сконвертировать диск в GPT и разметить его. В процессе установки это сделать невозможно.
Необходимо загрузиться в режиме PE с инсталляционного диска и запустить diskpart.
Convert MBR to GPT using DISKPART
Для дальнейшей установки необходимо в BIOS сервера выставить загрузку в UEFI режиме (но это в случае если у вас локальное дисковое хранилище сервера превышает 2 ТБ, если нет то этот шаг можно пропустить)
3. Начальная настройка
В sconfig включаем Remote Desktop (пункт 7-e-2):
Включаем ping (пункт 4-3):
В командной строке запускаем powershell и отключаем firewall (можно пропустить):
4. Настройка виртуального коммутатора
Задание пула MAC адресов для виртуального коммутатора (менять выделенные значения, т.е. берем последний октет ip-адреса (например 192.168.251.11) mgmt-интерфейса и переводим его в шестнадцатеричный вид):
Это нужно для того, чтобы MAC адреса виртуальных серверов, расположенных на разных hyper-v host, не пересекались. По умолчанию они выдаются из одного диапазона и могут получиться одинаковыми, как у меня и произошло при внедрении на одном объекте.
Получение списка сетевых адаптеров:
Нужные нам – NIC1 и NIC2.
Объединение адаптеров в группу (Team1):
Создание виртуального коммутатора (vSwitch0):
Создание виртуального сет. адаптера (Management) и подключение его к виртуальному коммутатору:
Порты на физическом коммутаторе настроены в trunk и Vlan 251. В данном примере это подсеть для управления Hyper-V сервером.
Настройка IP-адреса, маски, шлюза и DNS сервера на виртуальном адаптере (MGMT): пункт 8 меню sconfig (например: 192.168.251.11/24, gw 192.168.251.1):
После этого сервер должен пинговаться и можно использовать удаленный доступ.
Подключаемся по RDP, создаем виртуальный сетевой адаптер (Cluster) и подключаем его к виртуальному коммутатору:
5. Подключение СХД
Будем исходить из того, что СХД уже настроена и подключена в соответствующие порты коммутатора. Настроим ip-адреса для адаптеров iscsi интерфейса:
В командной строке запускаем powershell:
С сетевыми адаптерами Broadcom NetXtreme вылез неприятный баг, который выражался в том, что на драйверах, идущих в образе, была очень низкая скорость передачи по сети от 3 до 5 МБайт/с на гигабитном подключении. Низкая производительность сети —
Broadcom is aware of this issue and will release a driver update to resolve the issue. Until the driver update is available, you can work around the issue by taking one of the following actions:
Disable VMQ on the Virtual Network Adapter by using the following Windows PowerShell cmdlet:
Исправляем, либо обновляем драйвера вручную.
6. Установка необходимых ролей
Установка необходимых ролей, должно быть подключение сервера к интернету:
Это если вы не модифицировали образ, как описано в п.1.
Добавляем поддержку SAS и iSCSI в оснастке mpiocpl и после перезагрузки в диспетчере дисков LUN-ы не будут двоиться, если сервер подключен двумя и более путями.
(шесть пробелов обязательно)
При добавлении нового volume на СХД выполняем в powershell:
Настройка времени (после добавления сервера в домен Windows время будет синхронизироваться с PDC):
Event id 2012 windows server 2012 r2
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
During backup operations, on my Windows Server 2012 R2 (Hyper-v role installed) I find this warning in Event Log:
Event ID 51: An error was detected on device \Device\Harddisk5\DR43 during a paging operation.
How could I solve this issue? or Could I safely ignore this message?
Just for information, before latest OS Update Rollup installation, we also found the event below:
Event ID 157: Disk 5 has been surprise removed.
All replies
Event 157 is most often caused when something disrupts the system’s communication with a disk, such as a SAN fabric error or a SCSI bus problem. The errors can also be caused by a disk that fails, or when a user unplugs a disk while the system is running. You needs to verify the heath of the disk subsystem.
You could also refer to the article below to know more information about the event 51:
thanks for the reply.
The problem is that we cannot find Disk 5 reported in the event.
Below you can find an output of diskpart:
My opinion is that Disk 5 is the volume mounted during backup operations.
Sorry for the delay.
no fix or workaround provided from Microsoft?
This only ever occurs during backup operations.
It is driving me crazy, trying to keep clean event logs and stopping our monitoring software from generating critical alerts both to our operations centre and, more embarrassingly, to our clients.
Much as I love Microsoft bashing this bad is on us system admins.
Disk warning 51 at the end of a Windows Server Backup is caused by disk caching. It is a legitimate warning because your backups may not be viable due to the last part of the data never getting flushed to disk. Solution: Backup target disks should be dedicated and caching should be turned OF F.
I suppose some will argue that Windows Server Backup should flush all caches before it dismounts its virtual disk target(s). But, come on guys, competent admins should have turned caching off on the backup target disks when we set them up. Caching only adds another thing that can go wrong and does not appreciably improve performance for any application that «moves a LOT of data» because the cache is quickly filled and stays that way.
So turn caching off on all your backup target disks. You will likely get a one-time disk warning 34 when you do but the event 51s at the end of your backups should stop.
Event id 2012 windows server 2012 r2
Профиль | Отправить PM | Цитировать
Есть вышеописанная ошибка..
Microsoft Windows Server после установки роли DHCP Server при каждой загрузке ОС в журнале появляется ошибка EventID 8193
Гугл говорит, что проблема решается путем установки прав Full permission для пользователя SERVICE NETWORK SERVICE на ветку реестра: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS.
Но нефига это не помогает.
Решение через SubInACL описанное на течнете тоже не даёт плодов..
Может кто сталкивался и знает как решать?
