Clone screws op my USB-harddisk
I wanted to clone my non-system USB-HD (F:) to another HD (G:). I chose the option for not cloning a system disc.
After the process was completed my G: drive is not readable. The file browser does no even see it, so my 1TB disk is effectively lost. Hoe do I get it back and what went wrong?


- Log in to post comments

Yes, clone from within wiindows.
See log below
Source (F) is still fully fnctional
F: is an USB2 HD with one connection to USB port. Clone is 1GB USB3 connected, also 1 cable, to USB3 port. I have now seen that the clone shows in systemtray (not in explorer) without drive letter.
Disk management shows (see attached):
Disk 0, my SSD C: drive
Disk 1, my clone wihout drive letter. It shows 100MB, OK (EFI-systempartiton), 931,29GB primary partition). What is this EFI? My C and E don’t have this.
Disk 2, My USB3 HD (E:) which I use as my datadrive.
My original to-be-cloned drive is intentionally not connected.
log uuid=9D30A85F-3D56-4B26-8899-B1824893D5FA; product=True Image; version=18.0; build=6613; task=8B75FA98-D848-4FB7-ACC5-0BA8AAA5FFB7; task_name=Entire PC (HAROLDTC)
Start= 27-1-2017 11:27:20
id=1; level=2; module=100; code=0; date/time=27-1-2017 11:27:20
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2; level=2; module=100; code=2; date/time=27-1-2017 11:27:20
message=Operation Entire PC (HAROLDTC) started by schedule.
id=3; level=2; module=100; code=0; date/time=27-1-2017 11:27:20
message=Operation description: Stage Description.
id=4; level=1; module=8; code=0; date/time=27-1-2017 11:27:20
message=AcronisLRPCConnect::BEGIN id=2.328
id=5; level=1; module=8; code=0; date/time=27-1-2017 11:27:20
message=AcronisLRPCConnect::BEGIN id=2.152
id=6; level=1; module=16; code=0; date/time=27-1-2017 11:27:20
message=Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
id=7; level=1; module=16; code=0; date/time=27-1-2017 11:27:20
message=Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
id=8; level=1; module=16; code=0; date/time=27-1-2017 11:27:20
message=Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0
id=9; level=1; module=16; code=0; date/time=27-1-2017 11:27:20
message=Fdisk2: Use Disk 3 host= 0 bus = 0 target = 0
id=10; level=1; module=16; code=0; date/time=27-1-2017 11:27:20
message=Refreshing Drivers...
id=11; level=1; module=30; code=0; date/time=27-1-2017 11:27:20
message=Enter to process disks in Mbr Driver (id = 11)
id=12; level=1; module=30; code=0; date/time=27-1-2017 11:27:20
message=Exit from process disks in Mbr Driver (id = 11)
id=13; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=Enter to process disks in Gpt Driver (id = 12)
id=14; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=Try to load Alternate Header from 1953525167
id=15; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=Gpt Disk ED961CC1-DE31-4CEF-AAD2-A2B4037338EE LBA=1953525167 ALBA=1
id=16; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=try to loading Header from 1
id=17; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=Gpt Disk ED961CC1-DE31-4CEF-AAD2-A2B4037338EE LBA=1 ALBA=1953525167
id=18; level=1; module=32; code=0; date/time=27-1-2017 11:27:20
message=Exit from process disks in Gpt Driver (id = 12)
id=19; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=LDM: New ProcessDisks(rawLayer, headLayer)
id=20; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=ProcessDisks: One more disk to check
id=21; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=ProcessDisks: One more disk to check
id=22; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=ProcessDisks: One more disk to check
id=23; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=Mark All groups as Root Like Dgs
id=24; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=------ Volumes Objects ------
id=25; level=1; module=12; code=0; date/time=27-1-2017 11:27:20
message=LDM initialization complete
id=26; level=1; module=1; code=503; date/time=27-1-2017 11:27:20
message=Analyzing partition '0-0'...
id=27; level=1; module=1; code=503; date/time=27-1-2017 11:27:21
message=Analyzing partition '1-1'...
id=28; level=1; module=1; code=503; date/time=27-1-2017 11:27:21
message=Analyzing partition 'C:'...
id=29; level=1; module=1; code=503; date/time=27-1-2017 11:27:21
message=Analyzing partition '1-3'...
id=30; level=1; module=1; code=503; date/time=27-1-2017 11:27:21
message=Analyzing partition '0-0'...
id=31; level=1; module=1; code=503; date/time=27-1-2017 11:27:22
message=Analyzing partition '2-2'...
id=32; level=1; module=1; code=503; date/time=27-1-2017 11:27:22
message=Analyzing partition '2-3'...
id=33; level=1; module=1; code=503; date/time=27-1-2017 11:27:22
message=Analyzing partition '0-0'...
id=34; level=1; module=1; code=503; date/time=27-1-2017 11:27:22
message=Analyzing partition 'E:'...
id=35; level=2; module=100; code=0; date/time=27-1-2017 11:27:22
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=36; level=2; module=316; code=0; date/time=27-1-2017 11:27:22
message=Operation: backup
id=37; level=2; module=100; code=11; date/time=27-1-2017 11:27:22
message=Priority changed to Low.
id=38; level=4; module=11; code=1004; date/time=27-1-2017 11:27:22
message=Cannot find the partition selected for the backup.; line_tag=0x839CDD79F76936BC
Error_Code=AewDCwC8Nmn3ed2cg0Nhbm5vdCBmaW5kIHRoZSBwYXJ0aXRpb24gc2VsZWN0ZWQgZm9yIHRoZSBiYWNrdXAuACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAA==
id=39; level=1; module=8; code=0; date/time=27-1-2017 11:27:22
message=ServerLRPC::_CloseConnection id=2.152
id=40; level=1; module=8; code=0; date/time=27-1-2017 11:27:22
message=ServerLRPC::_CloseConnection id=2.328
id=41; level=1; module=8; code=0; date/time=27-1-2017 11:27:22
message=ServerLRPC::_CloseConnection id=2.152
id=42; level=1; module=8; code=0; date/time=27-1-2017 11:27:22
message=ServerLRPC::_CloseConnection id=2.328
id=43; level=4; module=316; code=5; date/time=27-1-2017 11:27:22
message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE18
Error_Code=AQUAPAEYzosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAA=
Start= 27-1-2017 11:27:20
Finish= 27-1-2017 11:27:22
Total Time= 00:00:02
Attachment | Size |
---|---|
403740-136228.jpg | 112.41 KB |
- Log in to post comments

