REVO 3 X2 can not restore

Does 2013 in Windows see everything OK?

I don't recall anyone in beta testing mentioning if they had a revo drive.

Have you tried pressing the F8 button whilst booting form the CD adn entering after the word quiet... NOAPIC ?

Do you know if Linux OS' work OK with Revo drives?

Hi,

REVO 3 X2 is a new drive with nothing on it; I want to test the restore process on this drive.

Upgraded from 2011 to 2013 with no issues, created new backup files just incase, all drivers for REVO 3 X2 loaded to Windows 7 AND during the Plus Pack option when booting from CD.

Please escalate to high level engineering

Thanks

If the Linux based Acronis Rescue Media is seeing more than one REVO drive than proper support for the drive/controller combination is not contained on it. You would probably need to create a WinPE based Acronis Rescue Media. You would need to inject the correct 32 bit drivers for the REVO into the .wim file before creating the Acronis Rescue Media.

Hi,

What does .wim vs iso do differently each ?

Refering to Acronis article 34318

The .wim file is the file used by Acronis WinPE Builder to build a WinPE based ISO file. The .wim file is part of the Windows 7 AIK http://www.microsoft.com/en-us/download/details.aspx?id=5753 that has to be installed to be able to create the WinPE ISO using the Plus Pack Acronis WinPE Builder. It is the base Windows 7 image used for this purpose. Using command line tools for the Windows 7 AIK, additional Windows 7 drivers can be injected into the .wim file before running the Acronis WinPE Builder application to support hardware that Windows 7 does not by default. You can install the Windows 7 AIK and then use the Acronis WinPE Builder to create WinPE based Acronis Rescue Media. This is an optional Rescue Media based on Windows 7 not Linux, so driver support can be added for new hardware. See this for help on creating the WinPE ISO for 2013. http://kb.acronis.com/content/34318

Refering to Acronis article 34318

What do the different options in image 6 mean?

Thanks

Normally you would choose the first option to build the ISO. If you are going to use Windows 7 AIK command line tools to build the ISO, you would select the option to update the .wim file with the Acronis True Image components, then continue with the .wim file manipulation outside of the Acronis WinPE Builder application.
I have found it easiest to use the Windows 7 AIK command line tools to inject drivers into the .wim file that is found in the folder you create after using the command "copype x86 c:\winpe_x86". There is a .wim file that can be used by Windows 7 AIK command line tools to inject the driver(s) that are required. After the injection of the correct drivers, following the steps to create the ISO with the Acronis WinPE Builder is the same as described, but the created ISO will have the drivers that were injected into the .wim file present. You can use either method (Acronis WinPE Builder or Windows 7 AIK command line tools) to build the ISO, but your have to use the Acronis WinPE Builder to modify the .wim file separately or during the automated WinPE ISO build process with the Acronis' Media Builder application to have the True Image Home 2013 application injected into the .wim before/during the ISO creation.

Thanks,

Acronis really needs to better document in a simple way how to slipstream the REVO drivers into the WinPE so as to work, the articles completely miss this point, please tell Acronis to update the articles etc..

Just to clarify, during the restore using WinPE, do you still have to provide drivers on a USB for PP to use just before looking where to restore, or should the "injection" process take care of it ??

Thanks!

