Salta al contenuto principale

True Image file creations switch locations Because 2 drives have same identifier

Thread needs solution

I am running True image 2018 build 15470

I have connected 2 USB SSD drives.  2 of my backups will change target drives from time to time even though these drives are always connected.  I have dropped and recreated them, changed the target drive, and need some guidance on how to solve this.

I did find the following on my Windows 10 pc that is running the jobs;

Disk 2 has the same identifiers as one or more disks... Event 158 on Windows 10 current build

For event 158, Microsoft says that it shouldn’t impact performance but gives this description:

  • If multiple paths to the same physical disk device are available, but Microsoft Multipath I/O (MPIO) is not enabled, the device is exposed to the system by all paths that are available. This causes the same device ID data (such as Device Serial Number, Vendor ID, Product ID, and so on) to be exposed multiple times.
  • If Virtual Hard Disks (VHD) are duplicated by using a copy-and-paste operation to create additional virtual machines (VMs), none of the internal data structures are changed. Therefore, the VMs have the same disk GUIDs and the same ID information (such as Device Serial Number, Vendor ID, Product ID, and so on).

I don’t have VHD.  MPIO seems to refer to servers when I looked up the installation instructions but I don’t have the necessary background to solve this.  Either way, True Image 2014 - 2018 had worked well until recently.  

Am I the only one experiencing this with True Image and how can I fix this.  I have had drives running out of space (target) and can not create scripts with any assurance that the tib files will be where I expect them.

 

1 Users found this helpful

Bob, when you say "Disk 2 has the same identifiers as one or more disks... " which particular identifier are you referring to here?

All disk drives have a unique disk signature which if 2 drives have the same can cause a signature collision, then on each disk there are also volumes & partitions which have identifiers.

Acronis uses the UUID of the disk in older versions of ATI before 2019, and uses the GUID of the partition from 2019 forward as I understand.

If your ATI 2018 Backup tasks are getting confused over your 2 USB drives, then this in turn suggests that this is because information in its internal database files reflects the identifiers used by the drives.

I agree that it seems that some internal function is confusing my two 2 tb drives. It is only True Image that seems to be affected by this issue and I spend most of my day with other non-backup functionality. I will attach a picture of one such backup in order to help answer your question. I was trying to find out how true image identified my drives which ARE uniquely set up as drives F and G.

I appreciate any help on how to diagnose it.

I uploaded 3 images to show you what I am getting.

You asked about the drives and they are both GUID.

I also have another Acronis scheduler error that may

Sorry but can see no uploaded images?

To make one drive different, partition it slightly (use windows or a third party tool like minitool partition wizard). That will update the uuid of that drive. Then update your backup task for that drive in Acronis as the source or destination and any conflicts should go away.

I am attempting to send the same files again.  Perhaps you will see something.

  I will look into partitioning tools

 

Thank you.

 

Allegato Dimensione
504864-169936.png 303.39 KB
504864-169939.png 350.23 KB
504864-169942.png 354.22 KB

First, I apologize for these little snippets as avenues for diagnosing and testing become apparent.   

Using Disk Part and Powershell, I can confirm that none of the 3 drives or any volumes on them are duplicates.

This brings me back to my initial question; how does True Image determine the location for a backup?  Using the windows 10 version and my 2 SSD drives (Both 2TB) should find my location uniquely. 

As I am tinkering, I am going to rename the parent folder on these drives in order to eliminate F:\Backup vs G:\Backup as the culprit although I do not have high hopes for this either.

I am not used to posting unique identifiers on a web site where they may be viewed by others however if needed, I can provide them in a more secure fashion.

I do want to thank you for your time and effort regardless of the outcome

 

To continue and get True Image backup consistently,  I'd like to find out where a Job stores the target drive information; Drive F G or using the Partition IDs as mentioned in another thread by a forum moderator; Ekaterina on Feb 28th at 10:46.  If I can see which id is specified for a particular job, maybe I can see where a change to windows or True Image configuration would enable my job to run correctly.  I must point out that ALL other jobs work as expected.  

I have attached info (Notepad) of the disk management for the Drives in the hopes that it will help. 

I have re-partitioned one of my 2 drives (2 TB Samsung 850 SSD) partitioning it differently.  The same result shows.  

The reason I am looking at Acronis is because one of my backups tends to switch drives from time to time.  It is anything but consistent but it does happen.  I have deleted and re-added the job.  The event 158 described above shows whether I use backups or not.  

However, the output of my backup switches from 1 to the other external USB SSD drives.

Win configuration includes 24gb ram i7 processor, windows 10 Home and true image as well as anything else is current.

Thank you

Allegato Dimensione
507933-170846.txt 2.02 KB
507933-170849.txt 810 byte

Open C:\ProgramData\Acronis\TrueImageHome\Scripts and check each of the script .tib.tis files that you see there by opening these in Notepad.

These files are in XML format and contain volume identifiers for the different backup tasks shown in the ATI GUI where the task name is shown near the top of the file data.

Please make copies of the files before making any changes.

I sent this yesterday but when I didn't see it, I decided to repost. 

Thank you for your response.  I did check the offending script and see F5BC3611-1FED-4BBD-BEE0-EB510F0875A7 which doesn't match anything in the disk management system. If you have a way to map this code to what on my system represents my "F" drive, I don't know how to proceed.

 

Thank you again for your help.

Allegato Dimensione
508113-170897.txt 2.02 KB

I did check the offending script and see F5BC3611-1FED-4BBD-BEE0-EB510F0875A7 which doesn't match anything in the disk management system.

That looks to be the Script identifier not the volume identifier that should be shown in the body of the .tib.tis file contents.

You should be seeing contents similar to below:

<volumes_locations>
                        <volume_location partition_id="\local\hd_ev\vol_guid(3B7AFA8001D542F20DB5654000EAA179)" uri="E:\AcronisBackup\(1)Win 10 SSD E 2020.tibx" volume_id="3870574414" />
                        <volume_location partition_id="\local\hd_ev\vol_guid(3B7AFA8001D542F20DB5654000EAA179)" uri="E:\AcronisBackup\(1)Win 10 SSD E 2020.tibx" volume_id="3870574414" />
                        <volume_location partition_id="\local\hd_ev\vol_guid(3B7AFA8001D542F20DB5654000EAA179)" uri="E:\AcronisBackup\(1)Win 10 SSD E 2020.tibx" volume_id="3870574414" />
                    </volumes_locations>

<disk_source has_asz_backup="true" sector_by_sector_backup="false" sector_by_sector_backup_unallocated="false">
                    <holder strid="\local\hd_gpt(D928FEE5486CA9D128B9539BA7C9E78F)" />
                </disk_source> 

Thank you. I’ll check it as soon as possible. Thanks

I think I have a working solution now.  This started with backups that changed from my F to G drive both SSD Samsung 850s with the same usb enclosure.   I kept getting an event Id warning;  Disk 2 has the same identifiers as one or more disks... Event 158 on Windows 10 current build with all the latest updates.  My brilliant brother mentioned that the controller chips on SSD external enclosures can vary greatly in consistency as well as speed.  Well, I tried pulling 1 of them and putting it into a docking station and low and behold; No more error.

Mind you, Every one of my existing backups had to have the Target location respecified.  Some of these jobs didn’t even use that drive in the docking station.  And at NO POINT, did anything other than Acronis have difficulty with data going somewhere other than where I specified.

 However, no errors and so far, all looks good. 

I want to thank all who gave suggestions on how to battle this beast.