Recent changes to 416: Corrupted Bitlocker D partitions on W11 Clones/images but not W10 maybe?

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

2024-05-05T06:11:11.425000Z

Thanks. As I mentioned, if the issue is not reproducible here, we can not do anything to fix that.
If you can reproduce this issue in a VM, maybe you can share us the virtual disk so that we can try to reproduce this issue, and fix it.

Steven

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

2024-04-21T13:35:12.825000Z

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.

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

2024-03-23T10:57:03.228000Z

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.

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

2024-03-23T09:34:42.496000Z

status: open --> open-works-for-me
assigned_to: Steven Shiau

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

2024-03-23T09:33:31.850000Z

"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. " -> Well, I do not have any spare physical machine here. However, even it's a VM, just like any physical PC, it's a PC. Just the hardware is physical or virtual....

Anyhow, I won't do more tests about this since I have done what I can do here. If you have patches, they are welcome. Otherwise I suggest you just use dd to clone that. Forget about Clonezilla in your case.

Steven

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

2024-03-22T07:51:05.062000Z

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.

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

2024-03-22T07:13:44.412000Z

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.
In order to make sure that, I did it again with 2 bitlocker partitions.
You can see the attached files, similar naming and layouts. The only difference is this time there are two bitlocker partitions in the source machine:

/dev/nvme0n1p3: TYPE="BitLocker" PARTLABEL="Basic data partition" PARTUUID="304424e5-3809-4525-94c4-5e369d5ca1c4"
/dev/nvme0n1p5: TYPE="BitLocker" PARTUUID="96dd0c96-0afb-484c-b96b-f69f77d8b52f"

Please check the attached files. Everything runs smoothly.
Of course, I also booted the destination to make sure if the Windows 11 boots well or not, and the 2nd bitlocker partition can be accessed or not. Apparently it booted well, I could enter Windows 11, and the 2nd bitlocker drive asked me to enter the passphrase. I entered, and I can explorer that drive. Everything runs smoothly in the destination machine. The Windows 11 works well.

Steven

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

2024-03-21T17:13:43.729000Z

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.

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

2024-03-21T12:51:45.040000Z

Here I tried to reproduce the issue here. Similar to yours, I configured a MS Windows and a partition having bitlocker encrypted.
You can see the partitions info in the file "src-pt.txt", the /dev/nvme0n1p4 is the bitlocker encryption partition. The file "src.txt" is the running log in the source machine, and the file "dest.txt" is the log in the destination machine. As you can see, everything runs smoothly.
I am using the testing Clonezilla live 3.1.2-20 amd64.

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

2024-03-17T13:32:10.937000Z

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.