When you inject drivers into the .wim and create an ISO, the drivers injected into the .wim are to allow the WinPE Rescue Media to access your hardware correctly during backup/recovery/clone. If the Operating System was installed on a different controller and you are restoring/recovering the Operating System to a new controller, you must use the Acronis Universal Restore option and have the correct drivers available to use during the restore and during Windows first boot. The WinPE based Acronis Rescue Media only supports 32bit drivers. The True Image 2013 Rescue environment does not support 64bit drivers. You need to have the correct drivers (32bit/64bit) for your system available for the Universal Restore option to use during restore/recovery. I usually place my drivers in a folder on the same drive as my backup images and have Universal Restore look there for them during the recovery. Universal Restore will look at the Operating System during restore to check if the drivers are already present and use those if it can, if not it will look in the location(s) you specify and use the drivers it finds there if appropriate. After performing a restore, sometimes it takes Windows a couple of tries to boot correctly after using Universal Restore.
The drivers you need to inject into the .wim file are the 32bit drivers for the REVO 3 X2 located in the i386 folder in the zip file from OCZ Tech. http://www.ocztechnology.com/resources/drivers/ocz10xx-1.3.6.17083.zip. If you are running Windows 7 64bit, you will need the drivers contained in the amd64 folder during Universal Restore. I would create a folder on your backup destination drive called REVO and copy both the i386 and the amd64 folders from the zip file into it, then have Universal Restore use both folders as a place to look for drivers during recovery/restore.

James, great info !!!

So use only 32 bit drivers to create the iso --> CD; AND have ready the 64 bit drivers (and 32 bit for good measure) for the Universal Restore to use when looking for the destination drive? The original is Win 7 64-bit

Why does ACRONIS not tell us this in their articles, especially the 32 bit limitation!!??

Also, can I also ‘Inject" the 64 bit inf into the .wim as a safety, or will this cause issues?

Thank you for the critical info!!

Will try tonight!

Thanks

Do not inject 64bit drivers into the .wim. The True Image 2013 (and earlier) rescue environment (application) that runs from the bootable WinPE does not support 64bit drivers. They are not needed to be able to access your hardware from the WinPE media. If you have trouble injecting drivers into the .wim before creating the ISO, I can provide some guidance there as well. I tested injecting the OCZ drivers into the .wim file and created a WinPE ISO with no problems. Since I don't have a $2700 drive to test with, that's are far as I can go. You are using a very specialized piece of hardware and your needs are different than most users of backup software. Acronis is very powerful and the ability to create WinPE Rescue Disks is of utmost importance to users such as yourself. Better documentation and/or an easier method to inject drivers and create the ISO would be helpful, but the average user should be fine with the Linux based Rescue Disks. I use both on my systems. I have created Windows 8 based WinPE rescue disks using the Windows 8 ADK and the Windows 7 AIK in combination, and THAT really took some work. (The Windows 7 AIK works fine on Windows 8 btw). I wish you the best of luck in your attempts with this. I have found that although Universal Restore works well, it does not always work with every piece of hardware. You may have to do a clean install of Windows on your REVO drive anyway, and then restore your data files from your backups. Once you do though, backing up from within Windows or using the (modified/driver injected) WinPE Rescue Disk using True Image 2013 will work, and you will not have to worry about having to use the Universal Restore option during recovery/restore, as it won't be needed since you are restoring to the same hardware.
Much of the information I have shared can be found in the KB articles, it is just difficult to locate and sometimes not clear.
Please keep us informed as to how this works for you. I'm sure other users of REVO products could use your feedback.

Hi Again,

After I add the inf, the MS doc says

""When you finish customizing the image, prepare the image for deployment by using the peimg /prep command.""

What does this mean, how to do exactly ?

Best

Syrob

I will post step by step instructions for you, in my next post, after documenting the steps. I take it you have installed both 2013 and the Plus Pack as well as the Windows 7 AIK. If all of these are in place the instructions I post can be followed to inject your drivers and create the ISO file.

James,

This thread features a user posting a resolution for this topic. Might be enough?

http://forum.acronis.com/forum/24939

How to inject drivers using DISM during the Acronis WinPE Builder ISO creation Process

This procedure assumes several things.
They are:
True Image 2013 by Acronis is installed.
True Image 2013 Plus Pack by Acronis is installed.
Windows AIK for Windows 7 is installed
Windows AIK for Windows 7 SP1 is installed (optional)
You are running Windows 7 (any version)
The default installation folders were used on the "C" drive.

Once you have the items above installed, the procedure to inject additional Windows drivers into the winpe.wim file that Acronis WinPE ISO Builder uses to create the WinPE ISO only requires a few additional steps be added to the Acronis WinPE Builder instructions.

