Bootable Media with UEFI (3TB volume target)
Hi.
I am trying to recover two 2TB volumes (they're not completely full) to two 3TB volumes on a dissimilar machine. The target machine supports UEFI while the source machine only supports MBR. I backed up the source machine to a TIB file on a NAS.
My question is, when I try to create bootable media using the Linux option and boot into the target machine for recovery, only 606.8 GB of the RAID 1 volume is visible to the recovery GUI. That means that I cannot target a 3TB recovery.
If I use WINPE 3.0 as my bootable media, the full 3TB volume of the RAID 1 (2 volumes) are seen but the machine will not boot after recovery. I get a non-system disk error. I think that is because WINPE does not convert the MBR partition to a GPT partition the way that it should. Linux bootable media has UEFI support for x64 machines, but if it only sees 606.8 GB of the volume then it becomes useless.
How do I solve this problem? Should I be using Linux Kernel Parameters? (I have heard that they can BRICK your motherboard though so I prefer not to use them). Or is there an option with WINPE x64 bootable media that will convert MBR to GPT automatically once the restore is complete?
Newbie with needed assistance...
Thanks in advance.
Can you use 64-bit WinPE 4.0 media (build on 64-bit windows) ? It should support conversion to UEFI. According to userguide, WinPE media based on WinPE prior to 4.0 don't support conversion to UEFI.
Can you use 64-bit WinPE 4.0 media (build on 64-bit windows) ? It should support conversion to UEFI. According to userguide, WinPE media based on WinPE prior to 4.0 don't support conversion to UEFI.
I'm glad you mentioned that option. I have tried it in the following way. I downloaded the Windows ADK (instead of the AIK for WINPE 3). I injected my RAID controller drivers into the bootable media ISO and burned the disc. However when I went to boot, a Windows 8 logo came up instead of a Windows 7 logo which I expected and then I got an error pertaining to one of the drivers that I injected into the bootable media.
Please provide me with some good steps to take in order to create winPE 4 bootable media for Windows 7 SP1 Ultimate. As far as I know WinPE4 is supposed to support Windows 7 SP1 x64 as well as Windows 8.
WinPE 4.0 is based on Windows 8. So if you created media using this ADK, it will display Windows 8 logo on boot. If it complains on drivers - check what drivers you use, as the ones from Windows 7 may not fit and drivers for Windows 8 are required.
WinPE 4.0 is based on Windows 8. So if you created media using this ADK, it will display Windows 8 logo on boot. If it complains on drivers - check what drivers you use, as the ones from Windows 7 may not fit and drivers for Windows 8 are required.
Does it even make sense to use Windows 8 drivers? Especially when I am trying to recover Windows 7 SP 1 Ultimate x64 ?
Drivers that are necessary for media itself are different from the drivers required for UR for the OS being recovered. If the media is based on WinPE 4 - you need Windows 8 drivers for it. What drivers you need for UR is determined by OS in the backup.
Drivers that are necessary for media itself are different from the drivers required for UR for the OS being recovered. If the media is based on WinPE 4 - you need Windows 8 drivers for it. What drivers you need for UR is determined by OS in the backup.
Thanks. This brings up a crucial point however. I just checked the drivers in question and they have the same filename for Windows 7 and for Windows 8. Where do I install the Windows 8 drivers and where do I install the Windows 7 drivers? At which stage of the Universal Recovery does this happen and at which stage of the WINPE media creation does this happen and which drivers for which step?
Drivers that are necessary for media itself are different from the drivers required for UR for the OS being recovered. If the media is based on WinPE 4 - you need Windows 8 drivers for it. What drivers you need for UR is determined by OS in the backup.
Hi. I tried creating bootable media from the Acronis Management Console. I got an error message "Failed to create the file" Error code 0x180000 . I saw somewhere you posted to delete a ~MntWIM folder or rename it but I could not locate this folder in my %TEMP% folder. The CMD console goes away too quickly to see what error messages are in there when creating the Bootable media ISO.
Try this builder to see more detailed error instead of 0x180000 - http://forum.acronis.com/forum/51965#comment-160935
Drivers that are necessary for media itself are different from the drivers required for UR for the OS being recovered. If the media is based on WinPE 4 - you need Windows 8 drivers for it. What drivers you need for UR is determined by OS in the backup.
I got a screenshot of the error during the CMD output. It states that the drivers are not properly signed. Use the /forceunsigned option to install the drivers.
How do I put this command into the WINPE process?
Instead of adding drivers using media builder, you can create a .wim with already injected drivers and the use it in media builder. Then execute copype command from ADK prompt, replace the default .wim file the the one with drivers and select 'use WinPE files from location I specify' on winpe source selection screen, and select 'media' subfolder from the folder structure creted by copype command.
Try this builder to see more detailed error instead of 0x180000 - http://forum.acronis.com/forum/51965#comment-160935
message in DISM log:
Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override.
How do I turn this switch on?
Instead of adding drivers using media builder, you can create a .wim with already injected drivers and the use it in media builder. Then execute copype command from ADK prompt, replace the default .wim file the the one with drivers and select 'use WinPE files from location I specify' on winpe source selection screen, and select 'media' subfolder from the folder structure creted by copype command.
Thank you that sounds like a good solution. The only thing is I do not know how to inject drivers into a WIM file. I will also need steps and full directory paths/file paths to the default wim from media builder and the wim that I create with the injected drivers.
Please advise. Thank you.
Instead of adding drivers using media builder, you can create a .wim with already injected drivers and the use it in media builder. Then execute copype command from ADK prompt, replace the default .wim file the the one with drivers and select 'use WinPE files from location I specify' on winpe source selection screen, and select 'media' subfolder from the folder structure creted by copype command.
I created a bootable WINPE 4 (windows 8) cd iso rom but it seems that the disk volumes are not recognized as they are in the WINPE 3 bootable media.
Please advise (I found out some steps on creating a WIM online but the steps may have skipped some crucial parts)
Looks like the necessary drivers were not injected into the wim file. You can use instructions for True Imag 2014 - http://kb.acronis.com/content/38917 for Dism command usage. After wim file is unmounted, you can use it in media builder.
That link prompts me to log in with knowledgebase credentials. Is there something that I can view without a login?
My bad, it's an internal article.
Briefly, you need to go to Start -> Programs -> Microsoft Windows AIK -> Deployment Tools Command Prompt , run from there
copype amd64 c:\winpe_x64
(you may use any folder name)
then mount .wim:
dism.exe /Mount-Wim /WimFile:c:\winpe_x64\media\sources\boot.wim /index:1 /MountDir:c:\winpe_x64\mount
add drivers:
dism /image:c:\winpe_x64\mount /Add-Driver /Driver:folder_with_drivers
and unmount it:
dism.exe /Unmount-Wim /MountDir:c:\winpe_x64\mount /commit