True Image 2013 Plus Pack Universal Restore Usage for AHCI Mode to RAID 0 Mode migration

Did you save the log from the failed restore using the Universal Restore feature?

100PIER,

To get a couple of things out of the way:
- do the recovery from the recovery CD,
- does the recovery CD see your RAID 0 as a single volume?

James F,
What and where log is ?
No error number is displayed on the screen. Only operation failure !

A quick first preliminary test you can do is do a backup of a system disk with a CD rescue (WinPE 3 or 4), then restore the image .tib at the same place, same PC with tagged Universal Restore and no drivers injection. You got the failure message !!
100PIER

100PIER

What is the "error message" you are receiving?

You can view and save the log using a utility that is included in the WinPE build Rescue Media.

After the operation completes/fails, in the WinPE command prompt window, navigate to X:\program files\Acronis\TrueImageHome\A43, then type A43 and press enter. This will start a graphical file explorer. While in A43, browse to X:\program files\Acronis\TrueImageHome\Data\Logs, here you will find the log files. You can view and save the log files to your backup drive or flash drive.

Pat L wrote:

100PIER,

To get a couple of things out of the way:
- do the recovery from the recovery CD,
- does the recovery CD see your RAID 0 as a single volume?

To clarify: the initial backup image is the AHCI Mode config, i want to restore this image to a RAID 0 config.

To do the backup/recovery we have 3 possible CDs rescue:

1) standard (Linux) CD provided with the product 2013 (build # 5551)
2) WinPE 3.0 CD
3) WinPE 4.0 CD

a) Can you confirm me that for any backup/restore operation with have to use one of them ?
Can we mix or not the usage of these C ? (i.e. a backup with Linux CD and a restore with a WinPE CD)
b) Doing a simple backup operation of the AHCI Mode config with each one of the CD rescue gives not an identical .tib size
Why ? Are backup image strictly identical ? What do you think about ?
c) I have done lot of tests, yes the recovery CD see the RAID 0 as a single volume, but the operation fail at the end !
Which CD rescue do you recommend to use ?
For me we are speaking of various add-in Pack Plus version , can you clarify me ?
100PIER

100PIER,

You can do the backup when in AHCI mode from any of the three pieces of Recue Media as long as each can see the source and target drives correctly. During restore, you must have Rescue Media that is able able to see the RAID array correctly. If you can see the RAID array as a single drive with the Linux based media, you could use that version, if not you will have to use the WinPE 3.0 or WinPE 4.0 Rescue Media with the correct 32 bit drivers injected unless the WinPE 3.0 or WinPE 4.0 Rescue Media has built in support for the RAID controller. (The WinPE 4.0 Rescue Media may be able to see the RAID controller without additional driver injection because it supports more hardware natively). I can't say why the .tib file sizes are different. (it could just be some small differences in how each version of the rescue media is compressing the .tib file, and may not matter) The version information should be the same for each of the type of Media you have created (2013 build 5551), I have all three versions of 2013 media (PE 3.0/3.1, PE 4.0 and Linux) and will check them and post the results of the version checks. (They should all report the same version).

After booting to all three versions of the Acronis Rescue Media that I have created (WinPE 3.0/3.1, WinPE 4.0, and standard Linux based), I can report that all three report 2013 build 5551 as the version of True Image 2013.

James F wrote:

100PIER,

You can do the backup when in AHCI mode from any of the three pieces of Recue Media as long as each can see the source and target drives correctly. During restore, you must have Rescue Media that is able able to see the RAID array correctly. If you can see the RAID array as a single drive with the Linux based media, you could use that version, if not you will have to use the WinPE 3.0 or WinPE 4.0 Rescue Media with the correct 32 bit drivers injected unless the WinPE 3.0 or WinPE 4.0 Rescue Media has built in support for the RAID controller. (The WinPE 4.0 Rescue Media may be able to see the RAID controller without additional driver injection because it supports more hardware natively). I can't say why the .tib file sizes are different. (it could just be some small differences in how each version of the rescue media is compressing the .tib file, and may not matter) The version information should be the same for each of the type of Media you have created (2013 build 5551), I have all three versions of 2013 media (PE 3.0/3.1, PE 4.0 and Linux) and will check them and post the results of the version checks. (They should all report the same version).

