I performed a full disk clone using Clonezilla and a Coolgear USB 3.0 to IDE/SATA Adapter with Write-Protect Selection. I know that the drive was definitely mounting as read-only during the process because Clonezilla was reporting the read-only file systems during it's drive scanning phase.
Before testing the cloned disk, I first installed the original source disk back into the computer and it asked me for the bitlocker recovery key. Unlike other posts here, the key is not the issue because I have that.
What I am really curious about is why I'm even being asked for a key.
I know the drive was mounted as read-only via a SATA write blocker. Therefore, I have good reason to believe that the data on the drive is identical to what it was the last time the system booted.
The only likely scenario I can come up with is that the drive controller itself wrote some data. (I know for sure that S.M.A.R.T would of been updated to monitor the amount of times the drive has been powered on, the amount of hours it ran and not to mention a few hundred GigaBytes of data being read probably changed some other statistics.)
The drive was a SSD for reference.
I've skimmed through a lot of Microsoft documentation and a few white papers but didn't really get a good idea on what could've signaled a change outside of the drive's controller.
If anyone could provide some insight I'd much appreciate it.
Before testing the cloned disk, I first installed the original source disk back into the computer and it asked me for the bitlocker recovery key. Unlike other posts here, the key is not the issue because I have that.
What I am really curious about is why I'm even being asked for a key.
I know the drive was mounted as read-only via a SATA write blocker. Therefore, I have good reason to believe that the data on the drive is identical to what it was the last time the system booted.
The only likely scenario I can come up with is that the drive controller itself wrote some data. (I know for sure that S.M.A.R.T would of been updated to monitor the amount of times the drive has been powered on, the amount of hours it ran and not to mention a few hundred GigaBytes of data being read probably changed some other statistics.)
The drive was a SSD for reference.
I've skimmed through a lot of Microsoft documentation and a few white papers but didn't really get a good idea on what could've signaled a change outside of the drive's controller.
If anyone could provide some insight I'd much appreciate it.
