Skip to main content

Partition/File Alocation Errors After Upgrade to ABR10.11345 from Echo Enterprise

Thread needs solution

We've just upgraded 36 servers from the Echo Enterprise product, with which we had no problems, to ABR10 and have deployed build 11345. I have several servers (20%) which when their imaging processes try to run return either the "Partition Error", "File allocation error" or "MFT bitmap is corrupted" errosr. I've run the CHKDSK /R process against all their disks more than once, and I continue to get the same errors. I've redeployed the agents multiple times with no positive effect.

Another issue I have is that when I try to image the system drive on my management server/storage node server, this server immediate reboots. I now show multiple running tasks for these failed images which despite my having tried to "Stop" them in the management console, and I cannot get ride of these bogus tasks. The other pressing issue is that I obviously cannot image the management server's C: drive at all.

My other major issue is that I have a Windows 2000 server to which the agent, the tray service and the URO agent have all been deployed and which show as in the RUNNING status on the server, but in the Management Console this server's line is greyed out and the availability is "offiline". I've pushed the installation several times to this server, but it hasn't helped.

Hoping someone can assist with something simple.

0 Users found this helpful

Hello,

We are communicating with Philip via Private messages. 

I would like to share some intermediate results, this information can be useful for other customers

1) The issue with the "MFT bitmap is corrupted" error has been resolved by installing SnapAPI file build #507. 

By the way, we have published the appropriate article concerning the initial issue, it contains the solution and the permanent link to download the necessary SnapAPI file of build #507. Please see the article for more information. 

2) The issue is under investigation, we are still trying to get rid of the tasks and trying to find the reason of the reboot.

I suggested:

- Please remove the traces of the tasks from Acronis Management Server. Please remove the appropriate policy using a special VBS script, you can learn more on how to do it in this article.

- Use  Task manager and stop Backup&RecoveryService.exe (all items that can be present there). After that go to Start -> Run -> type services.msc and restart Scheduler2 service.

- Please update or restart Acronis scheduler:

- Download a special Acronis utility;
- Start the Command Prompt from Start -> Programs -> Accessories menu;
- Run the following commands in the folder you saved the file to:

schedmgr task zap
schedmgr service stop
schedmgr service uninstall
schedmgr service install
schedmgr service start

- Download Acronis Scheduler, which is a special utility to update the scheduler service:
Windows 32/64 bit: scheduler

Extract the downloaded file and run install.bat. The utility will automatically update the service.

Due to unknown reason the system doesn't create mini-dump files after the operating system failure. 

3) The issue with the computer that is seen as "offline" has been resolved by re-adding the server.

From Acronis Management Console you should connect to Acronis Management Server. Delete the grayed out machine. And then re-add the deleted machine.

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.