Skip to main content

Segmentation Fault using Linux based Universal Restore (Windows 10)

Thread needs solution

Hello,

I'm having trouble restoring a full system backup to new hardware. I've tried using the linux-based Universal Restore media mounted on a flash drive. After I'm presented to launch True Image, the application throws a segmentation fault while enumerating local drives. I've tried disabling secure boot as advised by another post with no luck.

I saw another post advising to try the Windows PE method with the Windows 10 PE kit. It launches straight into the Universal Restore dialog where it shows no OS found (as expected).  From what I understand, the restore process is to first restore the backups to the local drive(s) and then use the Universal Restore dialog to adjust the Windows partition(s) with new drivers and such to make it bootable. How can I access the image restore functionality using Windows PE?

Hardware:

Destination drives: 2 NVME M.2

Source of backups: USB3 external harddrive

Imaged flash drive of Universal Restore media: USB3 64GB

Thank you

0 Users found this helpful

Jeffrey, welcome to these public User Forums.

My first comment is that you should not be using the AUR media to restore your backup image, this should be done with the normal Acronis rescue media, and given you have NVMe drives, then you should be creating the 'Simple' Windows PE version of the rescue media that uses files and device drivers from the Windows Recovery Environment.

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 69472: Acronis Cyber Protect Home Office: how to create bootable media

KB 69427: Acronis Cyber Protect Home Office: How to restore your computer with WinPE-based or WinRE-based media

Next, there are known issues with using any USB flash drive media larger than 32GB due to Microsoft limitations.

See KB 58108: Acronis products: using USB sticks with more than 32GB capacity - which explains.

There are also known limitations with using Linux based rescue media!

KB 58006: Acronis software: NVMe drives in RAID mode are not detected by Linux-based bootable media and Acronis startup recovery manager

KB 46250: Acronis Linux-based Bootable Media: Troubleshooting USB HID Devices Detection Issues

KB 45330: Acronis Bootable Media Does Not Detect HDD, RAID or NIC

KB 45331: Acronis Bootable Media(Linux-based): Troubleshooting NIC Detection

KB 59947: Acronis True Image Linux-based bootable media boots into black screen after selecting any option in the option menu

The only known issues for segmentation faults date back over 5 years and were fixed in the latest build version of ATI 2017 for Linux media as far as I can find.

Thank you for the quick response.

I was able to restore the backups to both of my NVME SSD's. While restoring, I selected "Recover Disk Signature" for both drives. Previously, in the BIOS both drives were correctly recognized as a Firecuda NVME drive - now only 1 drive is recognized as a Firecuda device and the other has a generic name of "NVME SSD". Could this be related to restoring with the "Recover Disk Signature" option?

I am able to boot into Windows but the generic "NVME SSD" device is not displayed in disk management. I booted into Seagate's SeaTools and it does not recognize it as a Firecuda device. I have confirmed I am able to read/write to the drive using their tool.

Is there a known fix for this situation?

Thank you

Jeffrey, if the backup images were from the same NVMe SSD's then the disk signatures should be identical to how they were when the backup was created, so if the drives displayed correctly then, it should do so after restoring the backup and signature.

I would more suspect that the drive showing as a generic NVMe SSD has the wrong driver installed so would suggest looking more closely in the Device Manager to see what the correct SSD driver is showing, then change the driver on the incorrect SSD to that same driver if they are both the same type of drive.