iiinova — where your digital self keeps evolving

ಚಿರಾಗ್ 🌹✊🏾Ⓥ🌱🇵🇸 (he/him) @chiraag.mastodon.online.ap.brid.gy · 09/02/2025

This is the output from lsblk, to make things clear. I ran it with --merge, so Crypto-Root points back to both nvme0n1p3_crypt and nvme1n1p1_crypt rather than being listed twice. I also left some free space in Crypto-Root so that I can create an LVM […] [Original post on mastodon.online]

Insane setup displayed through the output of lsblk as a tree, which shows three disks (sda, nvme0n1, and nvme1n1). sda only has one partition (sda1), its associated decrypted container (sda1_crypt), and one logical volume (CryptoData-Home, mounted on /home). nvme0n1 has 3 partitions: nvme0n1p1 (the EFI partition, mounted at /boot/efi), nvme0n1p2 (a partition mounted at /boot), and nvme0n1p3, the encrypted partition. nvme0n1p3 has an associated decrypted container (nvme0n1p3_crypt), which holds the swap partition (Crypto-Swap) and part of the root partition (Crypto-Root). nvme1n1 only has one partition (nvme1n1p1), which has an associated decrypted container (nvme1n1p1_crypt), which also belongs to Crypto-Root. To show the association of two disks with Crypto-Root, Crypto-Root is shown separately with arrows pointing back to both nvme0n1p3_crypt and nvme1n1p1_crypt.

101 1