Aller au contenu principal

Rescue Media help for Windows 10 (AIK 5.0) and RAID 1

Thread needs solution

I am trying to create a new USB Rescue media stick for ATI 2017 and to add the correct drivers for my Lenovo P70 with RAID 1 installed. Is there a straight-forward way of creating this without a lot of separate commands? Any help here would be appreciate. Thank you

0 Users found this helpful

Would we be correct in assuming that you have tried creating recovery media without speical raid drivers and it would not recognise the riad partions? From the specification of the Lenovo P70 it looks like the raid would be eithere vai the Intel Chipset (Intel Rapid Storage Techniology) or created by OS - which I would not be possible if it is the boot partition.

Intel Rapid Storage Techniology does not, if I recall correctly, require a driver. When the PC boots it scans the attached storage and see that the HDDs have a 'raid signature' and recognises the raid partitions like any other partition. This can be very useful if you replace the main board on the compute it recognises the raid when it boots (I have seen this happen several times).

Hope this helps

Ian

 

After creating the WinPE media you can use the tool at this link to help you inject the drivers into the boot.wim file which you will find in the Sources folder in the WinPE media

http://dismgui.codeplex.com/

The RAID 1 support for the P70 is in the Intel Chipset and there are drivers that are required to see the array in Windows 10. I can boot off of the array for normal operations. There needs to be a driver to for the Recovery Media to see the array. Otherwise I cannot restore the C:\ drive in case of failure. The tool link described below has a 2014 date. Will it work with WinPE 5.0 for Windows 10?

Thank you for the response.

IanL-S wrote:

Would we be correct in assuming that you have tried creating recovery media without speical raid drivers and it would not recognise the riad partions? From the specification of the Lenovo P70 it looks like the raid would be eithere vai the Intel Chipset (Intel Rapid Storage Techniology) or created by OS - which I would not be possible if it is the boot partition.

Intel Rapid Storage Techniology does not, if I recall correctly, require a driver. When the PC boots it scans the attached storage and see that the HDDs have a 'raid signature' and recognises the raid partitions like any other partition. This can be very useful if you replace the main board on the compute it recognises the raid when it boots (I have seen this happen several times).

Hope this helps

Ian

 

I can boot off of the array (It is the C:\ drive) on the system. The issue is that the Recovery media does not see the array to allow me to create a backup using that media or to restore to it because it can't see the array. A friend of mine created a USB stick from TI 2016 Recovery that does work, but I would like to create an equivalent stick for TI 2017.

Thank you for your response.

Harris, have you actually tried creating the WinPE Rescue Media for ATIH 2017 'as is' and booted from this to confirm whether you will need additional device drivers for your RAID array or not?

Please see post: 100770: Guide to Add Drivers to WinPE Recovery Media which has comprehensive information on the process to add drivers, but the starting point has to be that you first create the base WinPE Rescue Media.

I suspect as it is very common driver it would be in Windows 10 version of WinPE.

Ian

I don't believe the Intel Rapid Storage Technology (IRST) drivers are included in the Microsoft ADK drivers by default. I've typcially had to inject them after the fact.  I'd love to see driver injection included in the WinPE build process and have suggested this several times through feeback - please do the same. The Linux media is never going to do this so if WinPE is the only option, the easier we can make this process (especially as newer sysetms with NVME drives are being set in RAID mode even for single drives), this will only make the product more user friendly.  

I have done a good bit of testing using NVMe drives in RAID arrays.  In all cases thus far the drivers necessary to access the array are Intel RST drivers.  It is absolutely necessary at this time to inject those drivers into WinPE boot media to have access to these RAID arrays.

 

the tool I linked above provides an easier to use GUI interface for injesting the Intel drivers into WinPE boot media than that of command line injection.  Even though the DISMGUI is a 2014 product it works fine with ADK 5.0.

Thank you. I created the rescue media, but when I tried to do a backup with the USB stick, it showed 2016 TI not 2017 TI. Also, I got a message that I was using a trial version of TI. I'm not sure what is wrong here. Are the TI tools out of sync with the main program?

Steve Smith wrote:

Harris, have you actually tried creating the WinPE Rescue Media for ATIH 2017 'as is' and booted from this to confirm whether you will need additional device drivers for your RAID array or not?

Please see post: 100770: Guide to Add Drivers to WinPE Recovery Media which has comprehensive information on the process to add drivers, but the starting point has to be that you first create the base WinPE Rescue Media.

