PXE Deploy Agent with Kernel Panic
Hallo altogether,
I just upgraded my Acronis Snap Deploy 3 to the latest release 4. After installation I checked the whole system and I got an error on a waiting client with PXE boot Media (Snap Deploy Agent), see attached screenshots.
1. Error: "Inital ramdisk could not be loaded, please press "Enter" to continue"
2. Kernel Panic while loading/mounting system for Acronis Snap Deploy Agent.
I also tried with Acronis Boot Media (bootable CD and mounted iso-file in a VM) and both worked fine and without any problems. CD and iso are on latest revision, downloaded in my Acronis registration account.
Only the the PXE Agent caused problems. Does anybody have a hint or a solution for this error?
Thanks a lot.
Attachment | Size |
---|---|
acronis_error1.jpg | 204.08 KB |
acronis_error2.jpg | 281.44 KB |

- Log in to post comments

Hallo Anton,
thanks for your answer. I've already tried to solve the problem by reconfiguration of the PXE Boot components but without any effect. Problem with Kernel Panic is still the same.
I'll collect the report data and contact the support team as you've suggested.
Thanks a lot,
Fabian
- Log in to post comments

I run in exatly the same issue.
Curios: Sometime the boot process in the ASD4 Agent works. But in ~ 50% of all attempts the boot process failed with the alerts as fabian noted above.
Do we have already any fixes or updates?
Reinhard
- Log in to post comments

Got a reply yesterday after creating the AcronisReport.
Support told me, that's an "unknown" servere case, on which they have to take a closer look on.
--> Needs some time to figure out what's exactly happening and how to solve this problem.
As soon as I'll get new information, I'll tell you here.
- Log in to post comments

Hello Fabian and Reinhard,
Thank you for your posts.
Fabian, please feel free to contact me directly if you have any questions about your case.
Reinhard, we do not have any fixes at the moment, we are still investigating this issue. Please contact our Support team so that we can help you.
Is it possible for you to use a different PXE (Windows PXE) server and boot to it with our components? This will help us localize the issue because according to the information that we have from Fabian, the problem occurs on the last step of the booting process when the bootwiz.cfg & bootwiz.bin files have been uploaded successfully. Then the agent starts to load through tftp and this is where the failure occurs.
Please let me know if there is anything else we can do for you.
Thank you.
- Log in to post comments

I recently had this issue as well on one of my systems. What worked for me was running a disk wipe utility (like DBAN) on the system that wouldn't load in. as soon as that was finished Snap deploy agent loaded with no problem. Hope this helps.
- Log in to post comments