Direkt zum Inhalt

HP Z640 Backup with Error code 16 and 13 warnings

Thread needs solution

Hi,

I have a simple problem with Acronis 11.7 and around twenty HP Z640 workstations that I have deployed to a customer facility.

The problem is that when I do a full backup using Acronis 11.7 the backup is successful but the same warning codes are generated on all 20 of the PCs.

The spec of the PC's is

  • Intel Xeon E5-2620v3 2.4 1866 6C
  • 16GB DDR4-2133 (2x8GB)
  • 512GB SATA 1st Solid State Drive
  • NVIDIA Quadro K2200 4GB GFX

The error generated is as follows -

Acronis Backup Spare Matlab PC full backup.jpg

I have done the same backup to an HP620 and this works and I also have done the same thing on two Novatech NTI202 workstations that also regularly work fine.

So to me it looks like some sort of permissions or compatibility issue between Acronis 11.7 and the UEFI in the HP Z640.

I have uploaded the latest BIOS update which has made no difference.

Anyone any ideas?

Regards

John

 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi John,

There is a known issue that such warning is thrown for specific setup of the bootmgr setup on EFI machines (internal ID: ABR-117293). Despite the warning the recovery from such backup is working properly. See below screen shots showing the root cause.

The problem is that the machine is actually booted directly into EFI disk (0.0) without even going through Windows Boot Manager. In such case "BootCurrent" variable shows this disk instead of Windows Boot Manager, and our code can't find BCD record there.

Therefore you should either ignore this warning or fix the BCD record by moving Windows boot manager to the top.

image

image

Thank you.

In reply to by truwrikodrorow…

Hi Vasily,

You are definitely showing evidence of the 'Forum Star' status that you have, your fix works and I'll be deploying this to the rest of the network. 

For anyone that is also having this problem, the command I used to move the windows boot manager to the top of the list was -

Bcdedit /set {fwbootmgr} displayorder {bootmgr} /addfirst