Hello all,
I just wanted to throw this out here and see if anyone has ever had a similar problem or knows of any work arounds…
I'm trying to clone a Sata HDD to the exact make/model/size Sata HDD.
When I go to boot the clone.. Windows gives me the "bluescreen of death" even when I try to boot in Safemode. I can't run chkdsk on the drive because it is encrypted.
Why wouldn't it boot if it's an exact clone and the hash matches? How does the "BS=" value and "conv=noerror,sync" option play a role in cloning - would this effect the clone???
Thanks!
Would it be possible for you to describe your setup for cloning, in detail? For example, did you use a write-blocker? If so, which one?
What was the entire command line that you used? Version of dcfldd?
no write-blocker, using a linux bootdisk similar to helix. it is the most recent version of DCFLDD (can't remember version #)
Going from a Sata HDD to Sata HDD. All model/make/size/etc matches up.
I have tried the following (with variable BS values 512, 1024, etc.)
DCFLDD IF=/DEV/SDA OF=/DEV/SDB BS=32k CONV=NOERROR,SYNC
DCFLDD IF=/DEV/SDA OF=/DEV/SDB BS=32k
If it's a hardware locked drive - you only cloned all "0" or "ff". Harddrive lock will send false info to the bus, thusly you did not clone the drive.
There are ways of removing harddrive locks - One of the Menz twins in California does it all the time for LE.
Mike,
If the drive is hardware locked, and only '0' or 'ff' is cloned, then what would produce the BSOD?
Thanks.
Itd def not locked.. Just a normal hard drive. Like I said the hashes even match up…
How important is it to clone to the same hard drive make/model/size??? What is the significance of this when cloning?
Thanks
Itd def not locked.. Just a normal hard drive. Like I said the hashes even match up…
How important is it to clone to the same hard drive make/model/size??? What is the significance of this when cloning?
Thanks
I have required the same HDD make and model sometimes when I run into issues, though this really shouldn't be an issue in most cases.
With the full disk encryption I've delt with, I can not clone a drive and stick it into another machine that is not the same make and model….or BSOD.
If you get a BSOD, you should get a minidmp..
That would be the first place to look to figure out the problem.
PM me if you have a minidmp, I may have time to take a look at it.
I'm not sure whether the OS was mentioned. Maybe it has something to do with the HD serial number/firmware, though I wouldn't think so. One thing to try is to boot the target drive with the XP/2K/? CD and do a repair. That may allow a boot, but may not identify the issue. You could go through some before and after comparison's if it's worth the effort.
You mention encryption. What is the drive encrypted with? It may be worth checking the documentation for the encryption product.
Maybe this is something to do with TPM? Does your motherboard have a TPM chip?
From http//
Full disk encryption and Trusted Platform Module
Trusted Platform Module (TPM) is a secure cryptoprocessor embedded in the motherboard that can be used to authenticate a hardware device. Since each TPM chip is unique to a particular device, it is capable of performing platform authentication. It can be used to verify that the system seeking the access is the expected system.
A limited number of full disk encryption solutions have support for TPM. These implementations can wrap the decryption key using the TPM, thus tying the hard disk drive (HDD) to a particular device. If the HDD is removed from that particular device and placed in another, the decryption process will in theory fail even if the attacker has the decryption password or token.
Although this has the advantage that the disk cannot be removed from the device, it might create a single point of failure in the encryption. For example, if something happens to the TPM or the motherboard, you might not be able to access your data simply by connecting the hard drive to another computer, unless you also have a separate recovery key.