我怎么能有两个Ubuntu安装，一个是全磁盘加密的？

Question

我想要完全隔离我的工作和个人操作系统，所以我已经在我的电脑上安装了两个磁盘，因为我的工作需要完整的磁盘加密。

我已经成功地在一个驱动器上安装了Windows和Kubuntu，但似乎无法在另一个驱动器上安装加密的Ubuntu (无论如何旋转)。

我试过两件事。只是告诉安装程序使用整个磁盘与加密的LVM，并手动设置分区和安装到它。

当我告诉它使用整个磁盘进行加密的LVM引导安装时，它告诉我syslog包含了整个混乱，我不确定问题出在哪里。驱动器0是一个未加密的Windows和我的个人安装，驱动器1是我要安装在这里。

Oct 30 08:32:19 kubuntu ubiquity: /var/lib/partman/devices/=dev=nvme1n1
Oct 30 08:32:20 kubuntu systemd-udevd[142246]: nvme1n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p3' failed with exit code 1.
Oct 30 08:32:20 kubuntu systemd-udevd[142243]: nvme1n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p1' failed with exit code 1.
Oct 30 08:32:20 kubuntu systemd-udevd[142245]: nvme1n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p2' failed with exit code 1.
Oct 30 08:32:20 kubuntu kernel: [ 3067.145760]  nvme1n1: p1 p2 p3
Oct 30 08:32:20 kubuntu systemd-udevd[142275]: nvme1n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p1' failed with exit code 1.
Oct 30 08:32:20 kubuntu systemd-udevd[142278]: nvme1n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p3' failed with exit code 1.
Oct 30 08:32:20 kubuntu systemd-udevd[142277]: nvme1n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p2' failed with exit code 1.
Oct 30 08:32:20 kubuntu kernel: [ 3067.998718]  nvme1n1: p1 p2 p3
Oct 30 08:32:21 kubuntu systemd-udevd[142275]: nvme1n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p3' failed with exit code 1.
Oct 30 08:32:21 kubuntu systemd-udevd[142277]: nvme1n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p2' failed with exit code 1.
Oct 30 08:32:21 kubuntu systemd-udevd[142278]: nvme1n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p1' failed with exit code 1.
Oct 30 08:32:21 kubuntu partman: mke2fs 1.46.5 (30-Dec-2021)
Oct 30 08:32:21 kubuntu partman-crypto: kernel entropy_avail: 256 bits
Oct 30 08:32:30 kubuntu partman-crypto: WARNING: Device /dev/nvme1n1p3 already contains a 'crypto_LUKS' superblock signature.
Oct 30 08:32:32 kubuntu partman-crypto: No key available with this passphrase.
Oct 30 08:32:40 kubuntu kwin_x11[12890]: kwin_core: XCB error: 152 (BadDamage), sequence: 59632, resource id: 14716285, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Oct 30 08:32:40 kubuntu kernel: [ 3087.751753]  nvme0n1: p1 p2 p3 p4 p5
Oct 30 08:32:40 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:40 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:40 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:40 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:40 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:40 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:40 kubuntu systemd-udevd[144979]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
Oct 30 08:32:40 kubuntu systemd-udevd[144980]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1.
Oct 30 08:32:40 kubuntu systemd-udevd[144978]: nvme0n1p5: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p5' failed with exit code 1.
Oct 30 08:32:40 kubuntu systemd[1]: tmp-tmp.xhYzjKQpjU.mount: Deactivated successfully.
Oct 30 08:32:40 kubuntu systemd-udevd[144977]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
Oct 30 08:32:40 kubuntu systemd-udevd[144981]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
Oct 30 08:32:40 kubuntu systemd[1]: tmp-tmp.xhYzjKQpjU.mount: Deactivated successfully.
Oct 30 08:32:40 kubuntu ubiquity: mount: /tmp/tmp.xhYzjKQpjU: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:40 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.
Oct 30 08:32:40 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:40 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:40 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:40 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:40 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:40 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:40 kubuntu ubiquity: mount: /tmp/tmp.lZXCXAPqpp: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:40 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.
Oct 30 08:32:40 kubuntu kernel: [ 3088.011850]  nvme0n1: p1 p2 p3 p4 p5
Oct 30 08:32:40 kubuntu kernel: [ 3088.034833]  nvme1n1: p1 p2 p3
Oct 30 08:32:41 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:41 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:41 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:41 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:41 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:41 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:41 kubuntu systemd-udevd[144979]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[144980]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[145030]: nvme0n1p5: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p5' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[144981]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[144977]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
Oct 30 08:32:41 kubuntu ubiquity: mount: /tmp/tmp.G7NB4dtY8C: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:41 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.
Oct 30 08:32:41 kubuntu systemd-udevd[144978]: nvme1n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p3' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[145029]: nvme1n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p2' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[145031]: nvme1n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1p1' failed with exit code 1.
Oct 30 08:32:41 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:41 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:41 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:41 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:41 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:41 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:41 kubuntu ubiquity: mount: /tmp/tmp.pNOkIfiSWm: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:41 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.
Oct 30 08:32:41 kubuntu kernel: [ 3088.208138]  nvme0n1: p1 p2 p3 p4 p5
Oct 30 08:32:41 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:41 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:41 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:41 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:41 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:41 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:41 kubuntu systemd-udevd[144979]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[145796]: nvme0n1p5: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p5' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[144980]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1.
Oct 30 08:32:41 kubuntu ubiquity: mount: /tmp/tmp.tTk52jqdMM: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:41 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.
Oct 30 08:32:41 kubuntu systemd-udevd[144981]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
Oct 30 08:32:41 kubuntu systemd-udevd[144977]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
Oct 30 08:32:41 kubuntu ubiquity: NTFS signature is missing.
Oct 30 08:32:41 kubuntu ubiquity: Failed to mount '/dev/nvme0n1p2'
Oct 30 08:32:41 kubuntu ubiquity: : Invalid argument
Oct 30 08:32:41 kubuntu ubiquity: The device '/dev/nvme0n1p2' doesn't seem to have a valid NTFS.
Oct 30 08:32:41 kubuntu ubiquity: Maybe the wrong device is used? Or the whole disk instead of a
Oct 30 08:32:41 kubuntu ubiquity: partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Oct 30 08:32:41 kubuntu ubiquity: mount: /tmp/tmp.7U9XGuZFRp: unknown filesystem type 'crypto_LUKS'.
Oct 30 08:32:41 kubuntu ubiquity:        dmesg(1) may have more information after failed mount system call.