Following the instructions found here: http://kb.acronis.com/content/34318

Step 1
Enter the Windows Deployment Tools command prompt using the following procedure:.

Click Start / All Programs / Microsoft Windows AIK

Right click Deployment Tools Command Prompt and click Run as Administrator

(Be sure to click run as Administrator, or you will have problems in several of the next steps)
You will be in a Command Prompt at "C:\Program Files\Windows AIK\Tools\PETools"

Step 2
Copy the x86 files needed for Acronis WinPE Builder.
Enter the following command and press enter:

copype x86 c:\winpe_x86

You will see several files being copied, and be left in a Command Prompt at "c:\winpe_x86"

**************

We are now adding the additional steps to the Acronis KB article referenced above:

At this point we will inject drivers into the "winpe.wim" file located in the directory "c:\winpe_86"
Remember that ALL driver files to be injected MUST be 32 bit.

Create a folder (or folders) and copy your driver files into it that you wish to inject into the winpe.wim file.

You must provide these drivers. (usually they can be downloaded from the manufacturers site)
They must consist of extracted (not zip files or .exe installation files) .inf files along with other support files (Normally .cat and .sys files)

As an example for REVODRIVE 3 and REVODRIVE 3 X2:

From the Command Prompt (you should still have it open) enter the following command and press enter to create a folder named REVO

md C:\REVO

Copy the correct drivers for the REVO drive/controller into the REVO folder
You can use Windows Explorer to do this, but do not close the Command Prompt window.
In this example the following files should be in the REVO folder.
ocz10xx.cat
ocz10xx.inf
ocz10xx.sys

Once you have the driver files ready, we can inject them into the winpe.wim file.

This conists of:
mounting the winpe.wim file
injecting the drivers
committing the changes and unmounting winpe.wim file

Using the example driver files and folder from above:

(Modify the commands below to reflect the name of your driver folder(s) and driver files.)

Enter the the following commands (and press enter after each one) from the Deployment Tools Command Prompt that you already have open.
(You should still be at "c:\winpe_x86")

md c:\MOUNT
(This creates a folder called MOUNT on your "C" drive to provide a location for the image to mount.)

imagex.exe /mountrw winpe.wim 1 c:\MOUNT
(This mounts the winpe.wim file in read/write mode)

dism /image:c:\MOUNT /add-driver /driver:"C:\REVO\ocz10xx.inf"
(This is the driver injection command)
(You only need to point to the ocz10xx.inf file in this example).

At this point you can add more drivers if necessary using the same "dism" command as above, substituting the correct folder and driver file names.

After you have added your driver(s) we need to commit the changes and unmount the winpe.wim file.

!! Note: Make sure to close any Explorer windows that have your working directories open, or the unmount process “sticks” and doesn’t unmount correctly !!

Enter the following command and press enter:

imagex.exe /unmount /commit C:\MOUNT

**************
Once you have successfully completed the unmount you will continue with Step 3 in the instructions in the KB article referenced above.
Be sure to point the Acronis WinPE Media Builder to the "c:\winpe_86\ISO" folder in step 5.
In Step 7, be sure NOT to save the new ISO that you are creating into the c:\winpe_86" folder or any of its subfolders.
If you want to create an additional new or different ISO, you do not want anything added to those folders before hand.
I usually save my ISO's to my Desktop with a name that reflects the drivers installed. (You can always move them later)
In this example I might use something like 2013_REVO_Rescue.iso.
Once you have created the ISO file, you can burn it to a CD/DVD or mount it using third party ISO mounting software and copy the contents of the ISO file to a USB flash drive to have a bootable USB flash drive version of the Rescue Media. (You can also copy the files on the created CD/DVD to a USB flash drive instead of mounting the ISO)

(If you wish to create other ISO files with different drivers, you should follow this procedure a second time, but you will need to delete the "c:\winpe_86" folder before issuing the "copype x86 c:\winpe_x86" command in step 2 to give yourself a clean winpe.wim file to start with.)

