Skip to main content

Can't create Rescue media builder

Thread needs solution

Hi. I had a crash that rendered ATI unusable. I reinstalled it but lost all of the configuration including access to the backups. I tried to create Rescue Builder on a USB drive which won't run and reports a Runtime error 0x1480011. I tired to restore an image via the reinstalled ATI but I can't get it to point to the tibx file stored on a NAS. So I'm stuck.

Any help appreciated

Dayle...

 

 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hi Dayle,

I'm sorry to hear about the technical issue you are experiencing. Here are some steps you can try to resolve the issue:

  1. Verify that your computer meets the minimum system requirements for Acronis True Image 2021.

  2. Check that your USB drive is formatted correctly and has enough free space to create a rescue media.

  3. Try creating a rescue media using a different USB drive or DVD.

  4. Check that the NAS is accessible from your computer and that the network connection is stable.

  5. If you are still unable to restore the image from the NAS, try copying the image file to your local hard drive and then restoring it from there.

  6. If it fails to solve the issue, Create WinPE bootable media and perform a restore.

    Refer to the kb article for more info on how to create bootable media.

    https://kb.acronis.com/content/69472

    Refer to the kb article for more info on how to restore from bootable media.

    https://kb.acronis.com/content/69427

If none of the above steps help to resolve your issue, feel free to contact our support because the issue may require an investigation https://kb.acronis.com/content/8153

I hope this helps!

Hi Jose

Since I started this thread, I have advanced a little. At this stage the “Simple” media creation stalls at boot up. The “Advanced” media creation boots but I cannot find a way to invoke the network drivers so I can’t see the NAS and the tibx file.

In response to your suggestions:-

1. Yes it does. I’ve been running ATI for many years on numerous computers (10 over two accounts) including this one without problems. However I haven’t used the media creation option for a number of years.

2. Yes one 16GB (USB 3) and one 32GB (USB 2). Both formatted with FAT32.

3. See 2 above

4. Yes I access it regularly from this PC.

5. I’m copying one of the tibx files to a spare local drive as I type.

6. I’ll give those a try after I restore the local TIBX file.

 

I’ll report my findings. Thanks for your help.

Dayle…

I’ve been running ATI for many years on numerous computers (10 over two accounts) including this one without problems. However I haven’t used the media creation option for a number of years.

What rescue media are you using if you haven't used the media creation option for years? With .tibx files you must create rescue media that understands that new format, i.e. ATI 2021 media, plus if you have a non-standard network controller you will also need to inject drivers for the same if you cannot see your local network from the rescue media.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hi, everybody, good afternoon, and thank you for the comments.

Regarding the issue you reported

That behavior is described on the KB mentioned during the last day:

https://kb.acronis.com/content/69472

On the KB, please choose the TAB that says:

*** If you select advanced media creation ***

---- For better compatibility with your hardware, you can select drivers to be added to the media. Because finding the right drivers can be time consuming, you can skip this step, finish creating a bootable media, try and boot the computer from it and see if the disks / network / NAS are detected successfully in the Recovery's "Browse" dialog window. If some hardware is not detected, re-create the bootable media, this time not skipping this step and adding the drivers. ----

So on this step you have the option to add the drivers.

If there is any issue with that, you can always try the following options: 

  1. Manually load the network drivers: If the network drivers are not included in the bootable media, you can manually load them from a USB drive or CD/DVD. Acronis True Image 2021 allows you to load additional drivers during the startup process by pressing the F11 key. You will be prompted to select the driver file from the USB drive or CD/DVD.

  2. Use a different bootable media: If the above steps do not work, try creating a new bootable media using a different USB drive or CD/DVD. Sometimes, the issue may be caused by a faulty USB drive or CD/DVD.

If the issue persists, I strongly recommend to raise a support case with us so we can troubleshoot the issue properly and provide an accurate solution https://kb.acronis.com/content/8153 .

Thanks in advance.

The MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.5.2) can also be used to identify the correct network drivers (and to create custom rescue media to include them).

Hi again

Just to clarify, I'm using the latest Rescue Media from ATI 2021.

So at this stage I came very close to losing everything. I finally managed to get an SSD in a USB caddy, copied a tibx file from the NAS and plugged it into the PC as an external device. The latest backup wouldn't install for some reason and I used one that was 3 weeks old.

Now to the problem. Despite finding and attaching all the drivers from the motherboard manufacturer, RM didn't run at all. Removing all but the LAN driver, still didn't help, but RM did run at least. I had no network access and certainly no NAS visibility. Even using its IP address didn't help. I do know in previous versions I have been able to access a NAS. Recovering an image from within Windows isn't a problem as the NAS is visible, which is to be expected. My circumstance is that I have 9 PC's (not all mine) that all back up to NAS's and at this stage recovering from a disaster is not going to go well other than the method I used. What I need help with is obvious NAS/network access if anyone can think of what the problem might be. For the record, this is a desktop and as a test, I ran the USB boot drive on my HP laptop and still didn't see the NAS. 

One more thing, I raised a ticket with ATI on Wednesday but I've not had a response. 

Cheers

Dayle...              

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hello Daylef.

I'm sorry to hear that you haven't received any contact from our side.