James F,

Here are a summary of some tests I have done:

Step 1: Produce the AHCI configuration image with any one of the 3 CD rescue available.
Step 2: Modify SATA Mode setting in BIOS: AHCI => RAID
Step 3: Use (CTRL+I) boot command to set up the Intel RAID 0 volume
Step 4: Use PE 4.0 Rescue CD to Check RAID 0 Volume parameters (i use 'Acronis Tools' option).
Result: RAID 0 Volume is well detected and quite OK.

Test 1: Start a Restore operation , with NO tagged Universal Restore Option.
Result: Restore Operation OK,
BUT when Reboot PC ==> BLUE SCREEN

Test 2: Initiate a Restore operation, with Universal Restore tagged.
Specify Intel RAID drivers folder located on the same HDD as backup image is located.
Intel drivers Version used: 11.60 , Folder name: f6flpy-x64 which contains 6 files (nota: rumor is any previous version are not TRIM compatible..)
Result of the Restore setting:
A list of 6 steps appear. The last operation in the list states as this (i translate in english): "use all operating system drivers..".
Why is there no step listed such as "use additionnal drivers on xxx path-name" i had however specified ?
Why this additionnal drivers source seems ignored at the moment of the procedure ?
After the 'start' the steps are executing one after the other one , time calculation quite very variable (16 mn , then 6 m, then 15 mn again, etc..)however Operation seems quite a lot slow compared to a 'standard' restore.
Why this slow progression ??
Step 5 (at about at mid time of of the estimated calculated time) is the "MBR" step, seems well executed.
BUT, Looking carefully i see a very brief message such as "Starting Acronis Universal Restore.." and got immediate "Restore Operation failure" display !!

So, what ?

Next try to do, activate a logging.
100PIER

The log file is automatically created during the restore.

While still booted in the WinPE environment, open the A43 program as I indicated in the above posts and browse to the log file. Copy it to your backup drive, then attach it a post for us to review. (You can change the name of the backup log to a text file before attaching it.)

Also after doing a restore, you could try and boot your system to your Windows 7 installation DVD and run startup repair on the newly restored copy of Windows 7 on your RAID to see if it can correct the BSOD. You may have to run the startup repair several times before it can correct the BSOD problem.

James F,

Here is the log file. (i have change the name).

After doing the 'failing' restore i have try to boot with the W7 installation DVD and run a startup repair. Several times !
No success BSOD problem is not correted !
I get a message like this (i translate):
"Non specified modifications in system configuration should be the source of the problem ... Result=fail ,Error Code = 0x490"

So, what do you suggest ?
100PIER

100PIER,
Accorinding to your log, the Universal Restore is failing do to a file not being found on the WinPE media (mspack.dll). I have reported this problem to Acronis, but there is a workaround for it. The file that is needed is located on a 64 bit system (with Acronis 2013 installed) in C:\Program Files (x86)\Common Files\Acronis\Home. You will need to copy it to the drive that contains your backup files, and after booting to the WinPE disk, in the WinPE command prompt, you would need to copy the "mspack.dll" file from your backup hard drive to the X:\program files\Acronis\TrueImageHome folder before running the restore. You can do this using the A43 file explorer progam or using the "copy" command. As an alternative, when creating the WinPE media, after mounting the winpe.wim file, you could copy the "mspack.dll" file to the "mount" folder" in the appropriate directory "c:\winPe-x86\mount\program files\Acronis\TrueImageHome" before commiting the changes.

James F,
Thanks for your help and the bug detection.
It is strange this .dll is missing and I was the first user to get the problem....
I"ll do the workaround and the test and let you know asap what happen.
Hope this fix the problem.
100PIER

James F,
I have done the workaround as you tell.
The restore operation completed with OK. So, some progress.
See attached new log file captured at the end of operation.

Unfortunatly, when booting the system PC i get a blue screen one minute after the bureau appears.
Seems a ashaci64.sys problem , but the blue screen appears few seconds;

i am convinced the Universal Restore piece of software (driver injection algorithm) is not stable at all.
It should be more tested, and i have spend lot of time to try to use it. Acronis should improve it.
100PIER

Does the system boot in safe mode? The asahci64.sys file is a driver for the ASMedia SATA controller on your system board. You may be able to disable or delete the service and then reinstall or update the ASMedia drivers from ASUS. Also you may want to try and update the Intel RST drivers if you can in safe mode.

One of the most complex restores that can be done is to restore to different hardware. I have tried all the major brands of backup software that can restore to different hardware, and can tell you that all of them (Acronis included) are not perfect when doing this.

Your restore seems to have gone okay, but there seems to be an issue with Windows loading the ASMedia SATA controller driver. The Universal Restore procedure seems to have done its job correctly (with the additional .dll file added), but there seem to be other issues when your system boots up in RAID mode. Possibly a conflict with the ASMedia drivers and the older Intel SATA drivers previously installed on your system when in AHCI mode.

James F wrote:

Does the system boot in safe mode? The asahci64.sys file is a driver for the ASMedia SATA controller on your system board. You may be able to disable or delete the service and then reinstall or update the ASMedia drivers from ASUS. Also you may want to try and update the Intel RST drivers if you can in safe mode.

One of the most complex restores that can be done is to restore to different hardware. I have tried all the major brands of backup software that can restore to different hardware, and can tell you that all of them (Acronis included) are not perfect when doing this.

Your restore seems to have gone okay, but there seems to be an issue with Windows loading the ASMedia SATA controller driver. The Universal Restore procedure seems to have done its job correctly (with the additional .dll file added), but there seem to be other issues when your system boots up in RAID mode. Possibly a conflict with the ASMedia drivers and the older Intel SATA drivers previously installed on your system when in AHCI mode.

James F,
I use only "standard" bricks: PC based on Intel CPU and chipset Z77, W7 64 bits SP1. etc..
The backed up system configuration is very up to date (all OS updates applied, all drivers up to date, BIOS up to date, etc..)
The restore is strictly on the SAME hardware !
So this is NOT a complex restore. This RAID 0 is a 'software RAID'. Only one RAID ! One volume ! No more simple performant desktop.

The current software version of Universal Restore feature does not handle correctly even a SIMPLE restore.
Because:
1) In the original AHCI system there was NO conflict between the active ASMedia drivers and the intel SATA drivers. The system was quite stable several weeks !
2) If you install from scracth a new W7-64 SP1 on the same hardware configured in RAID 0 mode and inject RAID 0 64-bits drivers (f6 key drivers) the system is up and running well, very stable, very performant. (see some brief report/screen shot in attachment).
3) If you do this very simple test : start a backup operation followed by a restore of the image just produced but activating a 'dummy' Universal Restore Option (3 tags: Universal Restore, amovible media, additional path) but without usb key and without path name provided.
Result: you get a 'failure operation' !! Please try to do this test.

It seems that activating 'Universal Restore' option the software becomes 'lost' and not handling properly the things in the right order.
I have personal doubt on how the algo is working..
Acronis documentation says Acronis Restore will find the "most appropriate" driver.
What does really mean "appropriate" ?
100PIER

James F,
Looking at the specification of the ASUS Motherboard, there are only 2 AHCI/RAID controllers: Intel & Marvell.
The ASMEdia SATA chip ASM1061 only supports hot plug for 2 External 6Gbs SATA port, no RAID capability.
The Marvell chip set up in this configuration is AHCI Mode to control the backup HDDs.
100PIER

100PIER,

I agree that the Universal Restore procedure could use some updating, and I would be the first to admit that it doesn't always work as expected. I'm only try to help you get to your goal. (Moving from AHCI to RAID).

