![]() ![]() If my memory serves me well, TC will make a back-up of the original boot-loader but can't remember if there was a setting that lets you boot the original one once ESC is pushed. The TC boot-loader should then be configured to try boot other partitions if ESC is pushed, in effect giving control to GRUB when it finds it at the beggining of the partition where you installed it to. The boot-loader should be installed on the MBR, and GRUB installed on some primary partition (/boot, let's say). ![]() I'm unable to find documentation for the boot loader, but I remember it was simple to set-up to work with Linux. iso back-up to a CD/DVD this time, as it will let you use the media to boot into your Windows, in case you overwrite the BL again. Now that you're safe, you should be able to re-install the boot-loader by using TrueCrypt from your Linux and configure it as you did before. This is very important to have, because if the header is lost / corrupt, it practically means your data is lost forever! I suggest you test first that your data is intact, and once you're able to access it, make a backup of the volume's header. Note that you have to toggle the "system volume" option when mounting. If you boot into another system with TrueCrypt installed (you can use your Linux, there is a TrueCrypt version for Linux as well), you could mount your partition and access the data. What this means is, your data should still be accessible. The first track of the system drive and/or on the TrueCrypt Rescue For system encryption (see theĬhapter System Encryption), the last 512 bytes of the first logicalĭrive track are read into RAM (the TrueCrypt Boot Loader is stored in The first 512 bytes of the volume (i.e., the standard volume header)Īre read into RAM, out of which the first 64 bytes are the salt (see From the TrueCrypt encryption scheme, system volume header resides at the end of the volume, and should still be there, even if you have overwritten the boot loader. ![]()
0 Comments
Leave a Reply. |