Skip to main content

SnapDeploy3: problems deploying to IDE hdd's with version 3329

Thread needs solution

Good day,

i'm testing snapdeploy3 version 3329 prior purchasing it.

i've managed to make master images of win7 pro and winxp sp3 out of my new intel H55 based chipset PC. (original computer for master image had SATA drive)
i also managed to deploy those master images on other computers just fine but ONLY for computers with SATA drives!!!!
In case of IDE drive on target computer system reboot on the beginning of deployment with

0x330004 failed to create partitions structure [0]

error. I've tried several 100% WORKING ide hdds (maxtor, seagate) and several different computers - the original one based on intel H55, the older one based on intel G31 and the old one based on intel i945. Everywhere ide hdd's were detected and are working properly. i also able to install OS manually on those computers just fine...

Please assist.
as far as i remember my previous experience with snapdeploy, deployment to IDE was working perfectly.

---
Sincerely,
Vladimir Nikiforov.

0 Users found this helpful

$%^HGY^%&!!!!!!! I'm VERY sorry! My fault!!!! It was misconfiguration in template being used under deployment options - it was disk utilization as in master image not occupy disk space entirely! sorry!!! :(((((

Dear Vladimir!

Thank you for joining us and for finding time to open the thread!

I'm glad to know that this inconvenience was successfully resolved - thank you for finding time to notify us!

Should you face any issue or have any questions - feel free to leave a comment here, and we will be glad to help you!

Thank you for visiting!

Hi ! supporter,
I have mistake same Vladimir (0x330004 failed to create partitions structure [0] ) , I had chose option in disk utilization is "as in master image" or "occupy disk space entirely" but it is not work , When I start to deploy to target PC it goes for like 3 seconds and then reboots the PC, forward to support from you
thx u.

 Hello Nguen!

Welcome to our Forum, we're glad to greet you here. I understand your concern and will be glad to help you. 

There are several possible reasons for the reboot of the target machine: 

  1. Not enough free licenses (or Upgrade + Full licenses pairs)  in the License Server
  2. Connectivity issue
  3. Agent glitch

In order to localise the issue and find an appropriate solution we will need some additional information. Please gather the following data: 

  1. Screenshot of the License Server
  2. OS Deploy Server logs
  3. Agent logs
  4. Acronis Info from the machine hosting Management Console, OS Deploy and PXE Servers

After that please kindly contact support directly with the information attached. 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.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!