you stated:
"The restore is strictly on the SAME hardware !
So this is NOT a complex restore. This RAID 0 is a 'software RAID'. Only one RAID ! One volume ! No more simple performant desktop."

This is not exactly true. The hardware IS different if the controller mode changes. It may still be made by the same company, and use the same drivers (although in a different mode, AHCI vs RAID), but it appears to the operating system as new or different hardware. (As you can tell by doing a restore from a backup made in AHCI mode to a RAID 0 pair in RAID mode and getting a BSOD.) In addition, you are not using "software" RAID mode, but "hardware" RAID mode if you are configuring the RAID pair using the "Control-I" procedure with the Intel RAID hardware BIOS (firmware) to configure and create the RAID array outside of Windows. A software RAID would be made after the installation of Windows by selecting two or more drives and creating the RAID using Windows OS dynamic disk / RAID features. The "hardware" RAID 0 volume you create in the Intel RAID BIOS (firmware) is presented to Windows as one volume with the Intel controller (and corresponding RST driver) providing the RAID support, not the Windows OS alone. This is sometimes referred to as "firmware / driver based" RAID.

I have asked if you can boot the system in "Safe Mode" (without BSOD), and you haven't stated whether you can or not. My only suggestion at this point is to try and remove the offending driver and re-install it. In addition, as mentioned in my earlier post, re-installing the Intel RST drivers could also possibly help with any conflicts that may have arisen from the change in mode from AHCI to RAID.

If you can boot into safe mode, you could take a look at the Windows event logs to see if you can track down the issues with the BSOD that reference the asahci64.sys driver/service or any other issues that may be related to the BSOD.

Since this is a restore/recovery issue, you can contact Acronis support for help with this if you choose to go that route. I'm sure that support will be limited if you are using the WinPE 4.0 Rescue Media, but there is no charge for help with restore/recovery issues from Acronis.

100PIER,
As James points out, windows 7 disables the registry values "operate modes" for those controllers which are not in use.

I suspect (and this is only a guess) that merely injecting the storage controller driver is not enough since the operate mode of the controller is being changed in BIOS. (AHCI > RAID)

I hope you might be able to start in SAFE mode for futher diagnosis. Performing a start up repair may also work, BUT do so only if JamesF suggests as I only started following this thread today.

James F,
To reply to your last post.
I agree with you my wording 'software' RAID was not correct at all. You are right, it is a hardawre RAID 0 because managed by the Intel chip not the OS.
My mistake provided that i used the "Speccy" application report which displays a 'software' RAID.... instead of 'hardware'....

I have tried to boot in "Safe Mode" (mode sans echec in french). Booting is starting but i got a BSOD.
Please look at the attached photo of the Blue Screen. What do you think about ?

So you last suggestion , if i understand well, is to create one (new) another AHCI configuration but without the ASMedia SATA drivers.
'removing' is 'deactivate' ? or 'uninstall' them ?
I don't know if it is easy to do, i will try.
i ignore also if the same driver handles also some USB ports.
Then i have to backup this 'light' config, then restoring it in RAID 0 Mode, and if it is working re-install the ASMEDIA drivers ? and see what happen..
100PIER

As a quick test, you could also disable the ASMedia controller for USB and eSATA in BIOS and try to boot.

James F, shadowsports,
1) please find in attachement the 2 last minidumps i got.
2) I have disabled the ASMEDIA ASM1061 Storage Controller at BIOS level (on board devices configuration) and successfully booted the restored image.
So, the PC is now running in RAID Mode 0. See attached screen shots.
I don't know why perf if 700 MB/s instead of 1100 MB/s i got in the W7 'new install' config RAID 0.
I don't know why Intel RST drivers version seems quite old compared to the version in the original AHCI config. Is the Universal Restore which does this retrogradation ?
100PIER

100PIER,