Thank you for the further information.
The fact that the cloned drive now shows an EFI partition suggests that the clone operation tried to make the clone drive into a bootable drive. EFI is a bootloader used on many modern systems.
I would suggest approaching this situation in a different way, not using cloning at all.
- Make a full disk & partitions backup of your source USB drive F: - this should be written to where you have sufficient free space to hold the backup image. The size of the backup will depend on how well the contents of the drive can be compressed.
- Disconnect the source USB drive and connect the target USB drive G: - then first delete all the current partitions on this drive via Disk Manager (or a Partition Manager tool).
- Restore the backup of your source drive to the cleared target drive.
- When completed successfully, check that the drive is allocated a valid drive letter and that the contents can be viewed in Explorer.
- Log in to post comments

However.. I cannot do anything with my G:? drive, since it has no drive letter. How di I get my drive back en rid the EFI patittion?
PS: the cloning is nw done with another ID which I Had. I used goodsync. But I want my iTB drive back!
- Log in to post comments

If you don't care about any of the current contents of yuor 1TB G: drive, then you can delete the contents of that drive from within Disk Management - just right-click on the EFI partition on the drive and then select Delete Volume, then do the same for the second cloned partition. Once the drive is clear, you can do the same but select Create Volume instead to add back in a single partition - format as NTFS and allow a drive letter to be allocated to the same.
- Log in to post comments