Page 1 of 1

notes in the margins

Posted: Mon Aug 07, 2023 1:33 pm
by babut
when creating an encrypted partition, use the console whenever possible. there are enough reasons for that. the first reason is that you will save a couple of days(days, Carl!!) if you create a partition using the command "dccon -format <ptN> -raw -q -a -p <password_in_double_quotes>". the number in "ptN" can be found through the "dccon -enum" command, but it should be borne in mind that it will display only disks with volumes(it does not matter if they have file systems). and only after that, create a file system on an encrypted disk using the operating system itself. yes, DC is not VC, DC assumes that you have a telepathic gift and a desire to dig into the most unexpected things.
the second reason is that the GUI often crashes. and although i have not noticed any negative consequences from this, but this does not mean that there are none.
if there are several encrypted partitions on the disk, they are selected through the "5" boot mode(this is mentioned only in passing in man, since you are supposed to have a telepathic gift) in dcsprop. it looks something like this:
<config key="BootMode">5</config>
<config key="BootDiskID">4250605865</config>
the problem is that i haven't found any way to find out this magically ID(i don't have a telepathic gift!), except in the GUI, but in the GUI, the ability to select a specific partition for bootload lives its unpredictable life, and in most cases is blocked.
if bootloader does not want to be installed, giving an error that it is already installed, but does not want to be deleted, then delete the DCS folder from the EFI partition of this disk. telepaths can guess for themselves.

and more. in practice, you will not get the speed that synthetic tests like DiskMark show, do not even hope. in the best case, the speed will be three times less for linear reading, and four times or more less for writing

Re: notes in the margins

Posted: Mon Aug 07, 2023 2:18 pm
by babut
and one more thing. like Veracrypt, DC also likes to go where it is not asked, namely to rename the bootloader bootmgfw.efi in the EFI Windows folder. as a result, you will get unexpected problems, if not immediately, then sometime later. when you install the DC loader from the GUI, DC will ask you should he behaving like a pig, but it's easy not to keep track of this. in any case, after everything, go to the EFI section on the disk and restore the order given to us by the lord god there, i.e. restore the previous bootx64.efi(or whatever you have according to the architecture. for example, i have a uefi shell instead), restore the Windows bootloader in the "\EFI\Windows\Boot" folder, delete the DCS entry from the UEFI table(it will not be displayed in the BIOS anyway) and create it again. it is better to do it right away than to be unprepared for changes later(and they will be!)

Re: notes in the margins

Posted: Mon Feb 05, 2024 1:02 pm
by Brend
Do think these changes in the EFI might be what caused the problem I reported here:

I ask because I don't understand EFI well enough to fully understand what you are writing about. But thank you, Babut.
I do wish there were clearer documentation for DiskCryptor in one place with clear install and uninstall instructions.