Corrupted Bitlocker D partitions on W11 Clones/images but not W10 maybe?

Steven, There's confusion. I noted two issues one with Cloning and the other with images the IO error, you assumed the images one covered both and I assumed they may be related since cloning backups failed and an image restore failed at the same time.

Issue 1 is with cloning PC to PC using two USBs: There are no errors what so ever everything seems good until you boot into the clone and 'D' partition is locked because its been corrupted somehow. 5 attempts to two diffrent PCs 5 corrupted 'D' partitions.

Issue 2 is the IO errror for the internal Image restore. I'll leave that out for the moment.

It's issue one thats more concerning see image 'Clone corruption.jpg' for locked 'D'partition.

**Steven, there is no compression selection. To reiterate: **

PC to PC clone using two USBs, one on the Source and the other on the Target.

Notes:
1- The three HDDs I've been using have had multiple clones of this Source PC during these tests. I have deleted the partitions and formatted with gparted but that takes a few seconds which I would say it just deletes the MBR and makes new NTFS one. I then check with Clonezilla: sudo fdisk -l /dev/sda and I can still see all the Windows partitions. I mention this incase it has any bearing.
Source HDD is a 500GB SSD > Target HDDS are 3.5 inch 2 x 500GB and 1000GB.
2- If I do a local PC to USB HDD Clone that uses one USB, all is good. Just thought I would mention this for it's not something with Windows or the PC.
3- PC one > Router > Switch > PC2
4- Windows 11 Modified for older PC, Bitlocker 'C' and 'D' encrypted partitions.
5- Downloaded and used the version: clonezilla-live-3.1.2-17-amd64.iso as suggested.
6- Partition 'D' is the one that always fails.

Conclusion:
Failure on two attempts and noted that CZ does not actually clone partition 'D'. See video.

In the video provided around the 10 second mark partition 'C' 215GB finishes after '30 min' it then goes onto partition 'D' 279GB which takes 00:02 seconds. 00:02 seconds to clone 279GB's I can only dream.

Steven, that's a solid hard NO.
I have already spent countless hours on this.
Creating the VM Windows then expansion packs then figuring out how to use the two CZ USBs in the VM yet alone how to create the clone. No, nope, no way not interested. You are welcome to do it if you like.
Specs:
Source: Lenovo Thinkstation 4157 12GB RAM 6 Core CPU 5680 3.33GHz W11 on 500GB SSD 2 Bitlocker partitions 'C' 215GB and 'D' 279GB. There are other drives but this is the one I clone.
Target: Any PC laying around and any HDD laying around.

I get 100% failure on every attempt so yeah, not wasting more time going onto VMs.

Possible clue for you:

The source PC will stop at 'Waiting for Target to connect' Something like that, and it never goes beyond that even when the Target is cloning. It remains until the target tells it that it has finished....I would say that the two CZ USBs are not correctly communicating or possibly the second USB is not reading the 'D' partition size correctly.

Remember, if I create a clone just using a USB HDD on a hub connected to the source PC using one CZ USB all is good. So it's something to do with the two CZ USB's.

In the video is what I have done over 10 times except in this case after it starts I stop it for it's only for you to see settings. It could not be simpler.

Interesting result on cancelling cloning:

This video stops at the beginning of 'C' cloning. I was not going to continue just to have it fail but something interesting happened when I pressed 'CTRL + C' on the target PC (Left Monitor). Again this is not on the video.

Pressed > CTRL + C > which stopped 'C' cloning, it then proceeded to start cloning 'D' It actually started to clone 'D' giving a duration of 30 odd minutes @ 7.00GB/m. It did not just quit as normal at 00.02 seconds. So it is capable of cloning 'D' but not if 'C' is cloned completely first?

No, I did not continue to clone 'D' to see what happens since I already killed 'C' and have other things to do.

It's late and I'm tired so I shouldn't be answering but I'll try.

'Here I tried to reproduce the issue here. Similar to yours, I configured a MS Windows and a partition having bitlocker encrypted.'
Did you create one or two Bitlocker partitions. I use two 'C' and 'D' are individually bitlocker encrypted.

' everything runs smoothly.'
That is irrelevant. Mine also shows everything is good and it's not until you boot the clone and look at 'D' drive to find it did not actually clone. See the image attached.

Everythign runs smoothly is part of the problem. As above, if you didn't catch it not cloning 'D' you won't know until you run the Clone and look at 'D' drive in Windows Explorer.

Clonezilla live 3.1.2-20 amd64 - I'll give it a go.

**UPDATE: **

**Clonezilla live 3.1.2-20 amd64 - Failed to clone 'D' as all the above. Starts but then it says done withing 2 seconds. **

Still at a 100% failure rate. Did you actually create two Bitlocker partitions, 'C' and 'D'

My previous test only contains 1 bitlocker partition. I do not think there is any possibility that 1 or 2 will make difference since Clonezilla treats each one separately.

Well thanks for that, I just wasted half an hour comparing your info to mine to see if you had actually done two Bitlocker partitions for I was suspicious when I couldn't find them.

Sorry, but I can't take your result as factual since it's in a VM and not realworld PC to PC, in other words how do you know it's not seeing/treating the clone as it was a single PC with identical specs. From my limited experience with VM's they are not the same as a real PC. Can you clone the VM HDD onto a real networked PC.

When you say it's two partitions are treated seperately, they are not or I would not have a bug. **As I stated in a previous post if I kill the cloning of 'C' then 'D' will actually clone. So something is wrong in how CZ is handling the transfer between finishing 'C' fully and starting 'D'.
**
The other thing noted is that your src.txt files say 'done' after connect is that after it's finished cloning or during cloning for mine never says that it connects.

I don't know what to tell you except that it's a 100% failure rate with Bitlocker 'D' partition using two USB PC to PC cloning, I've shown you the video.

No hard feelings, I'm done with it anyway as well since you even tried to replicate with only one Bitlocker partition when all this is about two.

The irony is I don't actually need it for I can USB Hub Clone. I tried it out to see what this method did and thought it would be good to create hot swaps for backups since it can process at 7GB/m which is faster than USB Hub and imagin as clones are ready to go. Unfortuneately it can't handle multiple Bitlocker partiitons, could even be the size of the partitions for all I know, in any case, it can only handle one Bitlocker but not more so it's of no use.

I thought I would try and help by reporting it when I get 100% failure but if you can't replicate you can't replicate it.

It was worth a shot at fixing it.

Steven I came accross this bug from 2022 and it seems to be similar to what I experienced, which is an NTFS partion of 40GB taking a few seconds:

Rescuezilla bug advisory #328 https://github.com/rescuezilla/rescuezilla/releases/tag/2.4.2 for an NTFS partion of 40GB taking a few seconds, More info found at: https://github.com/rescuezilla/rescuezilla/issues/328 and https://sourceforge.net/p/rescuezilla/discussion/support/thread/2d3985ba7c/?limit=250#31bb

I cam accross it by accident and thought it may help since you couldn't replicate.