I was sure I had blogged this article; I know I read it and noted it, but I can’t find it in my blog. I’m getting old!
Anyway, this one deals with a scenario where Application log entries EventID 412 and EventID 257 are logged following install of Windows Server 2008 R2 as guest OS on a VHDx Hard Disk.
Consider the following scenario:
Using Windows Server 2012 Hyper-V Manager, you create a Virtual Machine with a VHDx hard disk using the New Virtual Machine wizard.
You install Windows Server 2008 R2 as guest OS on the newly created Virtual Machine. Following the install, EventID 412 and EventID 257 are logged in the Application Event Log of the guest OS.
Like physical disks, virtual disks have the same concepts of physical and logical sector sizes.
Certain applications and components, especially database and catalog, are aware of the physical sector size of the disk that they reside on. When these are moved to or installed on a physical disk that doesn’t have the same sector size as the one that they were initialized on, they will choose to do the appropriate action which may include logging an event to communicate the impact. Windows Server 2008 R2 has internal database and catalog components that will generate an error installing on an Advanced Format drive because Windows Server 2008 R2 RTM install media was prepared using a system that had a physical sector size of 512 bytes.
The VHDx hard disk created by the New Virtual Machine Wizard on Windows Server 2012 will be Advanced Format and will have a 4 KB physical sector size and a 512 byte logical sector size.
In order for Windows Server 2008 R2 to be supported as a guest OS installed on a physical or VHDx based Advanced Format drive, the install media must contain the hotfix from KB982018 or the install media must contain SP1 or later. For more information regarding the compatibility of Windows Server 2008 R2 with Advanced Format Disks see the following KB982018.
If Windows Server 2008 R2 install media with the hotfix from KB982018 or with SP1 is not available, use the New Virtual Hard Disk Wizard to create a VHD and manually attach it to the virtual machine. It is also possible to use the use the New-VHD Hyper-V Cmdlet in Windows PowerShell to create a VHDx with a virtual hard disk with a physical sector size of 512 bytes as shown in the following example:
new-vhd -path D:\VHD\vhdx512.vhdx -sizeBytes 100GB -PhysicalsectorSize 512 -dynamic
If a VHDx was created with a physical sector size of 512, it would not be considered Advanced Format and installing Windows Server 2008 R2 without the hotfix from KB982018 or SP1 would be supported. When creating a VHDx with a physical sector size of 512 bytes that is greater than 2TB, the same NTFS file system limitations that apply to a similar physical hard disk would apply to the VHDx virtual hard disk.
In other words, if you get this alert then deploy either SP1 for W2008 R2 or install the update (here’s the reason why). If you cannot do either of those, then install the OS and app into a custom VHDX as with the above cmdlet (that example creates a 100 GB Dynamic VHDX).