Warning! After Operation Completion Operating Systems Will Not Boot From The Destination Disk In Bios
The other day, I forgot to unplug my C:/ drive before installing linux and now that drive has more partitions than it should/did in the begining. So, to correct the matter (I think) I have to recover the Entire disk.
The problem is, I get this message: Warning! After Operation Completion Operating Systems Will Not Boot From The Destination Disk In Bios
I understand the the significance of the message to mean, the ACRONISBOOT USB drive is booting into BIOS/Legacy mode. And if you continue with the operation, and replace your UEFI system with MBR, doing so, will render your system unbootable.
I know this isn't the first time I've posted on the subject, and I apologize. But just the same, given my current set of circumstances, I really need to recover the entire drive (to get it back to it's condition on the 26 June 2020.
At any rate, I've included images proving that the drive (I.E. Acronis Recovery Media a.k.a. ACRONISBOOT drive is UEFI; and including the Lexar JumpDrive is also UEFI.
However, when asked at the screen to proceed with the operation, I still get the message: Warning! After Operation Completion Operating Systems Will Not Boot From The Destination Disk In Bios
When the ACRONISBOOT USB what appears is: white text on a black screen. I press 1, and then the program starts...
What "mode" is that text and background color indicative of: BIOS or UEFI?
Could someone please provide a screenshot of both "modes?" Evidently, Acronis Bootable Media, isn't happy with this mode I'm booting into...
Thanks.
Hi Steve,
I couldn't really d/c any drives, b/c a: my .tib files are on the WD 4 TB My Passport Ext. Drive.
and b:The last time I was facing this issue, the nVME wasn't installed, and in the absence of it being installed, didn't bring the issue to a resolution; except to say, I should only check / tick the box marked for the Samsung SSD, where my Win 10 OS is located; and that was used as a workaround - (rather than checking/ticking that on box that selects all the disks in one go.
Given the images I've provided, I can't understand why Acronis thinks it's booting from anything other than a UEFI environment.
I was wondering if the way my C:/ drive is partitioned (as seen in Gparted,) could be the culprit...
Thanks.....
I don't see any issues with your C: drive partitions.
Is your Disk 2 an internal drive? If so, can you disconnect just that one?
Your BIOS image shows your rescue media as first priority for UEFI boot, but when the PC boots, do you see an actual Boot menu to confirm that is the option being used?
KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media has examples of how the boot menu might look and differences in how the ATI app looks depending on the boot mode.
The Plot Thickens ---
KB 59877 confirms that, my boot screen - white text on a black background - the Acronis Bootable Media, a.k.a. ACRONISBOOT does in fact boot in UEFI mode.
Given all of that, it is incredibly frustrating to see the Warning!... appear just before the end user commits to the recover process.
As far as I can ascertain, Drive 2 is the nVME drive I bought to to install Linux on. I honestly don't think removing the nvme drive will solve the issue, as we've both seen this movie before, before I bought the Nvme drive. (see post #2) However, I'll give it a try, and report back with my results.
Well, I removed the nVME drive, and tried again, however I continued to received the "Warning!" message, even without the drive installed.
One further thought, what is the current partition scheme on the target drive now before the recovery is done?
One action I tend to do these days for most recovery actions is to click on Tools > Add new disk and select the target drive and set the partition scheme as wanted, i.e. to GPT for UEFI systems.
One action I tend to do these days for most recovery actions is to click on Tools > Add new disk and select the target drive and set the partition scheme as wanted, i.e. to GPT for UEFI systems.
I can also give that a try...
Also here are two more screenshots...
Hope that they help,
CotS
So, I tried to "add new disk," but Acronis let me know that a/ on the destinationdisk you selected (the Samsung 1 TB that houses my W10 system,) Acronis detected useful data on those partition(s). and b/ that I could potentially lose data if I went ahead by adding a new disk.
As far as I know, it would delete the existing partitions before adding a new disk...
What is your advise?
Thanks
One final sanity check needed here....
When in the rescue media environment, are you definitely selecting the correct target disk for the recovery?
Yes, the first action of a recovery is to wipe the target drive in order to prepare it for recreating the partition scheme from the backup image, so if you are selecting the correct drive, Add new disk is only doing the same as recovery would do other than allowing you to choose the GPT scheme beforehand.
Just to confirm, (and answer your question,) I am selecting the Samsung SSD 930.1 TB, as the target; i.e. as the drive I want to recover.) And also this drive also has my Win10 OS on it....and X-Plane 11.
My other question, is: will a recovery operation work if the number of partitions has changed? Would it now be recovering back to what it thinks is a "different" drive? (remember, I'm trying to do a whole disk recovery.)
Thanks in advance,
CotS
Crime of the Scene wrote:My other question, is: will a recovery operation work if the number of partitions has changed? Would it now be recovering back to what it thinks is a "different" drive? (remember, I'm trying to do a whole disk recovery.)
To be honest, ATI doesn't care about the number of partitions on the target drive as it will wipe the whole drive then will recreate how the drive looked when the backup was created. If you have applications that are activated based on the drive signature, then use the option to recover that signature during the recovery actions.
Hi Steve,
I successfully added a new drive, and created it as GPT.
However, by the time I got to the "Are you sure you want to proceed" page, there was the familiar warning that said basically: if you proceed, a/ this drive we've detected as MBR, won't be able to boot if you proceed if you proceed with this operation...
Or words to that effect. So, after seeing that, I cancelled out of the operation....
Now what? Please advise.
If you have used 'Add new drive' and prepared as GPT, then you have an empty drive so I would say do the restore and see whether it does change from GPT to MBR per the warning or not?
If it's true to it's word, and changes it to MBR, will I be out of a system drive?
No, you can use Add new disk and change it back to GPT as an empty drive or else use the Windows 10 MBR2GPT tool.
As scary as it was; going against Acronis' Advice i.e. the Warning! in orange, it worked!
Thanks so much for all your help; I appreciate it.
Crime of the Scene
Glad the warning turned out to be 'Fake News!'...
I'm battling the same issue and will use the advice given here and in other threads. But what really ticks me, as a software developer, is that the ATI developers have code to detect the mismatch, and in usual fashion, all they do is provide the warning. They could EASILY show mode of the backup and what we booted up as, and give us the solution right there, since their code caught it. As a software developer for over 20 years, I can genuinely tell you that we cause all the problems and don't go far enough to guide the user. Apple is equally guilty as well,
James DeCesare wrote:I'm battling the same issue and will use the advice given here and in other threads. But what really ticks me, as a software developer, is that the ATI developers have code to detect the mismatch, and in usual fashion, all they do is provide the warning. They could EASILY show mode of the backup and what we booted up as, and give us the solution right there, since their code caught it. As a software developer for over 20 years, I can genuinely tell you that we cause all the problems and don't go far enough to guide the user. Apple is equally guilty as well,
Hello James,
thank you for taking the time to share your experience and feedback! Passing this comment to the product management for review.