4/29/2023 0 Comments Truecrypt traveler diskmistakenly allowing Windows to initialize the drive, or performing a quick format), so the embedded backup header, if present, will almost always be usable. It's unlikely that both ends of the volume would be damaged simultaneously during a typical accident (e.g. a drive that was in an uninitialized and unpartitioned state when it was first encrypted) stores its volume headers at the very beginning of the drive, while the embedded backup headers are stored at almost the very end of the drive. (Earlier versions of TrueCrypt did not create an embedded backup header during volume creation.)Ī fully-encrypted device (e.g. Was the drive encrypted using a fairly recent (v6.0 or higher) version of TrueCrypt? If so, go into Mount Options, select "Use backup header embedded in volume if available" and try that. If you weren't seeing that "parameter is incorrect" message then I would probably lean towards the idea of rebuilding the partition table, but I think you'd better check on the drive's health first. I mention this so you can ask your friend how he used to select the drive, back when it was working, so we can figure out whether it's supposed to be an entire encrypted drive or an encrypted partition. To select a partition, the user generally wants to select something like "\Device\Harddisk1\Partition1" or some other partition number (not zero), but if the partition table was destroyed then those options will no longer be listed among the choices. If you try to select your encrypted volume via "Select Device" in TrueCrypt then you will see something like "Harddisk 1:", which TrueCrypt will display in the Device window as "\Device\Harddisk1\Partition0". Other symptoms are that Windows will now see the drive will as uninitialized. If you overwrite/destroy the partition table then TrueCrypt will no longer be able to find any partition-hosted volumes on the drive, or even their backup headers. Another possibility (again, excluding hardware damage) is that your friend encrypted a partition and then somehow destroyed the partion table. If your friend had encrypted an entire RAW (uninitialized and unpartitioned) hard drive then Enigm's suggestion probably would have worked (excluding hardware damage). Also, check the connections.Īs far as which drive or partition you are selecting, that's of secondary interest at the moment, but here's how it works: I've noticed that the vast majority of users who think they have encrypted their entire hard drive have actually just encrypted the single, maximally-sized partition that already exists on their hard drive. Are you sure it's being displayed by TrueCrypt and not by Windows?įor starters I'd try running the manufacturer's diagnostics on the drive to see if it's still healthy. It often indicates a hardware problem of some sort. That's a Windows error, not a TrueCrypt error. I've never seen TrueCrypt display that message, and I'm not even sure if it's in the code. If TrueCrypt can't find the starting location of a volume, or if the volume's header is damaged, or even if the volume has been inadvertantly overwritten, then after selecting the volume and entering the password you will always see the "Incorrect password or not a TrueCrypt volume" message, not "The parameter is incorrect". This business of which drive or partition you're selecting is interesting and it can also be the source of a fair bit of confusion, but I don't think it's particularly relevant to your current problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |