V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

hi there,

just wanted share experience manual p2v migration. vm became ressource hungry , decided move off esx 5 cluster dedicated physical machine.

v2p virtual machine physical server ibm x3650 m4 , switch bios uefi boot environment

task:
v2p migrate vmware virtual machine ibm x3650 m4 serveraid 5110e raid controller or other lsi raid controller without 3rd party tools.
should work other raid controllers or servers sure pick right drivers then.
task:
vm's boot environment/virtual bios bios, not uefi (as per default vmware setting). physical server running in uefi mode.

challenge:
after restore server won't boot or bsod (7b), because raid drivers missing.
after restore vm won't boot because boot environment has changed bios uefi

preparations:
existing physical server of same type , same raid controller , same os nice troubleshooting , checking registry.
existing dhcp server make networking things easier.
connect new physical server x3650 m4 power , network
    create virtual drive has @ least size of existing vm plus size of full backup (.vhd). should twice size of original vmdk.
usb flash stick (i used 8gb modell no problem larger sticks)
download , extract lsi megaraid driver on usb media (i used 6.705.05.00-mr_windows_driver directly lsi website)
download , extract intel network adapter driver on usb media (i used 12.11.97.0 of e1r62x64.inf 19.5 driver release 2014.09.26 directly lsi website)

step step:

if have other physical server of same type , same controller , same os:

1.    open regedit , export related scsiadapter , megasas2 .reg files or skip step , use files below
    some of (sub)keys may not accesible - first take ownership and/or modify permissions read them
    hkey_local_machine\system\currentcontrolset\control\class\{4d36e97b-e325-11ce-bfc1-08002be10318}
    hkey_local_machine\system\currentcontrolset\enum\pci\ven_1000&dev_005b&subsys_04121014&rev_05
    hkey_local_machine\system\currentcontrolset\services\megasas2
    this 1 more complicated:
    hkey_local_machine\system\currentcontrolset\control\criticaldevicedatabase (only relevant devices service name megasas2 - export whole subkey , filtering done tools notepad++)
    make copy of following files/folders:
    c:\programdata\lsi\
    c:\windows\inf\megasas2.inf
    c:\windows\inf\megasas2.pnf
    c:\windows\system32\drivers\megasas2.sys
        
on existing vm:

