Skip to main content

Rescue Media Question

Thread needs solution

Is it best to create a separate rescue media for each of my machines when all of my computers are running the same version of Windows 10?  In the past I simply made a set of rescue disks and used them on any or all of my machine as needed.  Recently, I attempted to use a rescue disk created with True Image 2021 on a computer where the backup was created with True Image 2020 (both .tibx format) and all that I got was a black screen when I attempted to reboot the machine. 

The disk was a brand new SSD disk and I was attempting to restore a backup instead of using Clone disk.  In the end I created a new rescue media and used clone disk utility to migrate the information to the new disk.   

0 Users found this helpful

Virgil, I would expect one set of rescue media to be capable of working with multiple different PC's but with the caveat that they have similar hardware and usage scenarios.

There may be issues where different types of disk and connection methods are involved if additional device drivers are required, i.e. NVMe M.2 SSD using RAID mode, but I would again expect rescue media created on such a system to work on other standard SATA drive PC's.

My own rescue media (created using the MVP Custom PE builder tool) gets used on a mix of my other PC's (and some visiting ones too when needed).  With the MVP tool, I normally elect to include the Intel RST support for NVMe and RAID which works with my PC's whether needed or not.

Steve, Thanks for your prompt reply.  The rescue media was created on a AMD Ryzen 9-3900X desktop machine that has PCI-E 4.0 NVME drives on it.  I downloaded and installed Windows ADK because I am running Windows 10, version 2004.  I downloaded a current copy of ADK because I wanted to create a WinPE rescue media. 

The machine that I attempted to use the rescue media on was a older laptop with an Intel 5 processor and a 2.5 inch SATA 3 SSD drive.  Perhaps the difference in hardware is what caused the problem because when I created the WinRE rescue media on the Laptop it worked and restored the backup just fine.         

Virgil, that is interesting. It may be that no Intel chipset drivers were included because the system was AMD based. I have not tried recovery media created on my ancient Ryzen on my more recent Intel based sustems.

If the laptop has an SSD it may be set up to use Intel RAID drivers - Intel RST support required. You can check the mode in the BIOS/UEFI settings. There is probably an easier way to find that out but cannot think of it at the moment.

Ian

IanL-S wrote:

If the laptop has an SSD it may be set up to use Intel RAID drivers - Intel RST support required. You can check the mode in the BIOS/UEFI settings. There is probably an easier way to find that out but cannot think of it at the moment.

 

Ian,

The driver that was installed for the SATA AHCI controller when I attempted the system restoral was storahci.sys and listed below for your information are the other particulars about the system.  I have since gone to the ASUS site, downloaded and changed the SATA AHCI controller driver to the Intel Mobile Express Chipset SATA AHCI Controller driver IaStor.sys.  The laptop only has a single SATA connection so I would not think that Intel RST support would be required for this machine.  However, I believe that the fact that the rescue media was created on a AMD machine that the Intel chipset drivers, as you suggested, may not have been included.  Especially since I got the same results with a restoral attempt using rescue media from a different backup program which was also created on the AMD system.  Looking back, It makes sense that the Intel Chipset drivers would not have been included since the rescue disk was created on a AMD machine.  Thank you for sharing your thoughts with me on this matter.  Do you think that the MVP recovery disk would have worked if I had elected to use it?

Virgil

 

SYSTEM BIOS:

Intel Core I5-2430M @ 2.40 GHZ

SATA Mode Selection = AHCI

UEFI Boot = Enabled

Boot Option #1 = Windows Boot Manager

Boot Option #2 = P0: SPCC Solid State Disk (Silicon Power ACE A55 512GB SSD)

 

SYSTEM INFORMATION:

Bios Mode = UEFI

Virgil & Ian, thanks for the continued conversation here which is of interest to other users!

I only have Intel PC's so haven't encountered this type of issue with rescue media and very rarely come across any PC's with AMD processors that give me reason to use my Intel based media, so suspect the conclusions being arrived at here are valid.

This perhaps is a case where the Linux based rescue media has some advantages with being a little more agnostic about the processor architecture and type, though it may stumble if RAID is involved..!  Always worth keeping some different 'flavours' of rescue media in the tool kit.