Direkt zum Inhalt

PCs reboot while waiting at PXE Snap Deploy screen waiting for an image to be sent

Thread needs solution

When I reimage a lab, I have to boot every PC to the PXE server and then select snap deploy and the PCs just wait for me to go to the server and send an image out. It's always been a problem but has gotten increasingly worse lately. It takes 10 minutes or so to get 30+ PCs waiting for an image to be sent. Suddenly after a few minutes, 5 PCs of the 30 will just reboot. How do I troubleshoot why PCs will just reboot while waiting? It gets very frustrating.

0 Users found this helpful

When I reimage a lab, I have to boot every PC to the PXE server and then select snap deploy and the PCs just wait for me to go to the server and send an image out. It's always been a problem but has gotten increasingly worse lately. It takes 10 minutes or so to get 30+ PCs waiting for an image to be sent. Suddenly after a few minutes, 5 PCs of the 30 will just reboot. How do I troubleshoot why PCs will just reboot while waiting? It gets very frustrating.

Actually I forgot to mention the most annoying part of the whole situation. I put in a previous forum question about why our new PCs didn't work with the Acronis server at all. http://forum.acronis.com/forum/20367 They mentioned we're entitled to free upgrades. So I upgraded our Acronis Snap Deploy to the latest version. Well the new laptops work now. But the upgrade introduced a new problem. When you boot up to the PXE server and they just sit there, if the PCs reboots at all, whether I reboot it or it reboots because of whatever is happening in my request above, the PC is non-bootable. I haven't even started an image going down to the PC. It just boots to the PXE server, sits there and waits for an image. Never receives one, reboots, and the PC is non-bootable. It comes up to a screen saying something to the extent "Windows has recovered from a serious error. Try rebooting and selecting repair." Why would the PXE server be destroying every PC that boots to it now since the upgrade?

Hello David,

Thank you for getting back to us. I will do my best to help you with these issues.

It is possible those 5 PCs reboot because of some hardware or network issue. Could you try toggling multicast/unicast settings in the network utilization tab during deployment template creation? (please check page 63 from our user guide for details).

To understand why the computers become unbootable we will need to study Acronis reports collected from the computer before and after the issue occurred. Acronis 51 is used for unbootable machines.

If you could get back to me with the results I would really appreciate it. You can always contact our Support team directly with the same reports and mention this forum thread.

Please let me know if you have any other questions.

Thank you.

What do I run the report on? The server or the workstations? If it is the workstations, how do I get a report before and after on the workstations? When I reimage a lab of 40 computers, maybe 5 have the problem. It could be any of the 5. So I'd have to run this tool on all the PCs before I reimage the lab?

Ok, I'm reimaging a lab and none of the PCs rebooted while waiting for me to send the image to it. One rebooted during the reimage.

The console gave this log...

Error 52 1 (0x340001) 4/27/2011 2:34:53 PM Host '172.16.46.119' failed to deploy.
Error 51 2 (0x330002) 4/27/2011 2:34:53 PM Failed to download image '4874614650700'.
Error 65,535 65,534(0xFFFF...) 4/27/2011 2:34:53 PM Segment receiver failed

Hello David,

Thank you for replying.

The report utility needs to be run on one of the computer before the deployment and then after it becomes unbootable. You can use the Acronis Report 51 to collect it.

The cause of the error message "Segment receiver failed" needs to be investigated. I would really appreciate if you could get in touch with our Support team so that we can troubleshoot it.

Let me know if you have additional questions please.

Thank you.