I would suggest updating the Intel RST drivers while booted to the newly restored system (RAID configuration). There is a chipset update utility on the Intel website that normally should be run first to help Windows identify the correct Intel components. After running the chipset update utility, reboot the system before installing the current Intel RST driver again. After installing the current Intel RST drivers, reboot, and test your system performance again. If all looks good, then re-enable the ASMedia SATA controller to see if you have the same BSOD issue.

The reason the Universal Restore retrograded the Intel SATA/RAID controller driver is that the appropriate Windows drivers were already present in the restored operating system. Universal Restore uses Windows default drivers first if it can find them. This normally allows the system to boot properly. The drivers being retrograded MAY have been the issue with BSOD, because the installed ASMedia driver may not be compatible with the standard Windows Intel SATA/AHCI/RAID drivers that Universal Restore specified, but may work fine with the newer Intel drivers.

There is no need at this point to do a new install of Windows 7 unless the performance and BSOD issues can not be corrected on the newly restored system running in RAID mode.

I'm also not clear on your performance test results. It looks like you have not used the same test parameters. Take a look at the test results images you have posted in this thread. One has a data size of 1000MB and the other has a data size of 100MB. This will certainly change the results. The updated Intel RST drivers may also provide better performance. Any additional software installed on the restored AHCI to RAID 0 operating system may also be different than when you did a clean install of Windows 7 in RAID 0 mode and could affect the performance results as well.

EDIT:
Doing some data transfer rate testing with the same program as you, my results were consistent with yours in that 100MB data transfer rate was slightly lower than 1000MB transfer rate on the same drives. (sequential)

James F,
Thanks for your help.
Yes, i have updated to 11.60 latest W7 Intel RST. performance are coming up again, a good thing. (performance Index Window = 7,8)
I 'l
But i forgot to apply first the the Intel chipset utility.
Is it o potential problem to have not done ? Or do i have to de-install again RST drivers, apply Utility and then re-install RST drivers ?

However, i get no longer a BSOD i report you some problem:

1) Booting is very very long (several minutes) why ?
2) I have had to reactivate via Microsoft a new key for W7, ( i don't understand why because i have a full DVD version, not an oem version)
3) Can you have a look on drivers issue detected via Panel Control or Touslesdrivers.com. I don't understand and how to fix these abnomalies, specifically CPU drivers ? Very strange...

i understand that Universal Restore algorithm is not enough elaborate , and should be significantly improved to detect that very up to date versions of drivers are present and so should avoid lot of painful tasks.
I have not yet enabled ASMedia chip.
I Let you know later .
100PIER

100PIER,

If the RST installation worked okay, the Intel Chipset Update Utility is not needed. You can download and run the Intel Chipset Update utility at any time. (I would still recommend you do so.) You should not need to run the RST driver install again.

Windows 7 will sometimes see changes to your hardware setup (new controller (or different mode), additional drives, RAID, etc) and prompt for re-activation. This is normal and is not a problem if re-activation goes smoothly.

On the items in Device Manger that have "caution" (yellow) indicated, right click and uninstall each device. After uninstalling each device, right click on any item (category or device) in Device Manager and select scan for hardware changes. This will re-install the appropriate drivers for each item.
I have seen this happen when installing the Intel RST drivers over older Windows or Intel drivers. It seem to always affect the Audio and CPUs.

You may have to download and install the Intel(R) Management Engine Interface V8.1.0.1263 for Windows XP/7/8 32bit & 64bit utility from ASUS (Listed under "Utilities" in the downloads section)

You boot speed issues could be related to the issues in Device Manager. Once these are corrected, you should notice your boot speed returning to normal.

Do not reactivate the ASMedia controller in the BIOS until all the other items in Device Manager show as normal. Be sure to install the latest driver from ASUS for the ASMedia controller.

James

James F wrote:

100PIER,

If the RST installation worked okay, the Intel Chipset Update Utility is not needed. You can download and run the Intel Chipset Update utility at any time. (I would still recommend you do so.) You should not need to run the RST driver install again.

Windows 7 will sometimes see changes to your hardware setup (new controller (or different mode), additional drives, RAID, etc) and prompt for re-activation. This is normal and is not a problem if re-activation goes smoothly.

