PDA

View Full Version : Bootable Rescue Media Fails

metusmons
July 4th, 2007, 12:17 PM
Hi Guys,

I am testing the ability of the trial version of Acronis Snap Deploy 2.0 to deploy an Image over a coorporate network. I have full intent on buying this product (well for the company to buy it :P) if it w2orks ou but am having some issues.

I have created my image from a newly installed WindowsXP SP2 build with all the relevant development packages, all correctly licenced. This image is hosted on the network.

My problem is that when I run the 'Rescue Media' CD I get the following error:

Loading Please Wait ...
Kernel Bug at AMD74xx.c :451!

My second question is am I going about this the right way for what I need?

Thanks all!
Acronis Support
July 5th, 2007, 12:58 AM
Hello metusmons,

Please make sure you use the latest build (2135 ) (http://www.acronis.com/enterprise/support/updates/) of Acronis Snap Deploy 2.0. To get access to updates you should first register (http://www.acronis.com/enterprise/registration/) your software. Don't forget to recreate Acronis Bootable Rescue Media after updating.

If the issue persists, please collect some information to let us investigate it thoroughly:

Please create Linux system information (sysinfo.txt) as it is described in Acronis Help Post (http://wilderssecurity.com/showthread.php?t=55317).

Then submit a request for technical support (http://www.acronis.com/enterprise/my/support/). Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with a solution.

P.S. I've moved your thread to the appropriate forum branch.

Thank you.
--
Marat Setdikov
metusmons
July 5th, 2007, 09:51 AM
Dear Marat,

I have the latest trial version of Snap Deploy, are there any updates for this? I can't register the trial but I have contacted your support directly regarding this!

As for the sysinfo.txt I do not get far enough in to the boot so I can not do this, the boot fails at the first step in command line.

Any suggestions?

Thanks