Aller au contenu principal

Another Computer Crashed and I need a VM

I have a backup of my system using 2018.  The computer crashed (CPU went bad), so I took the backup and put it on another system so I could use it in a VM.  Then I added the external backup.  When I try to convert to VHD, nothing happens.  For the fun of it, I click on recover and it says it can't find version 1, but it is version 1.  I tried to "validate" but it says the same thing.  I cant reconfigure because its a different computer so what cam I do?  Thanks.

0 Users found this helpful

Brad, more information is needed for this issue?

What type of backup do you have, how is this named (file names)?
What version of ATI are you using to validate the backup file(s)?
Do or have you had any backup tasks using the same name on the computer where you are trying to validate the backup?

The filename is Hitachi HTS545025B9A300 PB2O_full_b1_s1_v1.tib.

I am using the same version I backed it up with - ATI2018

I have not had any tasks with that name on the computer I am trying to validate with

Thanks!

 

 

Brad, thanks for the further information.

A couple of thoughts:  try renaming your backup file to abcdef_full _b1_s1_v1.tib then retry the validation of the file.

If you are still asked for version 1, then I would suggest trying an offline validation by booting from the Acronis Rescue media to do this.  To get to the validation option, first select as if doing a Recovey, then right-click on the selected .tib file where the validation option should be given.

Ok, I got it to validate when booting from the rescue media, but how to I create the VM? 

Brad, the successful validation indicates that there is nothing wrong with the backup. However, validation using the recovery media will not (as I understand) it update the Acronis data base that is used when running Acronis from Windows. So, I would try renaming the backup; or copying the latest back set to a new location, and renaming the files, then either do validation from Explorer or add backup from within Acronis, followed by validation. 

How do you do validation from explorer? Also I did try renaming file but I cant validate using the program.

Brad, open explorer, navigate the directory where the backup is stored, select the most recent backup file, right click and there should be an entry for Acronis True image, select it and you are given a choice to either mount or validate the backup.

If you do not see the item, the it may be that there is a problem with the Acronis installation. Download the full installer from you Acronis Account, run as Administrator and when prompted select repair rather than uninstall.

Ian

OK, so I finally got it to validate.  So I tried to convert it to a VHD.  It started the conversion and got to about 50% and then suddenly said it was complete.  But I cannot get it to boot.  I tried the universal restore and it says there is no operating system.  What steps to I try next? Thanks.

Ok so I ran the BCD thing and created the VM again, but it still doesn't boot.  It wants to repair but says it cannot repair (same as before running BCD). I try typing the drive letters and there is nothing there.  Because it gets to 50% during the conversion and then suddenly says its done, how do I know it converted properly?  

Because it gets to 50% during the conversion and then suddenly says its done, how do I know it converted properly?  

Brad, please download the MVP Log Viewer tool using the link in my signature below.  This will show you the log file for your conversion of the tib file to VHDX and thus will show if any errors were issued during the process.  

See the screen image below from an attempt I made to convert a tib to VHDX which failed due to insufficient disk space!

As I suspected there were errors, but I don't know what to make of them or what I should do next.