On the items in Device Manger that have "caution" (yellow) indicated, right click and uninstall each device. After uninstalling each device, right click on any item (category or device) in Device Manager and select scan for hardware changes. This will re-install the appropriate drivers for each item.
I have seen this happen when installing the Intel RST drivers over older Windows or Intel drivers. It seem to always affect the Audio and CPUs.

You may have to download and install the Intel(R) Management Engine Interface V8.1.0.1263 for Windows XP/7/8 32bit & 64bit utility from ASUS (Listed under "Utilities" in the downloads section)

You boot speed issues could be related to the issues in Device Manager. Once these are corrected, you should notice your boot speed returning to normal.

Do not reactivate the ASMedia controller in the BIOS until all the other items in Device Manager show as normal. Be sure to install the latest driver from ASUS for the ASMedia controller.

James

James F,
I have done ALL the corrections:
a)Intel Chipset Utility OK
b)Reactivate W7 Product Key OK
c)Fixed all devices with the 'yellow' caution warning via the right click_uninstall_scan method on Device Manager Panel. OK
d)Re-installed the Intel(R) Management Engine Interface V 8.1.0.1252 OK , will do soon update to .1263 or better.
e)Remain a NVIDIA pb detected at Maintenance Center (see attachement). Do i have some other thing to do to avoid this crash ?
f)Do a successull backup via standard Linux CD rescue. (restore not tested)
g)Try to enable the ASMEDIA controller (the driver ASM106x SATA Host Controller Driver 1.3.8.000 was already installed).
Unfortunatly when reboot ==> Blue Screen , see dump in attachement.
What to do ?
So, in summary the full system is not up and running well as it should do.
Migration fro AHCI Mode to RAID 0 is a real challenge !
100PIER

100PIER,

To correct the Nvidia error, download the latest Nvidia Graphics driver for your system, then use control panel to "remove a program" and un-install the Nvidia software on your system. After rebooting, install the newly downloaded Nvida driver. Then reboot.

With the ASMedia controller still disabled, you should see if you can un-install the ASMedia drivers via control panel. If so, do that and then reboot.
Re-enable the ASMedia controller, and see if the BSOD issues still persist. If not, install the ASMedia drivers and reboot again. Check for BSOD.

You can check you system for old non-active device drivers (for the controllers) in Device Manager using the following procedure: http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-driv…
Be careful to only remove device drivers that you know are no longer needed.

Glad you have already made a backup, smart, very smart.!

James F,
I have suceed to install the V 1.3.8.000 ASM106x SATA Host Controller Driver. I have had to uninstall the "restored" version.
See some attachments about the progress.
Remaining stuff: try to fix critical events
100PIER

James F,
Some attachments of critical events before nvidia driver re-install.
I ignore if all events be fixed after re-install.
what is comsurrogate issue ?
Microsoft Office also have to be re-activate ..
Started Acronis 2013 PP+ and do a successful backup.
Is a restore of this 'raid' config image should work with the current WinPE 4.0 CD rescue i have ? with Linux CD Rescue ? (without Universal Restore option activate !)
Any comments welcome
100PIER

James F,

1) The NVIDIA driver re-installation fixed 4 critical events. A good progress.

2) Now, it seems the only sticky bug/problem is the random "COMsurrogate" bug. I ignore how to fix it.
Any suggestion ?

3) Windows TI 2013 PP+ works fine to do Backups of the RAID configuration. No problem. Full Backup is very quick.

4) For a restore of this RAID 0 configuration do I have to use mandatory the WinPE 4.0 CD Rescue ?
Do you have tested a restore of a RAID 0 configuration using a Linux CD Rescue ?

100PIER

100PIER,

Looks like you are making good progress in getting the issues resolved.

1. Glad to see that corrected the Nvida errors

2. COM Surrogate errrors. I'll take a look at what I can find, but can not offer a fix yet.

3. Great

