Direkt zum Inhalt

Failure to restore TIBX image to Lenovo W340

Thread solved

Hi all,

 

I've been through a very frustrating Friday in trying to help one of my customers move their system from an old i5 system to a newly-bought Lenovo W340 with Core i7-10700K for better performance. The old setup had an SSD as the OS drive and a rotating HDD which unfortunately was picked as the boot loader location. So this makes things unneccessarily complex already but that's what the Windows installation routine did.

A full system image TIBX exists, created with Cyber Protect (aka True Image 2021). Whatever I did, I could not get the restore media to work properly on the new machine. It is a combination of multiple issues:

  • W340 has an M.2 PCI-express SSD on board which requires specific storage drivers. None are available for Linux or Windows PE.
  • It also has a non-standard NIC, so for network access, another specific driver is required. As the backup images are stored on a NAS, there is no easy way to get access to them other than over the network.

 

So the core question would be: how can I create a bootable rescue media (on USB) that is capable of including the drivers required, and using them to pull data from the network and write to the built-in M.2 SSD?

 

The machine came with Windows 10 preinstalled and I thought it might be a good idea to create the rescue media (along with Universal Restore) right on the new target device. Did so, but unexpectedly, the drivers needed for restore were not included with the USB bootable media as it seems. Eventually after restarting, there was no access to any storage device other than the USB stick itself, and no access to network either.

Running the restore directly on the W340 out of Cyber Protect console under the (new but to be replaced) Windows would reboot the PC, install some kind of Linux-based EFI boot loader so an USB media was not required, it looked very promising as storage and ethernet were both available, took a good amount of time showing frozen progress bars, but resulted in an unbootable system eventually after everything looked as if it might be a success. I think it is because the boot loader and OS were not on the same drive, and I had to select carefully what to restore from where. Multiple times, the dialog would not let me continue after mistakes, even after correcting them, so I had to use "back' and 'forward' to get into the dialog and take all settings again.

As a result, the only platform where it at least appeared to work is now lost and ends up in a blue screen on bootup (INACCESSIBLE_BOOT_DEVICE). I have no idea how to get that back to a working state.

Every rescue media I'm trying to build on the source PC fails. All variants of boot issues were seen: device not offered to boot from at all, device booting into a black screen with no more action, device booting into a blue screen and restarting, (Linux) device showing some sort of kernel panic. It never got into any kind of product splash screen or dialogue. One of my USB flash drives was even rendered unusable along the way.

Drivers are available on the same USB stick the system booted from but for some reason I cannot get any of them to work to make the devices available. The simple PE restore image does not even offer to add drivers, but it would be in vain anyway because Lenovo does not provide PE drivers for the critical components. The drivers I managed to download are for Windows 10 and are probably not usable with rescue media at all but there is no information about this to be found anywhere, and the media builder won't issue any "this is not going to work" message.

So what gives? I have paid for a full-blown backup and restore solution including Universal Restore, and none of it works. The only perceived security is that files can be recovered from the TIB(x) images. However, the thought was to be able to restore images from workstations immediately to any replacement PC available in a disaster situation, and the recovery itself was a total disaster until now. The customer's confidence has suffered considerably.

I cannot find any useful information on how to prepare a full system restore to a platform that needs drivers, which drivers to use, how and when to include them, whatever.

So what would be the strategy here? The new system is totally different from the old one, and as it's a ThinkStation with a very modern set of hardware components, a lot of generic drivers are apparently not compatible. Luckily, the old system is still up and running and continuing to make backups so I can pick up later but next time it better be a success and not another round of embarrassment.

Sorry that some parts of this story are lacking detail but I missed to take notes so this is rather what I remember. The key issue should be clear anyway.

Thanks for any advice!

Cheers,

Joe

 

0 Users found this helpful

Joe, welcome to these public User Forums.

I would recommend trying the new MVP Assistant tool for building your WinPE rescue media on the new Lenovo W340 system, as this has an alternative rescue media builder where you can add in any additional device drivers needed for the SSD and NIC.

The latest version of the new log viewer tool is at the link below. 
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.1.1)

Note: Linux based Acronis rescue media has a number of known limitations and is not recommended for your scenario.

Dear Steve,

 

thank you so much, I'm going to give the MVP Assistant a try, let's hope for the best.

I'm still a bit skeptical about the drivers. As stated, I could not find any drivers expressly for use in the PE, so all I have are the latest Windows x64 drivers that would be installed in the full OS also. As I don't have the target machine here with me, but have to visit the customer to try again, there is little time and room for exercise...

Do you recommend creating the MVP-based rescue media on the target computer in the preinstalled Windows 10, or does it not matter and I can set up the rescue media on the old PC? (including the drivers for the new machine, of course)

 

Cheers,

Joe

Joe, ideally it will always be best to create the media on the system where it will be used but if you have correctly identified the required drivers for that system, then it should be ok to try creating it on a more accessible system.

If you can run the MVP Assistant on the target system, then you can use the Driver analyser feature of the rescue media builder tool, plus select to include Inbox drivers in the analysis. Note: including Inbox drivers will make the analysis a lot slower!

The image above is for Driver Analysis with Inbox drivers selected on my Intel i7 HP system.

Awesome, that looks really promising. I'll keep you updated how it went. Will try on Wednesday next time.

Thanks a ton!

Cheers,

Joe

Oliver,

The machine you select to use and build MVP media on must have the Acronis True Image product or the Acronis Cyber Protect Home Office product (ie. 2017 to present).  The reasons are that first, testing of the MVP builder was tested on systems with the above products.  Second, the builder uses the installed version of the Acronis product from which to extract the application files for the app and then added to a Windows PE/RE image.

That did it! It took a while to get acquainted to the MVP tool but eventually it did the job. Thank you so much for giving me this hint. I don't know what I would have done without it.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 488

Dear Oliver Schmidt,
Great to hear that the issue was solved.