PC will not boot after ATI2016 to AT2017 upgrade
I can't find previous reports of this phenomenon, so I decided to throw it into the pile of issues that people might face when updating to ATI2017.
Continuing problems with ATI2016, and a £7/PC upgrade offer, conned me into upgrading to ATI2017.
After the upgrade, the PC couldn't find the boot drive and asked for a floppy to boot from.
The PC was setup to offer Acronis Startup Recovery Manager. So I went into the UEFI BIOS and told it not to do that.
Removing that option from the boot order allowed the PC to start as expected.
This suggests that something goes wrong when Acronis updates.
It might be a good idea to warn people that they should disable "Activate Acronis Startup Recovery Manager".
This is the PC in question:
Windows 10 64-bit + Asus Z-170-K + Intel i5-6500 + 512GB Samsung SM951 M.2 PCI-e AHCI SSD + Corsair 16GB DDR4 Red Vengeance LPX 2400MHz Memory
Perhaps Acronis doesn't understand the use of an M.2 PCI-e AHCI SSD.
I upgraded from ATI2016.
I simply told it to go through the upgrade process.
As expected, the final message was to request a reboot. That was when the sky fell in. It would not reboot.
Nothing had changed. Same array of drives, same BIOS settings. The only difference was ATI2017, which was set to show the Acronis recovery option. Going back into the BIOS and disabling that got me back in business.
I see that an other user has recently reported an issue with an m.2 drive. Perhaps it is too new for Acronis to have fully debugged.
Hello Michael,
The behavior described reproduces in rare occasions and we are trying to figure out what exactly causes it.
I'm glad you found a way to fix it on your own by removing Acronis loader from the boot order in BIOS.
Regards,
Slava
Slava,
EDIT:
This thread is a bit old but I would like to point out that I believe the user in this case is booting the M.2 drive in question in AHCI mode. That differs from most users whom have issue with booting the M.2 drives whom have NVMe drives. That points to an issue with the Linux kernel not recognizing the EFI module for PCIe based drives.
I downloaded Acronis 2017 True Image just the other day. After going through the first few steps of cloning my OS drive and restarting, my machine does not boot up at all. The only way I can access files is through the safe mode. What should I do?
Windows 10. I'm cloning from an SSD to a larger SSD.
At this point, I'm reseting my PC.
-scott
Scott, welcome to these user forums.
Your problem is completely different to the subject of this specific topic, please create your own new topic by clicking on the button for this at the top of the forum, then in that new topic, please provide more details of exactly what steps you followed to do the clone of your OS drive?
Indeed, start another question.
In that, explain how you have set up the boot order in your BIOS.
If that doesn't mean anything to you, then that is where to begin your quest for a solution.
Michael,
Would you confirm that you are using an AHCI version of the Samsung SM951 drive on your ASUS board?
Can you also confirm that you are booting in UEFI Only mode rather than UEFI/Legacy/CSM support mode?
Can you confirm that you performed a clean install of Windows 10 on this SM951 drive?
Can you confirm that you have the Samsung Storage Controller driver installed in Windows 10 for the SM951 drive?
Can you confirm how the SM951 is attached to your board, ie. dedicated M.2 slot or PCIe adapter card?
Can you confirm that you have Storage Configuration on your Mobo set to AHCI mode?
Can you confirm any other storage drivers that you may have installed in your Windows 10 installation such as Intel IRST drivers or ASMedia drivers?
Can you provide driver version numbers of ALL installed Storage Controller drivers in you Windows 10 installation?
I am asking so that I can compare your configuration to that of 2 systems that I have using the NVMe versions of the SM951.
Thanks.
Too many questions there. Do you have a problem like the one I saw? Or are you just inquisitive?
Read Slava's response. Acronis is aware of the phenomenon and is trying to track it down.
What I see – the failure to boot when the Acronis Startup Recovery Manager is enabled – has nothing to do with installing or running Windows with this drive. And the boot failure happens when TI2017 updates. I first saw it when I foolishly accepted a deep discount to upgrade and moved from ATI2016 to ATI 2017.
Fortunately, I understand the boot regime and just needed to go in and change the boot regime.
I haven't had to do this in a while, but I suspect that the way to avoid what I see is to disable Acronis Startup Recovery Manager before updating True Image.
Michael,
I asked those questions so that I can better understand your machine configuration in an attempt to help solve the problem you have here. Your particular issue is with ASRM in this Thread. Most users do not use ASRM so reports like yours are very few, in fact, I think yours is the only one I have seen where ASRM is mentioned!
Activating the ASRM provides the user with a method of booting the computer into a Linux based environment for example when Windows boot has issue. Other users whom have problems with the M.2 drives have issue when using the Linux based user created Recovery Media in that once booted to the Recovery Media the M.2 drives are not recognized. Your issue and theirs are most likely the same issue.
I have 2 systems using these M.2 drives and do not have the issues you or other users have with the M.2 drives. My questions if answered might give myself and others a new clue as to what might be the problem causing the issue. It is fine if you do not care to answer. I do encourage you however to provide the feedback and system report that Slava asked for as it will help the developers in finding a solution.
Maybe you can answer one question from me as well. Can you boot your computer using the default user created Linux based Recovery Media and once booted are you able to see and work with your M.2 drive?
Thank you.