然后，我尝试手动创建分区，然后安装到它们上。

首先，我打开了分区编辑器，使用LUKS创建了一个LVM卷，添加了一个卷组，并向其中添加了一个ext4分区。除了syslog中的以下消息导致grub安装失败外，这几乎是有效的

grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/etc/default/grub'.

我试着搜索这个错误，但是不能真正理解结果。我认为棘手之处在于你把grub放在了这个案子里。显然，个人Ubuntu安装已经安装到驱动器0的UEFI系统分区，但是告诉加密的安装这样做失败了。请注意，我不想解密工作分区来引导我的个人操作系统。

Answer 1

我有一个冒险的驱动器，碰巧包含一个Lubuntu iso为我的Chromebook，我想，为什么不。不管出于什么原因，Lubuntu安装程序都没有这个bug，并且会很高兴地安装一个加密的Lubuntu。我不得不采取两个步骤，使一切按照我喜欢的方式进行。

首先，我不想要卢本图。通过安装ubuntu-desktop或kubuntu-desktop，然后删除lubuntu-desktop和任何其他剩菜，就可以很容易地解决这个问题。我选择了Kubuntu，它已经使用了SDDM。您需要在系统设置中将主题切换到KDE，否则会发生奇怪的事情。

然后，出现了食物问题。现在我有了一个加密的grub，它可以引导所有的OSes，但是不管怎么说都需要一个密码。我有未加密的grub，它看不到加密的安装。最后，我向/etc/grub.d/40-custom添加了一个自定义菜单项：

menuentry "Work Linux" {
    insmod part_gpt
    insmod search_fs_uuid
    insmod chain
    search --fs-uuid --no-floppy --set=root 6CB2-14E8
    chainloader ($root)/efi/ubuntu/grubx64.efi
}

然后运行sudo update-grub。因此，现在未加密的grub检测到它自己的安装Windows，并可以将其链接到加密的磁盘中，然后该磁盘将提示输入密码。

注意: UUID是从ls -l /dev/disk/by-uuid获得的

如果不是因为卢本图的运气，我可能会删除另一个驱动器。但这仍然会留下链式装载的问题。不管怎样，现在看来一切都正常了。