We were told by NetApp to run the MBRALIGN on our servers. Seeing this as a LOT of work, I decided to do it first on our Windows 2003 template so that at least any NEW VMs would have correct alignment. I started in our LAB first before attempting production.
So I scanned the VMDK files in our lab and indeed it flagged the template VMDK file as not being aligned - cool...so far so good. The template was off, obviously cause its a template, and had no snapshot. I ran the alignment process on it and after about 45 minutes it completed, 100%, no errors.
I converted the template to a VM this morning to power it up and make sure the OS was still OK before I deleted the backup files the alignment tool created. I get this error:
Error Loading Operating System.
I also could not edit the VM in Virtual Center. It gave me this error:
The server fault 'SystemError' had no message.
Call "PropertyCollector.RetrieveContents" for object "propertyCollector" on vCenter Server "ourservername" failed.
Cool - love it....
Does anyone know what might cause this or what might have gone wrong? Was I not supposed to run this on a template? Should I have converted it to a VM first before running the alignment tool on it?
I am running the Host Utils version 5.2 (where mbrscan has been merged into mbralign) and ESX 4.0 in our lab. I am running vCenter 4.1, but our lab is ESX 4.0 still. None of our lab environment is running on NetApp (yet) - but I was told the alignment problem is a global issue with both physcial and virtual servers running on ANY type of storage. My understanding was the MBRALIGN could be run on any storage backend - not just NETAPP. But we are planning on migrating to NETAPP and so that is what started this whole thing.