USB boot media UEFI issues with SD4U1(540)
I had hoped that the new UEFI support in Snap Deploy 4 Update 1 build 540 extended to the USB boot media, but it does not work on my test systems.
Created new USB bootable media with Snap Deploy 4 Update 1 (build 540)
Systems: Lenovo X1 Carbon and Lenovo X230 (results are same on both)
BIOS mode: Legacy = USB media boots normally & opens Snap Deploy
BIOS mode: UEFI = error message immediately after choosing USB media:
Runtime exception 'Failed to detect graphic output mode' code 21495812, tag 0x089328c5c20a9047
This error message has been reported with ATIH 2012 on a Sony Vaio S in UEFI mode as well:
http://forum.acronis.com/forum/33773
One suggestion from Acronis in that forum suggests hitting F11 then entering a command:
http://kb.acronis.com/content/2921
However, this does not apply as the boot process is failing at the boot loader, not within Snap Deploy/ATIH itself.
Another suggestion in that forum was to use the YUMI boot loader tool together with the .iso version of the Acronis USB tool, but YUMI doesn't seem to work in UEFI mode. It worked fine in Legacy mode.
So I'm back to the old trick of changing the BIOS mode to Legacy, applying the image, then changing back to UEFI. (Note that it's actually quite a bit more complex than that.)
I'm able to boot to SD4U1 (540) on multiple generations of Lenovo X1 Carbon machine, but I am getting very different behaviors...
For the newest model, I get the attached screenshot's behavior.
For the older X1 Carbons, I can see the partitions on the external drive, including the data, and deploy as expected. (circled in screenshot)
I have tried adjusting the USB legacy boot modes... but no change in behavior. I know the USB drive is working because it is housing the Acronis Snap Deploy image (meaning I can consistently boot every machine, just not get the data volume to be seen once booted). I am at a loss. Any ideas? Should I be submitting logs of some sort?
Hi,
I want to create a bootable USB Harddisk to load acronis image captured through snap deploy 4. I created the ISO image and writing it to USB but it does not become bootable. I am using HPZ600 workstation with bios configured to boot with USB Hard disk but I am getting errors like invalid partition table.
I tried with grub4dos also but it does not work with that too.
In the forum I found a post that the USB hard disk should be formatted with FAT32 and tried formatting with Diskpart but it does not allow for larger volume hard disk and giving virtual disk service error: the volume size is too big error. I somehow managed with acronis application to format the hard disk with fat32.
It looks like nothing is working, can anyone help me regarding creating the bootable USB harddisk?
Hi All,
Thank you for posting this question in our forum. I am happy to assist you.
When using an USB stick for booting, please ensure, that the stick is bootable before using with Acronis Bootable Media Builder. If you are creating a WinPE media, please ensure, that you only apply 32-bit drivers for the boot media. See
Acronis Bootable Media: Use Only 32-Bit Drivers for WinPE-Based Devices Recognition
If you need additional assistance, please create a system report of the affected machine and contact support. You will find all available support options in our Customer handbook.
If there is anything else we can do for you, please let me know.
Thank you.
I'm having a strange issue. I am using Snap deploy 4 standalone master Image creator on a dell E6230 Windows 7 64 bit (UEFI). The HD I know for a fact has 3 partitions but when I used the master image creator I only see two partitions to clone. This creates a massive issue when I take that cloned image to another machine (Also UEFI). I get a missing MBR.. Issue with this machine is UEFI and has GPT not MBR... So my question is what do I have to do to find, then copy all three partitions?
Hello Shane Tatham,
Thank you for posting this question in our forum. I am happy to assist you.
Have you seen this information from our Web Help? Please ensure, that your GPT drives are not from type 'dynamic'. This kind of volumes could not be included into the master image.
If you need additional assistance, please create a system report of the affected machine and contact support. You will find all available support options in our Customer handbook.
If there is anything else we can do for you, please let me know.
Thank you.