1/13/2019 2:43:48 PM: Scheduler event handler is created
1/13/2019 2:43:49 PM: Operation started manually.
1/13/2019 2:43:49 PM: AcronisLRPCConnect::BEGIN
1/13/2019 2:43:49 PM: AcronisLRPCConnect::BEGIN
1/13/2019 2:43:49 PM: AcronisLRPCConnect::BEGIN
1/13/2019 2:43:49 PM: Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
1/13/2019 2:43:49 PM: Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
1/13/2019 2:43:49 PM: Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0
1/13/2019 2:43:49 PM: Fdisk2: Use Disk 3 host= 0 bus = 0 target = 0
1/13/2019 2:43:49 PM: Fdisk2: Use Disk 4 host= 0 bus = 0 target = 0
1/13/2019 2:43:49 PM: Refreshing Drivers...
1/13/2019 2:43:49 PM: Enter to process disks in Mbr Driver (id = 13)
1/13/2019 2:43:49 PM: Exit from process disks in Mbr Driver (id = 13)
1/13/2019 2:43:49 PM: Enter to process disks in Gpt Driver (id = 14)
1/13/2019 2:43:49 PM: Try to load Alternate Header from 1953525167
1/13/2019 2:43:49 PM: Gpt Disk 0C900C28-A6FD-4FA8-B566-60262A249BC6 LBA=1953525167 ALBA=1
1/13/2019 2:43:49 PM: try to loading Header from 1
1/13/2019 2:43:49 PM: Gpt Disk 0C900C28-A6FD-4FA8-B566-60262A249BC6 LBA=1 ALBA=1953525167
1/13/2019 2:43:49 PM: Try to load Alternate Header from 537234767
1/13/2019 2:43:49 PM: Gpt Disk 82D3A0B6-CA56-4CA0-B614-A7A9E5DB12F4 LBA=537234767 ALBA=1
1/13/2019 2:43:49 PM: try to loading Header from 1
1/13/2019 2:43:49 PM: Gpt Disk 82D3A0B6-CA56-4CA0-B614-A7A9E5DB12F4 LBA=1 ALBA=537234767
1/13/2019 2:43:49 PM: Exit from process disks in Gpt Driver (id = 14)
1/13/2019 2:43:49 PM: LDM: New ProcessDisks(rawLayer, headLayer)
1/13/2019 2:43:49 PM: ProcessDisks: One more disk to check
1/13/2019 2:43:49 PM: ProcessDisks: One more disk to check
1/13/2019 2:43:49 PM: ProcessDisks: One more disk to check
1/13/2019 2:43:49 PM: ProcessDisks: One more disk to check
1/13/2019 2:43:49 PM: Mark All groups as Root Like Dgs
1/13/2019 2:43:49 PM: ------ Volumes Objects ------
1/13/2019 2:43:49 PM: LDM initialization complete
1/13/2019 2:43:49 PM: Analyzing partition '0-0'...
1/13/2019 2:43:49 PM: AcronisLRPCConnect::BEGIN
1/13/2019 2:43:49 PM: Analyzing partition '1-2'...
1/13/2019 2:43:49 PM: Analyzing partition 'E:'...
1/13/2019 2:43:49 PM: Analyzing partition '1-4'...
1/13/2019 2:43:49 PM: Analyzing partition '0-0'...
1/13/2019 2:43:50 PM: Analyzing partition '2-2'...
1/13/2019 2:43:50 PM: Analyzing partition 'C:'...
1/13/2019 2:43:50 PM: Analyzing partition '2-4'...
1/13/2019 2:43:50 PM: Analyzing partition '0-0'...
1/13/2019 2:43:50 PM: Analyzing partition 'F:'...
1/13/2019 2:43:50 PM: Analyzing partition '0-0'...
1/13/2019 2:43:51 PM: Analyzing partition 'G:'...
1/13/2019 2:43:51 PM: Operation: Conversion
1/13/2019 2:43:51 PM: Priority changed to Low.
1/13/2019 2:43:51 PM: Error 0x0
1/13/2019 2:43:51 PM: Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
1/13/2019 2:43:51 PM: Fdisk2: Use Disk 7 host= 0 bus = 0 target = 0
1/13/2019 2:43:51 PM: Refreshing Drivers...
1/13/2019 2:43:51 PM: Enter to process disks in Mbr Driver (id = 53)
1/13/2019 2:43:51 PM: Exit from process disks in Mbr Driver (id = 53)
1/13/2019 2:43:51 PM: Enter to process disks in Gpt Driver (id = 54)
1/13/2019 2:43:51 PM: Exit from process disks in Gpt Driver (id = 54)
1/13/2019 2:43:51 PM: LDM: New ProcessDisks(rawLayer, headLayer)
1/13/2019 2:43:51 PM: ProcessDisks: One more disk to check
1/13/2019 2:43:51 PM: Mark All groups as Root Like Dgs
1/13/2019 2:43:51 PM: ------ Volumes Objects ------
1/13/2019 2:43:51 PM: LDM initialization complete
1/13/2019 2:43:51 PM: Error 0x100480: Staring RefreshVolumesHooked.
1/13/2019 2:43:51 PM: Error 0x100480: Staring RefreshVolumesHooked.
1/13/2019 2:43:51 PM: Error 0x3901f4: SingleOsLetterSetterImpl::Init
1/13/2019 2:43:51 PM: Error 0x3901f4: FindSingleOsOnComputer
1/13/2019 2:43:51 PM: Operating systems detect Computer - emulated begin
1/13/2019 2:43:51 PM: Detect OSes in Bios Disk BIOS num - 0 NtSignature - 0 begin
1/13/2019 2:43:51 PM: Detect OSes in Bios Disk BIOS num - 0 NtSignature - 0 end
1/13/2019 2:43:51 PM: Detect partitions Disk BIOS num - 0 NtSignature - 0 begin
1/13/2019 2:43:51 PM: Detect partitions Disk BIOS num - 0 NtSignature - 0 end
1/13/2019 2:43:51 PM: Operating systems detect Computer - emulated end
1/13/2019 2:43:51 PM: Error 0x390008
1/13/2019 2:43:51 PM: Error 0x100480: Unable to find os or more than one os is found.
1/13/2019 2:43:51 PM: Convert Acronis Backup to Windows Backup From file: E:\abcdef_full _b1_s1_v1.tib.tib To file: F:\gays virtual\gays.vhdx
1/13/2019 2:43:51 PM: Pending operation 52 started: 'Clearing disk'.
1/13/2019 2:43:51 PM: Pending operation 14 started: 'Copying partition'.
1/13/2019 2:43:59 PM: Pending operation 14 started: 'Copying partition'.
1/13/2019 3:44:17 PM: Error 0x101f6: A format/resize error.
1/13/2019 3:44:17 PM: Pending operation 14 started: 'Copying partition'.
1/13/2019 3:47:01 PM: Pending operation 61 started: 'Copying MBR'.
1/13/2019 3:47:01 PM: Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
1/13/2019 3:47:01 PM: Fdisk2: Use Disk 7 host= 0 bus = 0 target = 0
1/13/2019 3:47:01 PM: Refreshing Drivers...
1/13/2019 3:47:01 PM: Enter to process disks in Mbr Driver (id = 61)
1/13/2019 3:47:01 PM: Exit from process disks in Mbr Driver (id = 61)
1/13/2019 3:47:01 PM: Enter to process disks in Gpt Driver (id = 62)
1/13/2019 3:47:01 PM: Exit from process disks in Gpt Driver (id = 62)
1/13/2019 3:47:01 PM: LDM: New ProcessDisks(rawLayer, headLayer)
1/13/2019 3:47:01 PM: ProcessDisks: One more disk to check
1/13/2019 3:47:01 PM: Mark All groups as Root Like Dgs
1/13/2019 3:47:01 PM: ------ Volumes Objects ------
1/13/2019 3:47:01 PM: LDM initialization complete
1/13/2019 3:47:01 PM: Analyzing partition '1-2'...
1/13/2019 3:47:02 PM: Open BCD parser using raw registry parser
1/13/2019 3:47:02 PM: Open BCD parser using raw registry parser
1/13/2019 3:47:02 PM: Mapping from Disk NtSignature - 614115951 to Disk BIOS num - 0 NtSignature - 2383575895
1/13/2019 3:47:02 PM: Bootability restore operation has started.
1/13/2019 3:47:02 PM: Added dispatched dependent disk '\comp_emu(microsoft_computer_1)\hd_emu(353)'
1/13/2019 3:47:02 PM: Added dispatched partition '\comp_emu(microsoft_computer_1)\hd_emu(353)\part_sn(A8E881BF5EA8E8AA)start(2048)'
1/13/2019 3:47:02 PM: Added dispatched partition '\comp_emu(microsoft_computer_1)\hd_emu(353)\part_sn(183482DC681834B4)start(3074048)'
1/13/2019 3:47:02 PM: Error 0x1d01f4: Disk '\comp_emu(microsoft_computer_1)\hd_emu(353)' has invalid BIOS number (0). The following value will be used: '128'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda1'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda2'.
1/13/2019 3:47:02 PM: Partition Mapping: no Linux Root in set
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda1'.
1/13/2019 3:47:02 PM: Added BR mapping by dev ( (hd0,0) /dev/\Device\HarddiskVolume33 ) => ( (hd0,0) /dev/sda1 UUID=BF81E8A8AAE8A85E )
1/13/2019 3:47:02 PM: Added BR mapping by label ( (hd0,0) System
1/13/2019 3:47:02 PM: Added BR mapping by UUID ( (hd0,0) /dev/\Device\HarddiskVolume33 ) => ( (hd0,0) BF81E8A8AAE8A85E )
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda2'.
1/13/2019 3:47:02 PM: Added BR mapping by dev ( (hd0,2) /dev/\Device\HarddiskVolume35 ) => ( (hd0,1) /dev/sda2 UUID=DC823418B4341868 )
1/13/2019 3:47:02 PM: Added BR mapping by label ( (hd0,2) HDDRECOVERY
1/13/2019 3:47:02 PM: Added BR mapping by UUID ( (hd0,2) /dev/\Device\HarddiskVolume35 ) => ( (hd0,1) DC823418B4341868 )
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda1'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda2'.
1/13/2019 3:47:02 PM: Error 0x0
1/13/2019 3:47:02 PM: Error 0x0
1/13/2019 3:47:02 PM: Error 0x0
1/13/2019 3:47:02 PM: Bootability restore operation has finished.
1/13/2019 3:47:02 PM: Operating systems detect Computer - emulated begin
1/13/2019 3:47:02 PM: Detect OSes in Bios Disk BIOS num - 0 NtSignature - 2383575895 begin
1/13/2019 3:47:02 PM: Detect OSes in Bios Disk BIOS num - 0 NtSignature - 2383575895 end
1/13/2019 3:47:02 PM: Detect partitions Disk BIOS num - 0 NtSignature - 2383575895 begin
1/13/2019 3:47:02 PM: Detect partition Partition num - 1 begin
1/13/2019 3:47:02 PM: Open BCD parser using raw registry parser
1/13/2019 3:47:02 PM: System partition not defined!
1/13/2019 3:47:02 PM: Detect partition Partition num - 1 end
1/13/2019 3:47:02 PM: Detect partition Partition num - 2 begin
1/13/2019 3:47:02 PM: Open BCD parser using raw registry parser
1/13/2019 3:47:02 PM: Detect partition Partition num - 2 end
1/13/2019 3:47:02 PM: Detect partitions Disk BIOS num - 0 NtSignature - 2383575895 end
1/13/2019 3:47:02 PM: Operating systems detect Computer - emulated end
1/13/2019 3:47:02 PM: Error 0x108: Invalid activity info
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=1
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=3
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=2
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=1
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=3
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=4
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=2
1/13/2019 3:47:02 PM: ServerLRPC::_CloseConnection id=4
1/13/2019 3:47:02 PM: Error 0x13c0005: Operation has completed with errors.
1/13/2019 3:47:02 PM: WaitChangesEx returned not null
1/13/2019 3:47:02 PM: Scheduler event handler is completed
1/13/2019 3:47:02 PM: Scheduler event handler successfully destroyed
 

 

Brad, I am not an expert on using this Convert to VHD feature but there is one error that stands out near the start of the process in the log:

1/13/2019 3:44:17 PM: Error 0x101f6: A format/resize error.

This occurs because the disk where the F:\gays virtual\gays.vhdx file is being created is not large enough to expand all the stored partitions in the .tib file to the size they held on your old computer.

What OS was running on your old computer where the .tib file was created from?  I did not expect to see the lines that reference Linux drive / partition mapping in the log?

1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda1'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda'.
1/13/2019 3:47:02 PM: The Linux device name may be 'sda2'.

Was this a single OS computer or was it dual-boot?

You may need to either open a Support Ticket with Acronis to continue this investigation, or else consider a different approach such as trying to restore the .tib to a Virtual Machine application such as VMware or Oracle VirtualBox by booting the VM from the Acronis rescue media and restoring to a virtual disk.

See forum topic: How to convert .tib to VM? - which may provide more insight.

The old computer was not dual boot and was Windows 10. I'll try and do a restore to a VM or since 2018 has no support I'll upgrade to 2019 and open a ticket.  Thanks!