Skip to main content

Runtime Error 0x1480012

Thread needs solution
Beginner
Posts: 1
Comments: 3

Hi,

I recently joined this forum because of one specific problem we encounter for a few days now.

We are about to roll out new workstations with their specific storage setup beeing:

Main: 1 SSD for System

Secondary: 2 HDD RAID 0 (LSI SAS2 MPT Controller) for Data

All UEFI

For OS Distribution we are using Acronis Snap Deploy 5 on Windows Server 2012 R2 (latest Updates applied on OS and Acronis Snap Deploy 5)

-----

The Problem: booting via PXE Server, the client connects correctly to our Acronis Server and provides the four options: Acronis Snap Deploy 5 Master Image Creator, Acronis System Report and Acronis Snap Deploy Agent.

But no matter which option we choose: each returns the same error:

Runtime error:
Error 0x1480012
| line info: 0x76df0d19c4c8565a
| $module: bootwiz_efia64

Any previous machines do not have any trouble; all of the Options work fine. And since I wasn't able to find anything about this specific error on the web or in this forum, I'd really appreciate any help.

Thank you very much in advance!

Martin

 

 

 

0 Users found this helpful
Forum Hero
Posts: 70
Comments: 8346

Martin, it may be that the network drivers are not loaded with the Acronis Linux environment kicks in.  Version 1660 seems to be lacking drivers for some of the newer intel NICs.  1662 beta brought in those drivers.  1666 beta brough PCIE NVME support. There is no "official" version newer than 1660 and I'm not sure why that is.  However, 1666 appears to be exactly the same as 1660, but with the better driver support.  I'll send you a PM with the link if you want to give it a try.

Also, the error is showing that it is unable to run the UEFI 64-bitloader.  Are you pxe booting using legacy PXE or UEFI PXE?  You may want to ensure both options are configured in your PXE server and try both options to see if one works better than the other with these newer systems.  If possible, makes sure that legacy/CSM boot is enabled on these systems as well... if you are trying to legacy PXE boot on a UEFI only system, this could be another issue. 

Beginner
Posts: 1
Comments: 3

The Server loads the UEFI PXE, at least it says so before loading the menu. Thank you for the drivers, I'll have a go with them later that day.

Beginner
Posts: 1
Comments: 3

Same problem with v. 1666. In fact, I do not even need to choose any option to get the error. It comes up by itself after a few seconds.

See attached photo for reference.

Attachment Size
389711-133150.png 704.6 KB
Forum Hero
Posts: 70
Comments: 8346

So this error only occurs on these machines, but not others, correct?  What is the make/model of the PC's?

Do any of the other machines have a hardware raid as well?   I am guessing here, but thinking the default Linux media may be choking on the RAID controller as it won't have the necessary drivers.  In Snap Deploy 5, you can create a .wim file and upload it to the server as a boot option too.  You would want to be sure that the IRST driver and/or any specific hardware RAID controller drivers are injected into the .wim.  FYI, it usually takes a lot longer for the .wim files to copy into RAM and mount so be patient if it looks like it's taking a lot longr than usual.

Alternatively, have you tried the offline recovery media booting from a flash drive or DVD and using both the Linux media and the WinPE media to see if you can start the process on one of those instead?  I have a feeling you'd stukk need to use WinPE for the RAID controller as the Linux media won't have the necessary IRST drivers or any special controller drivers.

Beginner
Posts: 1
Comments: 3

Hi Bobbo,

first of all, sorry for the long delay. Other projects kept us occupied until now.

Thank you very much for your suggestions, it worked exactly as you said. We added the IRST driver as well as the network driver to a new .wmi file and botted from this. Worked like a charm and now we got our image distribution back running as intended.

Thank you very much for your support and have a good one!

 

Forum Hero
Posts: 70
Comments: 8346

Hi Martin,

Happy to help and glad that that adding the drivers to a .wim file allowed things to get back on track!

HT
Beginner
Posts: 0
Comments: 1

Hi Bobbo (and anyone else who might help),

I have a problem somewhat similar to Martin's. My problem is how to recover data that was backed up to a Seagate external hard drive (Seagate). I had used the backup software that came with the drive (DiscWizard, which is associated with Acronis). The backup was made from an old Dell computer running Windows 7, done on a weekly basis, the last one on August 20, 2017. These backup files are .tib files, with automatically generated names in the style of "Entire Internal Hard Disk_inc_b1_s121_v1".

The old computer recently died (would not reboot). I have got a new one (HP Pavilion 510, running Windows 10 Home), but cannot restore the data from the .tib files on the Seagate drive to this new computer. I tried two versions of DisWizard: a Serial-Number-Specific version (an older version) and then their latest version.

The older version of DiscWizard would run fine until it prompts me to restart the computer. But at the start of the restart I get the error message Martin also encountered:

 

Starting Acronis UEFI Loader(x64)(v.1.1.36)…

Runtime error:

Error 0x1480012

| line info: 0x76df0d19c4c8565a

| $module: bootwiz_efia64

  

Then the computer completes the restart, but with no data whatsoever restored.

I contacted Seagate and they gave me some generic instructions, including downloading and running their latest version of DisWizard. But this version does not clearly include a tool for data recovery. Only two tools seem possibly relevant. One is CLOSE DISK, which I do not want since I want to keep the Windows 10 on my new computer and not clone the old computer's Windows 7. The other tool is ACRONIS UNIVERSAL RESTORE, but I would have to upgrade to and pay for Acronis True Image in order to use it. I would not mind doing this if I can be sure that it would enable me to recover the data, but a few quick searches appear to indicate that this tool is for something quite else.

I am not a computer-savvy person. The data on the Seagate drive is very important to me. But I would like to see if I can recover it before taking the costly option of sending it to a lab for recovery. Any help on this would be greatly appreciated! Thank you in advance!

Best wishes,

Hao

Forum Moderator
Posts: 239
Comments: 6973

Hello HT,

You may want trying to restore your backups using a trial bootable media of Acronis True Image 2018, here the direct link to the bootable media in a trial mode (only restore functionality available)

http://dl2.acronis.com/s/AcronisTrueImage2018_trial.iso

How to burn a bootable media

You'll need to adjust the boot order to allow booting from an Acronis media. 

One key point about doing either a restore or a clone, is that the Acronis bootable Rescue Media should be booted in the same mode as is used by your Windows OS to boot, i.e. if Windows uses the EFI bootloader (has Secure Boot), then you should use the same for the Rescue Media.  See webpage: Check if your PC uses UEFI or BIOS for guidance on how to check the boot mode. Here the additional information on how to select the correct boot mode