Thanks Pat for the additional link. I like to use the procedure outlined above because it works well and only adds a few additional steps to the Acronis Plus Pack WinPE 2012/2013 Media Builder instructions.

Hi All,

I get these two errors

------------------------------------------------------------------------
c:\winpe_x86>md C:\REVO

c:\winpe_x86>md c:\MOUNT

c:\winpe_x86>imagex.exe /mountrw winpe.wim 1 c:\MOUNT

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Mounting: [c:\winpe_x86\winpe.wim, 1] -> [c:\MOUNT]...

[ 0% ] Mounting progress
[ WARN ] The image you are mounting has already been mounted at c:\$Recycle.Bin\
S-1-5-21-3146140248-16744116-4049203431-1000\$R74IHQB\mount. You should not com
mit both images.

Error mounting image.

The specified image in the specified wim is already mounted for read/write
access.

c:\winpe_x86>

------------------------------------------------------------------

c:\winpe_x86>dism /image:c:\MOUNT /add-driver /driver:C:\REVO3\i386\ocz10xx.inf

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Error: 2

Unable to access the image.
Make sure that the image path and the Windows directory for the image exist and
you have Read permissions on the folder.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

c:\winpe_x86>

------------------------------------------

Best

Syrob

Did you try to run the imagex tool earlier before following the commands I listed?

Hi,

Yes I tried you very detailed list and this is what happend

How to unmount?

Best

It looks like you mounted an image and then did not unmount it and deleted the mount folder.
Try running the two commands (pressing enter after each) from the Deployment Command Prompt command line.
imagex /unmount c:\mount
imagex /unmount c:\$Recycle.Bin\S-1-5-21-3146140248-16744116-4049203431-1000\$R74IHQB\mount
This should unmount any winpe.wim files your have mounted.
Then start with the imagex /mount command again and see how that goes.
Be sure you have all Windows explorer windows closed before running the unmounts.

Hi James,

Bingo!

Will start again

Best

Borys

repeat

repeat?

Hi james,

Sorry I double posted and just changed to repeat,

Burning the iso now!!!

Will let you know

Thank you so much for your help

Best

syrob

In post #17 above, you created a folder called REVO, but in the later steps you used C:\REVO3\i386 for your drivers. That is fine as long as your drivers were in fact in that folder. Did your drivers inject okay? Also if you create a folder name with spaces in it, or the file names themselves have spaces in them, the path to the drivers should have " " around them.
ie: .../driver:"c:\my drivers\i386\intel RST" (just for future reference)

Nice post James F. I will use this post as reference for WinPE driver injection!

Hi James,

CD saw REVO fine, installed both 32 and 64 bit drivers using universal install, then I was at the point of “select destination of disk 2”, had chosen the REVO3 X2 890GB drive, clicked next, which would normally bring me to the final task list to verify before restore, instead I keep getting an error message immediately, and never see the final task list :

TrueImage.xex- Application error

The instruction at 0x01397c14 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program.

Tried several times with same type of error message.

Memtest on my computer reports no errors, and just for fun I installed Win 7 on the REVO to see if there were any hardware errors, installed fine, no errors detected.

Also, did a verify on the master backup once I went back to the old HD, no issues with it either.

This is not my hardware as far as I can tell, I am writing this of off the old drive etc.

So close yet so far…..

Your instructions were the best anywhere BY FAR!!

Thanks again

Best

Syrob