4. You should use the WINPE 4.0 Rescue Media to do restore since it has the driver support for your RAID.
The Linux based rescue CD could be used to restore to your RAID ** ONLY ** if it detects and "sees" your RAID 0 array as one drive.
I have used both WinPE and the Linux based Rescue Media to restore to a supported RAID with no problem. Universal Restore will not be necessary since you are backing up from the RAID, and restoring to the RAID.

Check out this post for the COM surrogate errors. http://forum.acronis.com/forum/35064

I see a significant less of transfer rate performance between a 'light' No SP1 W7-64 RAID 0 and a 'full' W7-64 SP1 RAID 0 configuration.
(see attachments)
May be 30% less.. Is it normal ?
100PIER

Are the only differences the Service Pack? Is there any other software installed on the SP1 system that is not installed on the pre-SP1 system?

Performance issue:
Yes, There are some other software applications (several tens) installed on the SP1 system that are not installed on the pre-SP1 system.
May be this is the reason why performance transfer is quite higher with a 'light' system. But it is not a major issue for me. Fixing critical events is a priority.

RAID 0 system Restore (without Universal Restore option activation):
I used the Linux CD rescue (build 6611) . (see other post about build 5551 vs 6611 ??)
The RAID 0 volume is well detected (unique volume).
Restore operation completed fine BUT you have had to be very careful when setting restore parameters:
1) you have first to reinitialise manually the previous disk system with the Acronis Tools, if not doing this cleaning restore parameters settings stops (you have to go back again).
2) then be careful to indicate the 2 partitions to restore ( the 1-1, then the C: ) , one is a reserved system partition, the other one is the W7 system partition himself.
100PIER

Restore parameters settings phase: see attachment

Acronis build 6611 or 5551 ?

Look at this shots, i don't understand why i have a build# 6611 and another one is build# 5551.

Build # 6611 is on the CD made from the .iso file downloaded from Acronis web site PP+ (even if #5551 is displayed on the web, the real build is #6611) ! somewhere a mismatch....

Build # 5551 is on the CD i made from the Windows Acronis TI 2013. (one of the first recommended task to do after Acronis TI 2013 PP+ installation).

100PIER

I see the differences, but I see 5511 and 5551, not 6611 as you mentioned. Could just be a programmers typo.

James F,
So, here in attachment are the performance tests results (AS SSD and CDM) after updated iRST drivers to V 11.6.2.1002.
Result is a Significant improvement vs V 11.6.0.xxxx. So, i recommend to use 11.6.2.1002. (don't use V 12 beta , you get a blue screen)
No longer a performance difference between a 'light' W7-64 pre SP1 system (about 5 Go) and a W7-64 SP1 system (about 24 Go with AIK, ADK, Videos apps, etc..).
Backup operation (Linux CD Rescue) of 'light' system is < 45 sec, backup operation of 'full' system is less than about 4 mn.
So, performance are here as expected.

The remaining issue is the COMsurrogate bug.

Regarding the 'mspack.dll' do we have to wait from Acronis a fix in a future version ?
100PIER

100PIER,

Both the COM Surrogate Bug and the mspack.dll missing file are being addressed by Acronis in upcoming builds as far as I know.

Thank you for posting your comments and screen captures.

James

James F,

Backup operation from Windows no longer work.
I don't know why.
The Error Code = 0x000B03EC

The backup operation under Linux CD Rescue works fine.

So, what to do ?
100PIER

Try a repair install of 2013 again.

Are you outside your 30 day Acronis support period?

Colin B,
Yes, i am outside of the 30 day Acronis support period.
What is a repair install ?

I have recreated the backup description, and its worked.
I think software not really reliable when a such situation occurs. Works, don't work, works, ....
100PIER

Run the TIH 2013 installer again - it will offer you a 'repair' option.

I have run TIH 2013 installer with 'repair' function.
It seems now all is working well and stable, but why we have to 'repair' TIH ?
Does it mean this software is too 'complex' and have some time to time to be cleared and repaired ?
100PIER