BSOD after Image deployment with Snap deploy Universal Restore

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

Hello

I have imaged a laptop with Snap Deploy 3 to use as our base image to deploy to multiple machines. The base laptop was a single core with an IDE hard drive. If I deploy the image to dissimilar hardware, the laptop/pc will not boot up after deployment. MY test laptop is a dual core with a SATA hard. We purchased universal deploy under the impression that deploying to dissimilar was easy but I am not finding this to be the case. I appreciate that I need to add drivers etc, but I thought that Universal deploy would at least deploy the image so the target machine boots up? Am I missing some steps when deploying from IDE to SATA?

Tue, 06/15/2010 - 13:51
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Paul,

Thank you for posting and welcome to our forum! I will definitely help you with this.

You are correct in assuming that you are missing a step when deploying from IDE to SATA? When deploying to dissimilar hardware, you will need to provide hard disk drive controller or chipset drivers in either one of these formats: *.inf, *.sys or *.oem. You can always get them from your hardware manufacturer's website. If you have some problems with locating the necessary drivers, please let me know and I will help you.

Acronis Universal Deploy uses three sources for drivers:
- the Windows default driver storage folder (in the image being deployed)
- the mass storage device driver specified by the user
- the driver repository - a folder or folders on a network share or removable media.

If it fails to find the proper drivers, the deployed machine will fail with a BSOD error: 0x0000007b or it will be rebooting constantly.

I can suggest two sources of information that will assist you with this issue. You can check this thread where we have a similar discussion, please do not be put off by the name, Acronis Universal Restore works similar to Acronis Universal Deploy.

There is also Chapter 9.2.10 Using Acronis Universal Deploy in our User Guide which is available on page 59, it has a step-by-step tutorial for using Acronis Universal Deploy. The User Guide is available here.

I would really appreciate if you can keep me updated about your progress and let me know if you have additional questions please.

Thank you.

Tue, 06/15/2010 - 15:48
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

Hello

Thank you for your response. I have tried adding the drivers as you suggested but am still not having any luck. My test machine is an HP nx7400 laptop. I have downloaded the chipset and SATA drivers for this particular model. I have put the inf files in a folder on our network. On the driver location screen I have ticked the box to search in a specified location (In this case the folder containing the drivers). When I deploy the image I can see that the drivers are found and downloaded, but the laptop still blue screens. I know these drivers work as I have used them in the past for a manual build.

Do I need to add any other drivers?

Wed, 06/16/2010 - 11:24
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Paul,

Thank you for replying.

Can you please clarify if the BSOD error is indeed 0x0000007b?

If this is the case it means that either, improper drivers were provided or somehow, they were not injected properly by the Acronis Universal Deploy. I would recommend to contact our support directly with the following log files. I am confident that our support engineers will be able to resolve this problem.

 - Collecting Acronis Snap Deploy Agent Operations Log

I will also send you a private message with a unique download link, so that you can create another report from the unbootable machine and forward it to our Support team as well.

Please let me know if you have additional questions.

Thank you.

Wed, 06/16/2010 - 12:21
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

Hello

I have tried to test with other drivers but I am having a new problem now. I am using PXE to deploy images as per Acronis recommendation. PXE had been working fine but now when I try to deploy an image, the snap deploy management console locks up and the image is not deployed. I am able to see the laptop ready to deploy and I can setup a template etc, but when deploying the console freezes. I have not changed anything on the system. One thing I have noticed is that If I look on the license server, it is showing most of our licenses as being used even though they are not. I am wondering if this could be causing an issue. I have tried to remove the licenses and re-add them but I get an error message when removing the license.

Tue, 06/22/2010 - 14:40
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Paul!

Thank you for keeping us posted and for reporting about new issue.

There can be several reasons for this case, so we will have to localise the issue. I'm quite positive that it's not related to the License Server as in case there were the lack of licenses, Console would work just fine, but the target machine will continue to reboot. This is either the network issue or bootable components problem. Let's do the following:

I will send you the instructions regarding bootable components update. Please follow the instructions and see whether the issue persists. Should it be present, please gather this information:

  1. Wireshark output
  2. Acronis Info
  3. OS Deploy Server logs
  4. OS Deploy Agent logs
  5. Acronis Linux Report from the PXE (press ctrl+alt+f2 on very booting and then follow any of these instructions)

After that please either send this information to us or contact support directly with the information attached. Should you decide to contact support, please keep in mind that should there be any procrastination with the reply, you can always specify us the case number. We will do our best to speed up the process.

Thank you in advance for cooperation and patience! We will be waiting for news from you.

Tue, 06/22/2010 - 16:11
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 4

Hello

I have got PXE to work intermittently but I think it's an issue with e PC it's installed on. However I am still getting a BSOD with the incorrect driver error code. I know that am adding the correct drivers as I have downloaded them from the HP website. I have then built up the laptop manually and noted down the driver names from device manager. Now I may be adding the drivers in the wrong place or not adding enough drivers. In my template I am using Universal restore, and I am adding the chip set driver on the Mass Storage Device drivers screen. When I select the correct .inf file I can see the correct serial ATA driver listed in the drivers list. But I still get a BSOD. Am I adding the drivers in the correct place? Do I need to add more than the chip set drivers? I have seen a HAL driver mentioned previously? Do I need to add this as well or should the chipset do?

Thu, 06/24/2010 - 10:28