Repair-NaVirtualDiskAlignment repair boot record

[WAKEMAN811]

I have noticed that after running Repair-NaVirtualDiskAlignment the vhd's boot config data needs to be repaired.

Once the disk's have been aligned windows will no longer boot and gives error 0xc000000e.

To fix this I ran "bootrec /RebuildBcd" while booted from a windows cd.

Is this normal?

[crocker]

is this one that your team handles or should the question be asked in the NetApp Support Community?

[sizemore]

Hey Scott,

No you shouldn't have to fix the boot sector after the repair.  Could you share some additional data with us?

Size of VHD:

OS:

ONTAP Version:

This problem has been reported before, but we've been unable to repro the error.  Until then we can't find the problem.

~Glenn

[WAKEMAN811]

Sure Glenn,

The vm i am testing with is 2008R2 Standard Core

It has 2 vhd's attached to it, 4GB and 40GB

Ontapi   Version

  ------   -------

1.13     NetApp Release 8.0.2P4 7-Mode: Tue Nov 15 16:16:47 PST 2011

The command i am running is

Repair-NaVirtualDiskAlignment  -virtualdisk $VHDFullPath -controller $controller -confirm:$False -ForceHostCopy

I look forward to resolving this issue, as i am writing a script to check and repair any misaligned vhd's in our Hyper-V enviroment.

Thanks for the support,

Scott

[beam]

Hi Scott,

Could you also provide us the output of "Get-NaVirtualDiskAlignment -VirtualDisk $VHDFullPath | fl *" for the misaligned VHDs attached to the VM?

Thanks,

Steven

[WAKEMAN811]

Sorry for the slow response, i ran the above command with these results:

Size                 : 4293918720

VirtualDisk          : \\warthog\C$\ClusterStorage\Volume1\skeet\189ba1eb-643b-11df-808f-806e6f6e6963_2011-04-05T162446.vhd

StartingSectorChs    : (0, 1, 1)

EndingSectorChs      : (521, 254, 63)

IsBootable           : True

PartitionType        : 7

StartingLba          : 63

SizeLba              : 8386560

SizeInBytes          : 4293918720

AbsoluteStartingLba  : 63

IsExtendedBootRecord : False

Ebr                  :

IsAligned            : False

Size                 : 42841669632

VirtualDisk          : \\warthog\C$\ClusterStorage\Volume1\skeet\C_2011-04-05T162446.vhd

StartingSectorChs    : (0, 1, 1)

EndingSectorChs      : (1023, 254, 63)

IsBootable           : False

PartitionType        : 7

StartingLba          : 63

SizeLba              : 83675136

SizeInBytes          : 42841669632

AbsoluteStartingLba  : 63

IsExtendedBootRecord : False

Ebr                  :

IsAligned            : False

[paulshearer]

I'm also experiancing the same issue.  My VMs are on Windows 2003 Std. x86.  My ontap version is 7.3.2P3.

PS C:\acs> Get-NaVirtualDiskAlignment -VirtualDisk C:\ClusterStorage\3PRT\scIDXTSE23\C_2010-03-06T082417.vhd | fl *

Size                 : 42947668480
VirtualDisk          : C:\ClusterStorage\3PRT\scIDXTSE23\C_2010-03-06T082417.vhd
StartingSectorChs    : (0, 1, 1)
EndingSectorChs      : (1023, 254, 63)
IsBootable           : True
PartitionType        : 7
StartingLba          : 63
SizeLba              : 83882165
SizeInBytes          : 42947668480
AbsoluteStartingLba  : 63
IsExtendedBootRecord : False
Ebr                  :
IsAligned            : False

[beam]

What is the exact nature of the error?  Does it come from Hyper-V, or is it inside the guest OS?  What are the steps that you must take before the VM will boot (that is assuming you are able to eventually get it to boot)?

The cmdlet does modify the NTFS boot sector and NTFS boot sector mirror for NTFS partitions that are bootable.  It does *not* modify the Boot Configuration Data (introduced with Windows Vista/Server 2008), which is why a rebuild of the BCD is necessary before a Windows 2008R2 Core guest will boot.  A Windows 2003 guest should boot successfully after the alignment without any further modification.