I've had this error before when using Universal Restore, and have not been able to track it down yet. It may be in issue in the trueimage application itself. Since you now have a bootable CD that you can use for recovery (as well as cloning and backup) that can see your REVO drive, you would not need to use Universal Restore to recover/restore your files to your REVO if your backup is made from the OS installed on it. It's a shame that the Universal restore when running in WinPE has this issue, as Universal Restore under the Linux bootable CD does not seem to. I am going to report this to Acronis to see if there is a resolution or fix for Universal Restore under WinPE.
Glad you can now confidently backup and restore your REVO drive. Be sure to make several copies of the bootable CD so you dont have to build a new one. If a new version or build of 2013 comes out, you will need to create a new WinPE bootable CD and will have to inject the drivers again if you want an updated copy of it.
Glad to help.
How about a review of the REVODRIVE 3 X2 at some point. I would really like to know how you feel about its performance and whether the cost can be justified.

James

Try running the restore with only the 64bit drivers available to Universal Restore. It may be trying to use the 32bit drivers. This is probably not the issue, but is worth a try. If you can't get Universal Restore to work, the only option short of using a different product, would be to install Windows and any applications you need to the REVO and then restore your data files either from your backup or copied off your old drive to the REVO.
Keep us posted.

Hi James

The performances is great on my other one, the price here is amazing PLUS 15% off !!!! with promo code!! i.e $754.15 for the 960 GB drive REVO 3 X2 !!!

http://www.newegg.com/Product/Product.aspx?Item=20-227-742

Best

Syrob

I didn't realize that there were so many versions of it. I saw one at MAC Connection that was over $4000.00!

Many have this exact same drive for $2,700.00

That's what I saw earlier when I referenced that price in an earlier post. Will keep these drives in mind for future purposes. Looks great to me. Hope they last a while.

Hi James,

Sure enough it was universal restore that was causing the problem, did the restore without it, completed sucessfully, however, booting Win 7 on REVO 3 get a blue screen at the flower logo, windows repair, even reloading the drivers does not find anything wrong, all tests run according to their logs..

This is possibly due to the fact that the original Win 7 installation never really "saw" the REVO 3 as a new device fully booted up; as all I was able to do was install the drivers for REVO 3 under the old drive, (not enough option ROM space to have new REVO 3 by old HD REVO “1” on Mother Board at the same time.)

That is why I was hoping universal install would work...

Please provide ACRONIS feedback that they need to repair Universal Restore under Windows recovery.

Again, so close yet so far…

Best

Syrob

>>

I have reported this issue to Acronis. You should also put in a request to support. It is possible they could create a working Linux based recovery ISO for you that contains the correct support for the REVO. You may have better luck with Universal Restore under the Linux environment. Be sure that support understands you have the Plus Pack, just in case they do build you a custom ISO. It would still need the have the Universal Restore functionality. Wish I could help more.

I'm about to go through this tonight as well, unfortunately. I'm moving my system from a X58 based motherboard to a X79 based one, and I'm moving my Revo 3 x2. I was hoping universal restore would allow me to install the correct drivers during the move.

Further testing of the Universal Restore under WinPE led me to a possible solution to the error:

The instruction at 0x01397c14 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program.

I found that if I used the Tool "Add a new disk" and wiped the target drive before starting the restore/recovery, I did not get this error on my system.

James F wrote:

Further testing of the Universal Restore under WinPE led me to a possible solution to the error:

The instruction at 0x01397c14 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program.

I found that if I used the Tool "Add a new disk" and wiped the target drive before starting the restore/recovery, I did not get this error on my system.

Hi James,

Tried what you recommended, did not work.

0x00697C14 or 0X00547C14, or 0X01397C14 error  all memory at 0X00000000.

Hum, always ends in 7C14, does that mean anything?

Also, some times it says “Tool tip: TrueImage.exe” or some times just plain “TrueImage.exe”  both with “Application Error”.

Wow, the only reason our company went with Acronis was for the Universal Restore, and now when we finally need it; it is broken Ugh!

Since we both can duplicate this error should it not be easy for Acronis to track it down?

Best

Syrob

There might be some difference if James doesn't get the error with the workaround but you still do, run memtest86 for a few hours on your system. True Image gives RAM a major run for its money, so it will be worth checking that the RAM shows no flakiness whatsoever.