1.    create full backup (image) built-in windows backup utility , save in accessible network location (you need one, if goes wrong or want come point.
    alternatively create vmware snapshot.
2.    import .reg files created earlier or import files below.
    attention: make vm unbootable!
    but required prepare vm new raid controller when restored on physical server.
    do not reboot make vm unbootable!
4.    copy lsi folder , megasas2.inf/pnf/sys files appropriate destination folders on vm.
3.    again create full backup (image) built-in windows backup utility , save in other accessible network location not safed first backup.
    this "golden" backup if want, raid controller prepares. rebuild new machine second backup.
4.    optional: use backuputility restore systemstate of first backup , reboot or restore vmware snapshot.
    this undo changes made vm.

on new physical server:

1.    boot physical server windows server 2008 r2 sp1 dvd
2.    when ready install, press shift+f10 command prompt , not click install server 2008
3.    check driveletter of usb stick diskpart list vol (was c: @ server, don't wonder letter)
3.    load drivers serveraid sas controller (this mandatory see volume in diskpart)
    drvload c:\srv_2008_x64\megasas2.inf
4.    load drivers intel i350 gigabit nic's (you need access backup on network)
    drvload c:\pro1000\ndis62\e1r62x64.inf
5.    wpeinit (will start network. wait ~15 sec let start , ip address)
    check if have ip connectivity address ipconfig, if not, use other nic driver , repeat steps 4+5

6.    create efi , bcd
    diskpart
    list disk
    select disk x (where x number of disk convert)
    clean
    convert gpt
    create partition efi size=128
    format fs=fat32 quick label=efi
    assign letter=i or other free drive letter
    create partition msr size=128
    
6.1    copy efi bootloader efi partition
    i: (where letter of efi partition)
    mkdir efi\boot
    mkdir efi\microsoft\boot
    copy x:\windows\boot\efi\bootmgfw.efi i:\efi\microsoft\boot (where x ist default letter of current windows pe environment)
    copy x:\windows\boot\efi\bootmgfw.efi i:\efi\boot\bootx64.efi (note file renamed bootx64.efi)

7.    create new partitions
    diskpart
    create partition primary size=100000 (edit size needs. later become system drive of server)
    format fs=ntfs quick label=windows
    assign letter=y or other free drive letter
    create partition primary size=990000 (this temporarily store backup , need restore process)
    format fs=ntfs quick label=backup
    assign letter=b or other free drive letter
    exit

8.    map network drive , copy backup .vhd  local disk
    net use l: \\networklocation\where\you\saved\the\backup (enter credentials when asked)
        copy .vhd file contains os of vm local backup partition b. relevant vhd file largest file in fileset.
        note names - sure correct file!
    copy "l:\windowsimagebackup\vmname\backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" b:\
        give time, slow , take minutes/hours , not see progress! @ disk-led's see if still happening

9.    mount .vhd , copy it's contents new system partition
        note can mount locally stored .vhd. cannot mount .vhd in network location.
    diskpart
    select vdisk file=b:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
    attach vdisk
    select vol 5 (where 5 number of mounted vdisk)
    assign letter=z or other free drive letter
    exit

10. restore files image
    z: (where z letter of mounted .vhd)
    xcopy * y:\ /e /c /h /k /o /b /q /y (where y: letter of new partition label "windows")
        several "access denied" messages appear, ignore them. systemvolumeinformation folders.

11.    create boot configuration data (bcd)
    bootrec /rebuildbcd
        this try repair missing bcd on second of 2 small partitions created earlier in , should work, otherwise you'll have create bcd manually (search google procedure)
        note may find more 1 windows installation , ask sould added boot list. sure select 1 in correct volume (y:\)
    that's - exit dos command box , close "install windows" window, after prompt reboot.
    select "start windows normally", if windows error recovery appears.    
    
12. preparing windows
    when windows boots first time, not reboot if asked, won't come @ stage!
    install intel chipset drivers server (i used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" ibm website)
    open device manager, uninstall "raid-controller" exclamation mark. cannot install correct driver device @ point, bring error: "cannot create stable subkey under volatile parent key"
    once again, not reboot!
    in device manager select action>add legacy hardware
    click next
    select hardware manually
    select storage controller type
    lsi should listed, select "lsi megaraid sas 9281-8e"
    click next, ignore error "code 10" message.
    click done.
    rightclick lsi megaraid sas 9281-8e device exclamation mark in device manager
    select update driver
    select browse computer driver software
    select let me pick list of device drivers on computer
    select "have disk"
    browse folder extracted raid driver 6.705.05.00-mr_windows_driver located (e.g. usb flash stick e:\6.705.05.00-mr_windows_driver\srv_2008_x64)
    then unselect "show compatible hardware"
    on right side, scroll , select "ibm serveraid m5110e sas/ssata controller"
    ignore update driver warning , click yes
    click next, ignore error "code 10" message.
    ignore exclamation mark on "ibm serveraid m5110e sas/ssata controller" in device manager sure there controller , no other raid-controller or lsi sas controller listed under "other devices" or "storage controllers"
    now safe reboot
    after reboot find 2 "ibm serveraid m5110e sas/ssata controller" in device manager
    rightclick , uninstall 1 exclamation mark. not tick checkbox remove driver well!
    
you're done!! (hopefully)

windows registry editor version 5.00  [hkey_local_machine\system\currentcontrolset\services\megasas2] "start"=dword:00000000 "type"=dword:00000001 "errorcontrol"=dword:00000001 "imagepath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\   72,00,69,00,76,00,65,00,72,00,73,00,5c,00,6d,00,65,00,67,00,61,00,73,00,61,\   00,73,00,32,00,2e,00,73,00,79,00,73,00,00,00 "group"="scsi miniport" "driverpackageid"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7" "tag"=dword:00000041  [hkey_local_machine\system\currentcontrolset\services\megasas2\parameters] "bustype"=dword:00000008  [hkey_local_machine\system\currentcontrolset\services\megasas2\parameters\device] "enablequeryaccessalignment"=dword:00000001  [hkey_local_machine\system\currentcontrolset\services\megasas2\parameters\pnpinterface] "5"=dword:00000001  [hkey_local_machine\system\currentcontrolset\services\megasas2\enum] "0"="pci\\ven_1000&dev_005b&subsys_04121014&rev_05\\4&127e0079&0&0012" "count"=dword:00000001 "nextinstance"=dword:00000001  

Windows Server  >  Migration