I have relayed the situation to the appropriate team, and we will do our best to assist you in resolving the issue.

Thank you for keeping us informed and for your understanding.

 

Dayle, have you tried using the MVP Assistant tool for creating rescue media?  If not, then I would recommend doing so.

Adding too many drivers to rescue media can cause issues the same as not having the correct drivers.

One feature of the MVP media builder tool is the ability to analyse your system for drivers then offer a selection of drivers that you can choose whether to install or not, along with those which it is recommended be installed.

The tool can be used in E Z mode where there are minimal selections for the user to make, or else in Advanced mode with full control over all selections.

One advantage of using the MVP created rescue media is having a WinPE desktop with a Windows Terminal option.  In that option you can run commands such as:

ipconfig /all   to check that you have a valid network connection.

ping 192.168.0.29   to check that your NAS is reachable on the network (using your own IP address)

net use S: \\192.168.0.29\Backup /user:Name Password   to mount a Windows drive letter, S: to your NAS backup storage folder (using your IP address, folder and user credentials).

See the following images showing my own rescue media doing the above for ATI 2021 and my NAS.

All. As an update, ATI have advised that they will no longer support 2021 despite an indication on the site that they will help with recovery issues. A very poor outcome in my opinion. The move to subscription based products is obviously the motivator. At least we have this forum.

Cheers

Dayle...

 

 

   

Hi Steve

I don't seem to be able to attach a jpg file but trying to create a boot USB using the "Build" tab in Advanced mode is greyed for the USB drive. Trying to do the same thing in EZ mode shows the Boot USB drive but it does nothing. 

Cheers

Dayle...

 

   

Dayle, have you checked the size of the ISO file that the MVP builder creates and compared this to the size of your USB drive?

The forum File Upload option is broken at present but you can still embed images using the Imce File Manager option (to the left of the YouTube icon).

Hi all

I have been in contact with support after purchasing a subscription to CPHO, however we've had zero progress. I'm now 11 weeks without a USB boot that will work. One agent actually managed to create one using NTFS format but I can't replicate how he did that. Consequently I get the same CMD screen after boot and no progress using Rescue Media Builder (either Simple or Advanced). Trying Universal restore got me three options on the boot screen 1. UR. 2. CPHO and 3. System Report, none of which did anything other than give me an error (Runtime error 0x1480011. Line error 0x76df0d19c4c85653. $Module: boowiz_ef ia64). Despite all of that, I have made a couple of discoveries. 1. I was using a 128gig USB drive which formated to 32gig with a partition, using FAT 32. That seemed to create the error above. Changing to a 16gig did work. 2. RMB simply doesn't work, it just produces a blank CMD screen (using the 16 gig drive). 3. UR does work, but it doesn't find a network card.

So I'm still in their hands but I wanted to feed back to you guys. Fingers crossed.

Dayle...      

OK a major step forward. I have an HP Laptop (I7 intel running Windows 10 home) and a desktop running an Asus ROG mother board (I7 intel running Windows 10 Pro). The HP only has WiFi (no ethernet port) and the desktop has both. For the hell of it, I shut down all the internal network devices and plugged in my D Link USB 3 to ethernet gigabit converter. Booting into UR and CPHO finds the network and the NAS on both PC's. I would suggest that for some reason The boot drive doesn't load the internal network drivers but it does for the external USB device. I did in fact untick the "Allow the computer to shut down the device to save power" option for the NIC but that didn't help.

So "go figure". I still want to know why I can't use internal NIC's so I'll keep the pressure up but at least I have a solution, just not the one I wanted.

Cheers        

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Daylef wrote:

OK a major step forward. I have an HP Laptop (I7 intel running Windows 10 home) and a desktop running an Asus ROG mother board (I7 intel running Windows 10 Pro). The HP only has WiFi (no ethernet port) and the desktop has both. For the hell of it, I shut down all the internal network devices and plugged in my D Link USB 3 to ethernet gigabit converter. Booting into UR and CPHO finds the network and the NAS on both PC's. I would suggest that for some reason The boot drive doesn't load the internal network drivers but it does for the external USB device. I did in fact untick the "Allow the computer to shut down the device to save power" option for the NIC but that didn't help.

So "go figure". I still want to know why I can't use internal NIC's so I'll keep the pressure up but at least I have a solution, just not the one I wanted.

Cheers        

Regarding the NIC detection the most likely reasons usually are:

- the Acronis Bootable Media does not have drivers for the respective hardware

- there is hardware malfunction/specifics due to which Acronis modules can't get access to the device.

I am sorry for the delay in getting a response from our support. I've contacted the team regarding this situation. You can expect a reply from our side.

Thanks in advance!

 

Daylef,

Your issue here is that of needing to use a wireless connection to your NAS deivce rather than a wired ethernet connection which you have discovered.  This issue is not due to anything related to the rescue media (RM as you put it) itself but rather is an MS shortcoming.

MS PE environment does not natively support wireless connection.  In order to achieve a wireless connection using a rescue medium you must use the MS WinRE based media so that wireless support is available.  You must then create or run a wireless profile after booting the RM to see and gain access to your NAS.  This is not a straightforward process unfortunately.

Your best solution is, as you have already discovered, to use a USB to Ethernet adapter for network connectivity.