You can also try using the Windows diskpart command line utility to clean the drive while in the WinPE environment. I may have done this before using the "Add a new drive tool" (not sure). The errors may also be related to the injected REVO driver. It could be that the Universal Restore application is trying to use the injected driver to access the drive and may not be able to do so correctly, resulting in the memory errors you are seeing. I have already started a support ticket for some issues I am having with Universal Restore under both the Linux and WinPE versions of the 2013 build 5551 version of the Acronis Rescue Media when trying to restore a backup of Windows 8. I am still testing the Universal Restore feature with some Windows 7 backups using the Linux and WinPE 2013 Rescue Media.

Hi Colin,

Good idea, already ran it last night, no errors as I suspected

Best

Syrob

Hi All,

Has there been any feedback from Acronis R&D on the issues?

Best

Syrob

Hello Everyone,

Thank you for your posts and your continuous assistance with this issue.

Syrob, we are sorry that you experienced this recovery issue. We are currently investigating it in the case that you submitted and I will make sure that we reach out to you to collect proper information. It will help us understand what is causing this problem. Currently there is no solution to it, but I am certain that we will get to the bottom of it.

If you need additional assistance, please do not hesitate to contact me directly.

Thank you.

You've got a reply on "REVO 3 X2 can not restore":
*****
Hello all,

*REVO USER,*

Could you please boot the system from Acronis Boot Media and obtain Acronis
system report? This option is available at the main menu of the CD.

Attach the file to your next message.

Thank you.

What system report, you can not make one from the boot CD??

I think Acronis is referrring the the Linux based Rescue Media (Boot CD). If you included the System Report option in the creation of the Linux based media, you can run the "System Report" after booting. You can also download the Linux based ISO from your account and burn it to a CD/DVD. It includes the "System Report" option by default.

Please find the two system reports I ran:

System Has TI 2013 with PP

REVO X2 drive (Gen 1) 223 GB drive; where OS resides, and what is backed up to Intel RAID to "my backups".

Want to move to New REVO3 X2 (gen 3) 890 GB drive; drivers installed for this drive on old OS drive REVO X2 drive (Gen 1) 223 GB drive (and therefore the backup) but New drive itself NOT installed in PCI-e slot as it is not possible for both Gen 1 and Gen 3 drives to reside in this MB at same time.
So was hoping to remove old REVO X2 drive (Gen 1) 223 GB drive (where OS resides, and what is backed up to Intel RAID to my backups), and replace with New REVO3 X2 (gen 3) 890 GB drive, where restore was going to be told to restore to.

Made Rescue disk (Linux), with REVO X2 drive (Gen 1) 223 GB drive in place ran CD system report AcronisSystemReport_Sep_18__2012_Revo X2 Gen1.zip

Made Rescue disk (Linux), with REVO3 X2 drive (Gen 3) 890 GB drive in place ran CD system report AcronisSystemReport_Sep_18__2012_Revo 3 X2 Gen3.zip.

Please see attachments

Thanks

Syrob

Hello Syrob,

Thank you for getting back to us.

Our QA Team has created a task for this issue and our Expert Engineer will keep you updated about it.

Please let me know if you have additional questions.

Thank you.

Has this problem already been fixed? Because ive to undergo the same process in the comming days.

I already prepared an WinPE ISO with the Revodrive 3 X2 32bit drivers. Went all okay, but now i have to restore the same thing as Revo user as soon as i recieve my Revodrive 3 X2.

My problem is a bit complicated, because my old revodrive X2 (OS DISK) died a few days ago. So i restored my OS on a mechanical 1TB disk. The backup is placed on a totally different (500GB WD disk) drive. Dunno if i get the same problem as RevoUser. We shall see in few days.

Hello Everyone,

if you face an issue similar to described above, please gather the following information:

1) system report created in Windows

2) system report created in Linux from bootable media

3) photos of all RAID configuration from BIOS

and contact Acronis support.

As a workaround you can use WinPE media with drivers for your RAIDs.

Thank you.