Skip to main content

General recovery/uefi questions

Thread solved

I have done several uefi disk recoveries to same/and/different disks by selecting the entire disk from older versions of ATI and also what I have now ATI 2019. These work fine.

I installed new Realtek audio drivers which made all the realtek stuff dissapear and rolling back the drivers, etc didn't help.. after a couple of days messing around I decided to do a restore.

When doing the restore from both linux and windoze recovery media, I get a corrupted index message on ALL versions full, and incremental.... first time in many years. Verify comes out good both from recovery media, and the boot disk.

A couple of questions:

Why does it say it is doing a sector by sector restore when the .tib files are NOT sector by sector.  Does it auto set that when doing a full disk restore?  It has always worked ok in the past. I will go back and see if there is a setting I missed.

If I only restore from recovery media the C: partition (os,date,etc) will I get back to that particular date and still boot?

Also Can I do it if booted off of the disk I want to revert back a couple of days?

I don't want to screw up the bootable disk I have if none of the .tib files work.

In the past I have always been able to restore to a new blank disk and make sure it works saving the original for a backup. For some reason now I can't.

Any info is greatly appreciated

0 Users found this helpful

Tim, if you still have a working, bootable system, albeit with the Realtek audio driver issue, then I would suggest making a new full disk backup of that working system before attempting any further recovery actions.  Ideally, store the new backup on a different backup drive if available.

When doing any OS recovery, I would recommend against trying to do this from within that Windows OS as this will require that the boot configuration (BCD) files be modified to launch a temporary Linux based Acronis environment for the recovery.

It is safer and better to boot your computer from the Acronis Rescue Media for an OS recovery.

If you have a spare disk drive that you can recover to, rather than the current working drive, then that too would offer a safe way of testing your recovery.

Sector-by-Sector mode is normally invoked (during backup) if disk errors are encounters, such as bad sectors.  It has been my experience that it is shown during recovery regardless of whether it was actually used to create the backup image being recovered from!  If the backup file was created without using Sector-by-Sector, then there can be no extra sector information involved in the recovery.

I would recommend performing a CHKDSK /F for all disk drives involved in this scenario to ensure that there are no file system issues here.  CHKDSK /R may also be needed if there is any suspicion of any bad sectors.

One further option you may have here, if you have a spare disk drive, would be to clone your current working drive to the spare one (after making a disk backup first!) then try just recovering your C: partition to that spare drive.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media - any recovery must be done using the same boot mode as used by your Windows OS.

Also, if you still have a running system (minus the Realtek stuff) and you have Windows' System Protection enabled, I would recommend trying to to go back to an earlier Restore Point.  I know a lot of people have had problems with restore points over the past few years (with Windows usually saying it can't do the restore, I think), but I've had luck backing out bad drivers that way.  When it works, it's a lot less hassle than doing a complete recovery.

Thanks to both of your for you quick response and insight as to what to do.  I created a new full backup on different media and had a clone of my boot disk 6 months or so old. Did a restore of just the C partition.  No complaints of corrupt index.  While it was restoring I remembered that I had changed the login for the two windows audio services following some instructions for a different problem. Went to two other win 10 machines and checked the settings of the two services. The restore was good, and booted fine.  I then applied the one service whose login was different, low and behold the Realtek problem is fixed.  Now I just need to put my original boot drive back in and figure out just exactly what disk is causing the  index problem.  Kinda good this happened or I might have been sol when I really needed a good backup! And I have a current clone. :-) and I do have System Protection enabled, but it did not help.

Thanks Again!

Tim

Tim, glad to read that you have been making good progress with this issue, so hopefully getting the original boot drive sorted should be an easier task now.  Thanks for the feedback.