Manual partitioning for encrypted LVM setup is blockedWhy is Kali Linux so hard to set up? Why won't people help me?Installing Debian with encrypted root: installer does not see EFI /boot partitionOpen luks-encrypted partition from virtual DomU LVM disk containing another LVMKali Linux Install IssueHow do I partition my disk to install encrypted Debian installation alongside OSX?Partitioning for dual boot of two Linux systemsCreating custom sized LVM partitions during installation (Debian)?recover files after formatting and partitioning disk that originally had windows into kali linux?Unusable space problem while create swap area (installing kali linux)How to install Debian on encrypted LVM partition?new kali installation (EFI), I can't start on kali OS without the “super grub 2” usb keyDual boot of Kali Linux and Windows machine failed after installation!
How to add power-LED to my small amplifier?
Email Account under attack (really) - anything I can do?
Can I interfere when another PC is about to be attacked?
Motorized valve interfering with button?
Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?
Should I join office cleaning event for free?
What are these boxed doors outside store fronts in New York?
Why are only specific transaction types accepted into the mempool?
Set-theoretical foundations of Mathematics with only bounded quantifiers
Draw simple lines in Inkscape
Is it possible to make sharp wind that can cut stuff from afar?
How long does it take to type this?
What makes Graph invariants so useful/important?
Download, install and reboot computer at night if needed
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
How is this relation reflexive?
Are tax years 2016 & 2017 back taxes deductible for tax year 2018?
How do you conduct xenoanthropology after first contact?
declaring a variable twice in IIFE
Banach space and Hilbert space topology
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
Why was the small council so happy for Tyrion to become the Master of Coin?
Copenhagen passport control - US citizen
Possibly bubble sort algorithm
Manual partitioning for encrypted LVM setup is blocked
Why is Kali Linux so hard to set up? Why won't people help me?Installing Debian with encrypted root: installer does not see EFI /boot partitionOpen luks-encrypted partition from virtual DomU LVM disk containing another LVMKali Linux Install IssueHow do I partition my disk to install encrypted Debian installation alongside OSX?Partitioning for dual boot of two Linux systemsCreating custom sized LVM partitions during installation (Debian)?recover files after formatting and partitioning disk that originally had windows into kali linux?Unusable space problem while create swap area (installing kali linux)How to install Debian on encrypted LVM partition?new kali installation (EFI), I can't start on kali OS without the “super grub 2” usb keyDual boot of Kali Linux and Windows machine failed after installation!
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am trying to Install Kali Linux on my MacBook Pro for dual boot with Mac.
Here is the GUI I am talking about (the same is in Debian and Ubuntu, but just to clarify this I found image in google):
I actually did a single-partition installation already, but it is unencrypted. Suddenly, manual partitioning during install blocked me from performing it the right way with some weird error message.
My SSD is partitioned this way before installation of Kali:
- macOS EFI partition (I don’t touch it) - 100 MB
- macOS partition (encrypted APFS) - 90 GB
- Linux partition (EXT4) - 30 GB (should contain encrypted / root and swap)
- Linux boot partition (300 mb)
I’ve tried defining an encrypted partition for / root file system both with and without LVM. It shows an error with exclamation icon and text:
“you’ve selected root filesystem to be stored on an encrypted
partition. This feature requires a separate /boot partition ... go
back and setup /boot partition."
and blocks installation. Despite the fact that I have partition configured in manual partitioner GUI (#4 in my table) as “BIOS boot area”. There is no option to specify mount point for it though. So this looks weird bug in installer to me.
Notes: on MBP, it is not important to have macOS boot option. You can boot to macOS with Option key that detects macOS partitions regardless Linux bootloader so it is ok to use grub and graphical installer to me.
Can you suggest a step-by-step list of actions for manual partitioning in this case? I cannot find a guide, I always read about “Guided” when people discuss encrypted LVM, but “Guided” wipes all disk and other partitions.
Trying to add LVM is no different:
- Choose Manual Partitioning
- Create LVM group on top of EXT4 part
- Add volumes: root for / fs, and swap, format them properly
- Format partition #4 (outside LVM) as EFI boot area (“Use as:”)
- Set encryption for partitions swap and root (partitioner GUI has option for cryptsetup configuration listed right after LVM section)
- Cannot start installation, complains about /boot which cannot be specified as mount point anywhere)
kali-linux system-installation dual-boot debian-installer cryptsetup
asked Apr 4 at 18:36
CrollCroll
172111
|
show 3 more comments
I am trying to Install Kali Linux on my MacBook Pro for dual boot with Mac.
Here is the GUI I am talking about (the same is in Debian and Ubuntu, but just to clarify this I found image in google):
I actually did a single-partition installation already, but it is unencrypted. Suddenly, manual partitioning during install blocked me from performing it the right way with some weird error message.
My SSD is partitioned this way before installation of Kali:
- macOS EFI partition (I don’t touch it) - 100 MB
- macOS partition (encrypted APFS) - 90 GB
- Linux partition (EXT4) - 30 GB (should contain encrypted / root and swap)
- Linux boot partition (300 mb)
I’ve tried defining an encrypted partition for / root file system both with and without LVM. It shows an error with exclamation icon and text:
“you’ve selected root filesystem to be stored on an encrypted
partition. This feature requires a separate /boot partition ... go
back and setup /boot partition."
and blocks installation. Despite the fact that I have partition configured in manual partitioner GUI (#4 in my table) as “BIOS boot area”. There is no option to specify mount point for it though. So this looks weird bug in installer to me.
Notes: on MBP, it is not important to have macOS boot option. You can boot to macOS with Option key that detects macOS partitions regardless Linux bootloader so it is ok to use grub and graphical installer to me.
Can you suggest a step-by-step list of actions for manual partitioning in this case? I cannot find a guide, I always read about “Guided” when people discuss encrypted LVM, but “Guided” wipes all disk and other partitions.
Trying to add LVM is no different:
- Choose Manual Partitioning
- Create LVM group on top of EXT4 part
- Add volumes: root for / fs, and swap, format them properly
- Format partition #4 (outside LVM) as EFI boot area (“Use as:”)
- Set encryption for partitions swap and root (partitioner GUI has option for cryptsetup configuration listed right after LVM section)
- Cannot start installation, complains about /boot which cannot be specified as mount point anywhere)
kali-linux system-installation dual-boot debian-installer cryptsetup
asked Apr 4 at 18:36
CrollCroll
172111
1
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
1
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
1
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
1
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
1
@roaima sure, thanks!
– Croll
2 days ago
|
show 3 more comments
I am trying to Install Kali Linux on my MacBook Pro for dual boot with Mac.
Here is the GUI I am talking about (the same is in Debian and Ubuntu, but just to clarify this I found image in google):
I actually did a single-partition installation already, but it is unencrypted. Suddenly, manual partitioning during install blocked me from performing it the right way with some weird error message.
My SSD is partitioned this way before installation of Kali:
- macOS EFI partition (I don’t touch it) - 100 MB
- macOS partition (encrypted APFS) - 90 GB
- Linux partition (EXT4) - 30 GB (should contain encrypted / root and swap)
- Linux boot partition (300 mb)
I’ve tried defining an encrypted partition for / root file system both with and without LVM. It shows an error with exclamation icon and text:
“you’ve selected root filesystem to be stored on an encrypted
partition. This feature requires a separate /boot partition ... go
back and setup /boot partition."
and blocks installation. Despite the fact that I have partition configured in manual partitioner GUI (#4 in my table) as “BIOS boot area”. There is no option to specify mount point for it though. So this looks weird bug in installer to me.
Notes: on MBP, it is not important to have macOS boot option. You can boot to macOS with Option key that detects macOS partitions regardless Linux bootloader so it is ok to use grub and graphical installer to me.
Can you suggest a step-by-step list of actions for manual partitioning in this case? I cannot find a guide, I always read about “Guided” when people discuss encrypted LVM, but “Guided” wipes all disk and other partitions.
Trying to add LVM is no different:
- Choose Manual Partitioning
- Create LVM group on top of EXT4 part
- Add volumes: root for / fs, and swap, format them properly
- Format partition #4 (outside LVM) as EFI boot area (“Use as:”)
- Set encryption for partitions swap and root (partitioner GUI has option for cryptsetup configuration listed right after LVM section)
- Cannot start installation, complains about /boot which cannot be specified as mount point anywhere)
kali-linux system-installation dual-boot debian-installer cryptsetup
asked Apr 4 at 18:36
CrollCroll
172111
I am trying to Install Kali Linux on my MacBook Pro for dual boot with Mac.
Here is the GUI I am talking about (the same is in Debian and Ubuntu, but just to clarify this I found image in google):
I actually did a single-partition installation already, but it is unencrypted. Suddenly, manual partitioning during install blocked me from performing it the right way with some weird error message.
My SSD is partitioned this way before installation of Kali:
- macOS EFI partition (I don’t touch it) - 100 MB
- macOS partition (encrypted APFS) - 90 GB
- Linux partition (EXT4) - 30 GB (should contain encrypted / root and swap)
- Linux boot partition (300 mb)
I’ve tried defining an encrypted partition for / root file system both with and without LVM. It shows an error with exclamation icon and text:
“you’ve selected root filesystem to be stored on an encrypted
partition. This feature requires a separate /boot partition ... go
back and setup /boot partition."
and blocks installation. Despite the fact that I have partition configured in manual partitioner GUI (#4 in my table) as “BIOS boot area”. There is no option to specify mount point for it though. So this looks weird bug in installer to me.
Notes: on MBP, it is not important to have macOS boot option. You can boot to macOS with Option key that detects macOS partitions regardless Linux bootloader so it is ok to use grub and graphical installer to me.
Can you suggest a step-by-step list of actions for manual partitioning in this case? I cannot find a guide, I always read about “Guided” when people discuss encrypted LVM, but “Guided” wipes all disk and other partitions.
Trying to add LVM is no different:
- Choose Manual Partitioning
- Create LVM group on top of EXT4 part
- Add volumes: root for / fs, and swap, format them properly
- Format partition #4 (outside LVM) as EFI boot area (“Use as:”)
- Set encryption for partitions swap and root (partitioner GUI has option for cryptsetup configuration listed right after LVM section)
- Cannot start installation, complains about /boot which cannot be specified as mount point anywhere)
kali-linux system-installation dual-boot debian-installer cryptsetup
kali-linux system-installation dual-boot debian-installer cryptsetup
asked Apr 4 at 18:36
CrollCroll
172111
asked Apr 4 at 18:36
CrollCroll
172111
edited Apr 5 at 1:32
Croll
asked Apr 4 at 18:36
CrollCroll
172111
asked Apr 4 at 18:36
CrollCroll
172111
asked Apr 4 at 18:36
CrollCroll
172111
172111
1
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
1
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
1
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
1
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
1
@roaima sure, thanks!
– Croll
2 days ago
|
show 3 more comments
1
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
1
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
1
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
1
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
1
@roaima sure, thanks!
– Croll
2 days ago
1
1
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
1
1
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
1
1
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
1
1
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
1
1
@roaima sure, thanks!
– Croll
2 days ago
@roaima sure, thanks!
– Croll
2 days ago
|
show 3 more comments
1 Answer
1
active
oldest
votes
The answer to question and important clarifications are posted here in more focused question. Voilà!
As it turns out, for an encrypted root setup, there must be two bootloader related partitions:
- EFI system partition (for Linux boot)
- /boot partition (ext4) (for Linux boot)
edited 2 days ago
GAD3R
28k1958114
answered 2 days ago
CrollCroll
172111
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the/bootpartition is for the Linux OS to boot. One chains the next.
– roaima
2 days ago
1
In one day, sure. Thank you!
– Croll
2 days ago
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a/bootpartition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)
– telcoM
2 days ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510561%2fmanual-partitioning-for-encrypted-lvm-setup-is-blocked%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer to question and important clarifications are posted here in more focused question. Voilà!
As it turns out, for an encrypted root setup, there must be two bootloader related partitions:
- EFI system partition (for Linux boot)
- /boot partition (ext4) (for Linux boot)
edited 2 days ago
GAD3R
28k1958114
answered 2 days ago
CrollCroll
172111
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the/bootpartition is for the Linux OS to boot. One chains the next.
– roaima
2 days ago
1
In one day, sure. Thank you!
– Croll
2 days ago
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a/bootpartition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)
– telcoM
2 days ago
add a comment |
The answer to question and important clarifications are posted here in more focused question. Voilà!
As it turns out, for an encrypted root setup, there must be two bootloader related partitions:
- EFI system partition (for Linux boot)
- /boot partition (ext4) (for Linux boot)
edited 2 days ago
GAD3R
28k1958114
answered 2 days ago
CrollCroll
172111
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the/bootpartition is for the Linux OS to boot. One chains the next.
– roaima
2 days ago
1
In one day, sure. Thank you!
– Croll
2 days ago
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a/bootpartition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)
– telcoM
2 days ago
add a comment |
The answer to question and important clarifications are posted here in more focused question. Voilà!
As it turns out, for an encrypted root setup, there must be two bootloader related partitions:
- EFI system partition (for Linux boot)
- /boot partition (ext4) (for Linux boot)
edited 2 days ago
GAD3R
28k1958114
answered 2 days ago
CrollCroll
172111
The answer to question and important clarifications are posted here in more focused question. Voilà!
As it turns out, for an encrypted root setup, there must be two bootloader related partitions:
- EFI system partition (for Linux boot)
- /boot partition (ext4) (for Linux boot)
edited 2 days ago
GAD3R
28k1958114
answered 2 days ago
CrollCroll
172111
edited 2 days ago
GAD3R
28k1958114
edited 2 days ago
GAD3R
28k1958114
edited 2 days ago
GAD3R
28k1958114
28k1958114
answered 2 days ago
CrollCroll
172111
answered 2 days ago
CrollCroll
172111
answered 2 days ago
CrollCroll
172111
172111
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the/bootpartition is for the Linux OS to boot. One chains the next.
– roaima
2 days ago
1
In one day, sure. Thank you!
– Croll
2 days ago
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a/bootpartition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)
– telcoM
2 days ago
add a comment |
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the/bootpartition is for the Linux OS to boot. One chains the next.
– roaima
2 days ago
1
In one day, sure. Thank you!
– Croll
2 days ago
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a/bootpartition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)
– telcoM
2 days ago
1
1
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the
/boot partition is for the Linux OS to boot. One chains the next.– roaima
2 days ago
Yes, that would make sense (of sorts). The EFI system partition is for the computer to boot; the
/boot partition is for the Linux OS to boot. One chains the next.– roaima
2 days ago
1
1
In one day, sure. Thank you!
– Croll
2 days ago
In one day, sure. Thank you!
– Croll
2 days ago
3
3
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a
/boot partition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)– telcoM
2 days ago
Just for clarification, the "BIOS boot area" mentioned in the question is neither an EFI system partition nor a
/boot partition. It's only used if you plan to use a legacy BIOS bootloader on a GPT-partitioned disk: in that situation, it serves as the location to embed the GRUB core image. (On a MBR-partitioned disk, the GRUB core image will normally fit in the empty space between the actual MBR and the beginning of the first partition, which usually has almost 1 MiB of unused space.)– telcoM
2 days ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510561%2fmanual-partitioning-for-encrypted-lvm-setup-is-blocked%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Please click edit and add that weird message to your original question.
– K7AAY
Apr 4 at 18:37
1
@K7AAY please, take a look at updated question
– Croll
Apr 5 at 0:40
1
Nice trolling, but this is not the case. In fact, you just cannot answer the question. I suspect anyone who have ever done encrypted setup with dual boot for Ubuntu or Debian will be able to answer this, and I use Kali Linux for years. I don’t ask “why it is hard”, I just don’t understand is it Debian installer GUI bugged or me stupid
– Croll
Apr 5 at 1:29
1
@nwildner not really, given the OP explained this is the same for Debian and Ubuntu.
– roaima
2 days ago
1
@roaima sure, thanks!
– Croll
2 days ago