Skip to main content

Recovered PC not working - specific HDDs

Thread needs solution

Hello everyone,

 

we have a really weird problem I don't even know how to properly describe, but I will try:

Short version: we have troubles with recovery of several Windows 10 clients. After the recovery they get stuck on black screen with loading spinning dots and stays there (even for days) never load the system.
Weird thing is, that if recovered to some HDDs, it boots well. 
What the hell? How is that possible?

 

Long version:
recently we have started to experience issues with some Windows 10 clients after recent Windows updates (PCs get stuck after reboot on black screen). This is currently under investigation and we have ticket open with Microsoft. 
So, for now let's ignore that, but this is the reason why our colleagues affected by this problem noticed issue with Acronis recovery.

When they recovered those affected clients (with backup month or two old, before updates were installed) they unfortunately got into the same situation - black screen with spinning dots. 
OK, so we thought that maybe the problem was already present there when those backup were created and the last windows update worked only as a trigger. It's strange, but I guess anything is possible...

Nevertheless, they tried to recover quite a lot backups and basically all of them failed with the same outcome..until I moved one of failing backups to another server and successfuly recovered it to a spare test PC..and there it worked just fine!

We compared system I used for the test recovery and their systems, but they were basically identical (all standardized HW we are using, Siemens IPCs with same HW configuration).

After many hours/days of testing/troubleshooting we found out, that after successful recovery the PC is bootable only on some HDDs. We have no idea why and there seems to be no obvious pattern (different brands, models, HDD sizes).

We tried the recovery on around 7 HDDs (Seagate, WD, IBM..mostly 500GB or 1TB version) and even though the recovery works on all of them, PC boots the system only on like 2-3 of them. 

And not even that is consistent, because some of those backups are bootable from let's say disks A, D, G , and other from B, D, E etc. , another boots from C and E, but not from the rest etc.
So it's not even consistent in a way where we could say, OK, this and this disk is bad.

All disks were checked and show no errors/bad sectors. All disks were properly cleaned with diskpart before the recovery. All are GPT.

It doesn't matter if we do the recovery via Acronis console or with Acronis USB media. The results are identical. Also the source of the backup doesn't matter..we moved backups to another server, used non-deduplicated Location (original backups were in deduplicated Location, but in the end that didn't make a difference) and even created and tested brand new backups.

 

Have anyone experienced something similar? How can it be that if we recover backup to original HDD, it won't boot. But if we recover it to some random HDD, then it (MIGHT) work? But only on some? As I said, backups were tested on around 7 different HDDs so far, some work, some don't and those that don't have no issues with other backups and vice versa.
We are completely mind blown by this and it's not even something I can take to official support as I have no idea how I could explain this properly over the phone. It's just a case where "recovered backups sometimes work and sometimes don't" :-/ 

 

Crazy..

 

 

Lukas

0 Users found this helpful

Hello Lukas!

I think I had an instance where I restored a windows 10 machine and and it booted forever (spinning circle). After a few tries it boots, but it's generally an unstable computer. I'm suspecting a faulty PCI card there though, as it's also sometimes loggin errors in the event log. Either that or a faulty motherboard.

Most of the mysterious cases I had when restoring didn't yield a usable system boiled down to a messed up system with/without hardware faults. I had a CPU card where it didn't detect 4 out of 8 pci solts. Everything else worked, the pci cards worked, the backplane worked, swapping them around worked, the system just wouldn't detect them in any form in 4 specific slots. It seems the PCI controller died on that side only, because a new identical card worked as expected.

I also had a few cases where some industrial motherboards were very picky about the hardware they were compatible with, but that included mostly pci cards and memories. Haven't seen this with drives yet.

Couldn't it be that the sata controller died/is faulty in your problem system?

-- Peter

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Lukas,

thank you for posting on Acronis forums!

Have applied Acronis Universal Restore as instructed in this KB article: https://kb.acronis.com/content/35681 ?

The restore goes the following way: the software creates volumes on a target drive as in the backup and then begins to restore data from the backup. As I understood from your description, the issue is at the second step. So, the root cause could be either in the specific data in these backups or in the target drives (where the data could not be written).

We are completely mind blown by this and it's not even something I can take to official support as I have no idea how I could explain this properly over the phone. It's just a case where "recovered backups sometimes work and sometimes don't" :-/ 

You can always share a link to this forum thread with any support engineer.

@Péter:
Hello Péter,

 

thank you very much for your response and insights. PCI cards sometimes cause similar issues, we experienced that in the past too, but it unfortunately doesn't seem to be the case here as some of PCs where we have this problem, don't have any PCI cards connected.
One or two of them were even brand new, not even completely set up yet (just prepared to be used in production in the following weeks/months) and were working just fine until colleagues there tried to recover them - as a test.

@Maria: 
Hello Maria,

Thank you. I guess we can try universal restore to see if it makes any difference, but it's weird if it will, as it's not really recovery to dissimilar HW, but identical HW (even recovery to original PC with no HW changes done, has the same result).
We will test universal restore and let you know the outcome.

 

Lukas