Salta al contenuto principale

Clone fails to read MBR

Thread needs solution

I have tried 3 times and I keep getting the same error. Setting up the clone is fine in Windows 7, then it reboots, starts the Acronis loader, gets a few lines in before it says "failed to read MBR" or something close to that... the bloody thing closes so fast you can barely read it...

I have checked the forums and found people having similar problems but no solutions were offered... so don't tell me to boot from recovery disks or to backup and restore. I want a functioning clone. That's all I want from acronis.

I went with an Adata SSD because it included this software... which I now find out is broken and useless. I can't even email or phone you bloody customer support people because this legacy software is unsupported... truly pathetic customer service.

0 Users found this helpful

Can someone reply with a solution? I see a few forum topics regarding this issue, but no reply as to why this happens.

I have this same exact issue as Gerrtt. I'm using the free Seagate edition of TI - I believe it is a 2010 version. Problem is, I got a new hard drive over a year ago and was able to clone my hard drive with no issue. I've been using it ever since. Now I have a newer hard drive and I'm trying to clone my existing one to it, but TI tells me to reboot and then after the reboot I get the following:

======================================
Starting Seagate Loader....

Loading, please wait...
no raid disks
Reading all physical volumes. This may take a while..
No interfaces discovered
Unable to read configuratioin file
Setup AVD devices
Failed to read MBR sector.
======================================

I have no idea why I could clone my hdd a year ago and now it doesn't work. I've tried many things before posting here, but now I'm just about out of options. Any help as to how to solve these error messages would be appreciated.

It is possible that your version doesn't support your chipset. You might want to register for a trial of 2013 (no need to install), get the bootable ISO of the trial and see if that boots correctly on your PC.

It shouldn't have anything to do with my chipset since I was able to clone my C: drive last year on the same PC with the same version of TI. The only change to my system since then is I added a new gpu. I'm really interested in finding out why I get the messages below when I try to clone. If I knew the answer to this then I might be able to fix the problem. It seems like someone at Acronis should be able to tell me why these messages appear.

No interfaces discovered
Unable to read configuratioin file
Setup AVD devices
Failed to read MBR sector.

This forum is not very much frequented by ACronis employees, and older versions are not supported by Acronis either.

We typically recommend that users use the recovery CD to clone, and not do it from Windows. This avoids issues where the MBR and boot records changes required to boot into the cloning environment don't get in your way.

I cannot explain why it worked in the past and not now... Maybe your security software is different and blocks some changes, maybe the data that ATI is using on the disk to reboot in has been changed somehow, ...

Try with the recovery CD.

I have seen my problem brought up on a lot of forums and no true answer given other than "Please try using the recovery disk". I was finally able to fix my problem. I'm posting this so that others receiving this error using DiskWizard may benefit.

When I tried to clone from Windows, my pc would reboot as it should, but then I'd get the "failed to read MBR sector" message and my pc would simply reboot back into normal operation.

When I tried to clone using the recovery disk, I would simply get a "Clone operation failed" message.

Being an idiot, I failed to notice the Log Files tab when I was in the DiscWizard software using the recovery method. When I finally noticed it and looked at the log it gave me my exact error - corrupted index on the disk I was trying to clone. I ran chkdsk on my hard drive to correct all errors and the clone operation then worked like a charm.

Anyone else having this problem should just check the Log Files tab in DiskWizard - I don't recall seeing it when I ran DiskWizard within Windows, so you may have to use the recovery option.

Thanks for the update.

The log files are viewable in the Windows version of your software as well.

Any Acronis error that reports MBR problems is a sign of corruption of the MFT/file system/MBR, on an MBR style disk, and indicates the need to run disk checking utilities. Acronis is very picky about these type of errors.

Glad to hear you are up and running again.

As a side note, running a clone from the Rescue Media is often a better method, as it gets Windows out of the way of the operation. When cloning from within Windows, Acronis will change the boot loader on the source disk and reboot to start the recovery environment (Same as the Recue Media) from the source hard disk, before Windows boots. This can sometimes cause issues with the source drive if there is an issue with Acronis's ability to start the system up correctly. Running the clone from the Rescue Media leaves the source drive "un-touched".

"This forum is not very much frequented by ACronis employees, and older versions are not supported by Acronis either. "

Pretty amusing, the LACK of support for "older versions" support from Acronis - not very reassuring for potential NEW customers hoping for EXACTLY that support, since NEW versions regularly appear, rendering THIER version old and now unsupported...

"We typically recommend that users use the recovery CD to clone, and not do it from Windows. This avoids issues where the MBR and boot records changes required to boot into the cloning environment don't get in your way.

I cannot explain why it worked in the past and not now... Maybe your security software is different and blocks some changes, maybe the data that ATI is using on the disk to reboot in has been changed somehow, ...

Try with the recovery CD."

UMMMmmmm - no reply to THIS user comment?

"When I tried to clone using the recovery disk, I would simply get a "Clone operation failed" message. "

SOOooo, the revered " use the recovery disk" unfortunately is NOT the "always cure-all" would-be helpers constantly fall back upon...

And then, when a USER comes up with a working solution on his own, we get this reply- as tho' the "helpful poster" knew it all along, but for some reason, failed to bring it up as a suggested solution:

"Thanks for the update.

The log files are viewable in the Windows version of your software as well.

Any Acronis error that reports MBR problems is a sign of corruption of the MFT/file system/MBR, on an MBR style disk, and indicates the need to run disk checking utilities. Acronis is very picky about these type of errors.

SOOOoo, why wasn't THAT fact addressed earlier? It would have been FAR more helpful and applicable, than the tired old "Use the recovery disc" we see so often...

Glad to hear you are up and running again.

As a side note, running a clone from the Rescue Media is often a better method, as it gets Windows out of the way of the operation. When cloning from within Windows, Acronis will change the boot loader on the source disk and reboot to start the recovery environment (Same as the Recue Media) from the source hard disk, before Windows boots. This can sometimes cause issues with the source drive if there is an issue with Acronis's ability to start the system up correctly. Running the clone from the Rescue Media leaves the source drive "un-touched"."

And ONCE again, that "fall-back" solution to "use the recovery disk" -- WHAT PART OF the earlier posted "When I tried to clone using the recovery disk, I would simply get a "Clone operation failed" message. " went over your head?

Looks like we users could use lots more original, and insightfull replies, than the canned, broken record stuff spooned out by "helpers" falling back on old wornout crutches that too frequently are NO help at all...