Yes, I cannot see the RAID 1 array without injecting the Intel RST drivers. Also, when I create the WinPE Rescue Media, I get a message that I am using a trial version of TI 2016! I followed all of the instructions, but I'm not certain why this message is happening. I can't use the rescue media to do a backup. I don't know why the media creation has to be so difficult with the multitude of command-line items to create the WIM file with the correct drivers.

DISM GUI cetainly makes it easier and am glad it's available - it's not overly complicated and is pretty easy to use for the typical home user.  However, I do continue hope that driver injection functionality becomes an integral part of the Acronis True Image Home product.  Driver injection is already part of the Universal Restore media builder, so it seems more than feasible.  Unfortunately when using the universal restore media builder to create WinPE, you can only create universal restore media - weird ,since you can build Linux Acronis bootable media using the same tool and have both True Image and UR on the same disk.

If it's not possible to add such drivers into the default Linux media sooner (or at all because of driver limitations with Linux), WinPE is the only way to go.  With most newer laptops using NVME drives and being set in RAID mode by the manufacturers, this is becoming more of a necessity for home users and we're seeing it even more with the newer Intel network drivers too.    

Harris, format your usb flash drive and create the media again to be doubley sure if it is showing as 2016 and/or trial if you have 2017 installed and registered.  If it is still producing such media after that, I would download the full 2017 installer, right click and "run as administrator"  and see if you get the option to repair or install again. If you can repair, that might fix things easily.  If not, and this was an upgrade gone bad, using the cleanup tool (it works for 2017 even though the documentation hasn't been updated yet) and starting fresh should get you back on track, but you'd have to cresate new backup tasks and start with some new backups again.  You can still use your old backups and import them if desired, but I would just hold onto them for posterity and/or delete them once you are comfortable with any new backups and the amount of history you need to retain before permanently deleting older backups. 

Hey, I just found another GUI ADK tool as well, called VDISM.  Looks like it's a bit more polished and recent than DISMGUI.  There's also a video tutorial on youtube.  DISMGUI has been great for me, but I just downloaded this new one (last updated April 2016) and am playing around with it right now. 

Original (tried and true)

DISMGUI

DISMGUI Youtube Tutorial

New (looks promising and seems to be newer)

VDISM

VDISM Youtube Tutorial

 

Bobbo_3C0X1 wrote:

Harris, format your usb flash drive and create the media again to be doubley sure if it is showing as 2016 and/or trial if you have 2017 installed and registered.  If it is still producing such media after that, I would download the full 2017 installer, right click and "run as administrator"  and see if you get the option to repair or install again. If you can repair, that might fix things easily.  If not, and this was an upgrade gone bad, using the cleanup tool (it works for 2017 even though the documentation hasn't been updated yet) and starting fresh should get you back on track, but you'd have to cresate new backup tasks and start with some new backups again.  You can still use your old backups and import them if desired, but I would just hold onto them for posterity and/or delete them once you are comfortable with any new backups and the amount of history you need to retain before permanently deleting older backups. 

Fixed the issue!! THANK YOU! The problem was that that in the Programs(X86)->Acronis->TrueImage->WinPE there was a WinPE.zip file from the 2016 installation. I deleted that file, re-ran the installation doing a repair and now I have rescue media saying 2017! I'll have to recreate the .wim file for the RAID 1 drivers.

Harris,

Wow, did you upgade a True Image 2016 install to True Image 2017 before creating the WinPE media?  Sounds like you have.  If yes please use the Feedback tool found in the help section of the application to report this problem of having the WinPE.zip file remain after the upgrade.  That file should have been replaced by the 2017 installer during the upgrade install to the correct 2017 version.

Enchantech wrote:

Harris,

Wow, did you upgade a True Image 2016 install to True Image 2017 before creating the WinPE media?  Sounds like you have.  If yes please use the Feedback tool found in the help section of the application to report this problem of having the WinPE.zip file remain after the upgrade.  That file should have been replaced by the 2017 installer during the upgrade install to the correct 2017 version.

Yes,  I did an upgrade from 2016 to 2017 which was offered when I started up the system last week. The correct file was there only when I removed the .zip file from the Acronis directory. The repair process installed the correct version.

Thanks for confirming.

Thanks for pointing me in the right direction. I had the exact same problem, but didn't notice that it said ATI 2016 when the boot media came up.

I deleted the WinPE folder (which contained the WinPE.zip file and an acronis.inf

I reran the ATI installation as a repair and now I'm good to go.

BTW, the newly created WinPE folder does not contain the acronis.inf file.

Thanks so much.

David