Aller au contenu principal

Hard drives dead after Locking Partition 0-0

Thread needs solution

Hello,

We are using Acronis Backup 11.5 Update 3 (build 11.5.38573) on a computer running Windows Server 2008 R2 SP1. The MOBO is IEI IMB-Q670-R21 Rev2.0. Fried disks were Western Digital Enterprise Storage WD2003FYYS configured in RAID1 (software RAID, intel).

The computer was delivered in April 2013. The Acronis jobs have been working fine until 2. June 2016. The job consists of:

 - Weekly full backup

 - Daily incremental backup

 - Delete older backups and log entries etc.

 

The absolute last entry in the acronis log is "Locking partition 0-0". The PC was unable to boot at this point, showing the error "Bootmgr is missing". After examining the PC, we find that both harddrives in a RAID1 configuration were fried (BIOS is telling us that the harddrives are 0 GB and not accessible).

After purchasing new harddrives and recovering from backup, we examine the logs further. We find that there are no entries in windows application and system logs, and no entries in our own application logs after "Locking partition 0-0". The operators have not been notified of harddrive failure, and we cannot find any mention of hardware issues in the logs neither. This leads us to believe that both hard drives were intact, and Acronis somehow managed to fry our disks. We have also checked the UPS logs, and it was online with full battery at the time of the failure.

There are a few mentions in the forums with people having trouble with "Locking partition 0-0". It seems that the answer that is most relevant is to install updated "SnapAPI drivers".

Please advice us what we can do. We have had very good experience with Acronis in the past, but we need to make sure that the backup solution cannot cause problems in production.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Trond,

Thank you for your posting! I'm very sorry to know that you've faced such a terrible situation. I've discussed the issue with my colleagues from the development team. According to my colleagues the SnapAPI drivers cannot affect the data on the lowest level. In case of a hardware RAID the interaction chain will look like

Acronis Backup -> SnapAPI -> Windows OS storage subsystem -> Single block device as provided by RAID controller -> 2 physical HDDs. 

As one of the possible causes - the backup process can load the drives and if the drives already were in a bad state (e.g. overheated), it might lead to the complete failure. Have you checked your drives with the diagnostic tools?

Thank you,