Results 1 to 2 of 2

Thread: External Drive Encryption Using KDE Part Manager In LXQT

  1. #1
    Join Date
    Jul 2005
    Beans
    49

    External Drive Encryption Using KDE Part Manager In LXQT

    Lubuntu version 19.10

    The reason I'm posting to the desktop environment section is that I used KDE Partition Manager which is specific to the Qt side of things.

    I've started an encryption job on a single partition 4 TB external 2.5 inch HDD drive connected via USB 3. I created a new partition table (GPT) and created a single partition encrypted using LUKS and formatted using ext3. The issue is that I'm now 12 hours into the job and the only feedback that I've seen from KDE Partition Manager is that the partition table was created successfully and the new partition format operation has started. The external HDD has an activity which is still flashing to show activity, so the drive appears to be doing *something*. This is being performed by a small box with an x5 8350 CPU which is not powerful but does support AES-NI. Currently, htop shows very little CPU activity however, so that doesn't seem to be the primary bottleneck.

    I'm trying to figure out which one of the many possibility might be the case:

    1. (Best case) These is something like a dd step being performed that just takes a while. Assuming this finishes in something like 24-48 hours I have no problem letting it continue to run.

    2. The operation failed invisibly somewhere in the background. I need to stop the current operation and find some way to do it manually. Years ago, the frontends in both KDE and Gnome for partition management used to be absolute trash and failures like this used to happen ~50% of the time. For the last 5-10 years though, they've seemed much more reliable to me. I'm not sure how likely this scenario is.

    3. My combination of hardware and options conflict in some way that I don't know about, and the software failed to warn me. Instead it decided to let me cause my own implosion because I was supposed to know that this was never going to work. (Probably the most Linux way of doing things).

    4. (Worst case) I did everything right, but LUKS is somehow really, really slow for this type of operation, so this is going to take weeks and KDE Part Manager has no progress bar or feedback so I'll never know. Entirely possible. If that's the case, it would be nice to know now, so I can find some other way of doing it. I can use Veracrypt on another computer and then just move the pre-encrypted HDD over to this machine.

    It's likely that the only response I'll get is ¯\_(ツ)_/¯ since it is so hard to know how long this takes for different combinations of hardware. It would be nice if anyone that has done encryption of several TB using LUKS could tell me whether this took you hours, days, or weeks to complete the operation though. It could help me narrow it down. Or maybe if there is a way that I can do this manually with a progress bar.

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: External Drive Encryption Using KDE Part Manager In LXQT

    Have you checked the system logs? Anything in there about connection problems or low power on the USB port?

    external 2.5inch HDDs without direct, external, power, only get power over USB. That means it will be slow, very slow.
    If you have a USB dock - they run $15-$25, you could pull the 2.5inch disk out, put it into the dock and have full power, full speed, for the disk.

    Why use EXT3 and not EXT4? EXT4 is what any new file systems should be using today.
    Hopefully, you have backups for this data planned. When an encrypted disk has any sort of failure, there is seldom any way to recover data except from a good, recent, backup.

    I don't use KDE or a non-LTS release. Perhaps the GUI tool used is laying down random data before putting the file system down? That is the more secure choice. With the cryptsetup tool, it is optional. GUI tools tend to provide 20% of the features of the CLI tools and try to do what 80% of the end-users would want. Someone going to the effort to encrypt would probably want the most secure setup.

    While you were at it, did you setup LUKS to use 2FA for unlocking? Say, with a yubikey and challenge-response? This can be added later. There are 8 "slots" for different unlock codes/methods for each LUKS container.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •