I am new here, and to Debian.
I played with minimal Ubuntu to repurpose some otherwise unusable hardware into a mediaplayer/xbmc in the past,
unfortunately always with a pretty ignorant approach towards the final application and too long ago to be much good.
I started with with Debian in order to get a little more familiar with Linux systems and to use it as host for further test VM's,
where i ran into a problem which exceeds my searching skills.
I puzzled stuff together using LVM and cryptsetup Manual while using tutorials as orientation for the needed steps and order,
because I wasn't able to find a source delivering exactly what i wanted to do.
I probably just missed some crucial step while extending my LUKS encrypted System with additional Partitions,
which a more experienced user probably can easy identify so I am gonna start with what i did.
System (no Problems until here:, as far as i can tell)
-Dell Latitude e6220 with one 320GB Hdd and Debian 11 Bullseye
-Partitioning, LUKS2 encryption of "/" , LVM, during installation
-LUKS1 encryption of "/boot"
-added 2 encrypted Partitions in order to be able to easy remove Storage gradually and reassign it to VM's
-added entries in /"etc/crypttab"
System was booting fine and i could see the "/dev/mapper/..." via "lsblk" so i assumed that they got recognized correctly and proceeded as follows.
...hope u can bare with the photos, just did them as little reminder for myself, thinking everything went as planned.
Photos show procedure to add "sda4".
Same was applied to add "sda3" which is accordingly already visible.
In my inexperienced eyes everything looked fine so i proceeded downloading a rather large file to "/home/Downloads".
Then Firefox complained about lack of disk-space.
Clicking the popup made it disappear instead of revealing further information and i couldn't find the file.
Which probably was send to "/dev/null" caused by the LVM or OS not being able to see or handle the added disk-space.
Rebooting the system I noticed the following Warnings.
I also rebooted after adding "sda3" and "sda4" and probably overlooked them then.
So I started to check the filesystems.
Code: Select all
chnott@schnott:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 953M 0 part
│ └─boot_crypt 254:4 0 951M 0 crypt /boot
├─sda2 8:2 0 46.6G 0 part
│ └─sda2_crypt 254:0 0 46.6G 0 crypt
│ ├─vg--host-lv--root 254:1 0 20.5G 0 lvm /
│ ├─vg--host-lv--swap 254:2 0 7.4G 0 lvm [SWAP]
│ └─vg--host-lv--home 254:6 0 67.4G 0 lvm /home
├─sda3 8:3 0 24.4G 0 part
│ └─sda3_crypt_vg-host_ext1 254:5 0 24.4G 0 crypt
│ └─vg--host-lv--home 254:6 0 67.4G 0 lvm /home
└─sda4 8:4 0 24.4G 0 part
└─sda4_crypt_vg-host_ext2 254:3 0 24.4G 0 crypt
└─vg--host-lv--home 254:6 0 67.4G 0 lvm /home
Code: Select all
schnott@schnott:~$ sudo blkid
[sudo] password for schnott:
/dev/sda1: UUID="9c3e110f-9ef0-425c-894f-6615fd2fb1a7" TYPE="crypto_LUKS" PARTUUID="1647cd99-01"
/dev/sda2: UUID="3ba3350e-e2db-4102-ac69-695f361578e0" TYPE="crypto_LUKS" PARTUUID="1647cd99-02"
/dev/sda3: UUID="0853cf3e-711a-4ba6-bef5-19c30b75ef1d" TYPE="crypto_LUKS" PARTUUID="1647cd99-03"
/dev/sda4: UUID="49d2fc3c-24b5-4dd4-ad40-931ad62a1fbd" TYPE="crypto_LUKS" PARTUUID="1647cd99-04"
/dev/mapper/sda2_crypt: UUID="8S9OEZ-jh1f-p4JA-bZGB-SJfK-tzR1-MgZj5p" TYPE="LVM2_member"
/dev/mapper/vg--host-lv--root: LABEL="root" UUID="850309ba-7bcf-423b-a8e0-d18dde6ceca1" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/vg--host-lv--swap: UUID="1d96b69e-dd36-4cd4-abe7-c6a0ee1b7be6" TYPE="swap"
/dev/mapper/sda4_crypt_vg-host_ext2: UUID="ElA6Rk-5Y9i-yOWp-TiGu-rYYt-6JPO-cVoyTZ" TYPE="LVM2_member"
/dev/mapper/boot_crypt: UUID="b30a607e-be82-424c-808b-d3788395108c" BLOCK_SIZE="4096" TYPE="ext2"
/dev/mapper/sda3_crypt_vg-host_ext1: UUID="Mvrdym-IS10-IDCK-msAZ-EfbF-K0k7-V5Bqw6" TYPE="LVM2_member"
/dev/mapper/vg--host-lv--home: LABEL="home" UUID="529f0500-3df2-49c3-bc24-24a04936023b" BLOCK_SIZE="4096" TYPE="ext4"
Code: Select all
schnott@schnott:~$ sudo vgdisplay
--- Volume group ---
VG Name vg-host
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 3
Act PV 3
VG Size <95.34 GiB
PE Size 4.00 MiB
Total PE 24406
Alloc PE / Size 24406 / <95.34 GiB
Free PE / Size 0 / 0
VG UUID afpZck-7M3m-fjso-z1Bi-8WvS-d8YW-Wc4Xj4
Code: Select all
schnott@schnott:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv-home vg-host -wi-ao---- 67.41g
lv-root vg-host -wi-ao---- <20.49g
lv-swap vg-host -wi-ao---- 7.43g
Code: Select all
schnott@schnott:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 381M 1.6M 380M 1% /run
/dev/mapper/vg--host-lv--root 20G 4.7G 15G 25% /
tmpfs 1.9G 98M 1.8G 6% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mapper/boot_crypt 935M 113M 823M 13% /boot
/dev/mapper/vg--host-lv--home 19G 5.9G 12G 34% /home
tmpfs 381M 664K 381M 1% /run/user/1000
Process as I understood it....
As the warning during boot states its obviously some kind of UUID based hick-up.
Looks like I still suffer a gap in the understanding of the Filesystem-layers.
Looking at "/dev/sda3" as example.
"/dev/sda3" with it's UUID is recognized via "crypttab", gets decrypted to /"dev/mapper/..." with it's UUID which then is used by LVM to find the LV.
Since the UUID LVM is not able to find and the UUID of "/dev/mapper/..." via "blkid" is the same, I need some help at this point.
Where I am stuck...
Did I just have a fail in the Procedure which prevented update of the LVM-Label in the 2.nd 512MB Sector?
Is it just a timing issue where LVM is searching while the Partition is not decrypted yet?
Or do I have to make the disk-space I added to the LVM somehow known to the OS ? (maybe also the reason why the added space is visible via "lvs" but not via "df -h"?)
Or did I miss to update some Config-File; because LVM requires the UUID of "/dev/sda3" instead of UUID of /dev/mapper/..."?
Or am I so damn of that nothing I've done makes sense? ....still just standing in front of the rabbit whole.
Any help, or pointing towards the solution, or origin of my Problem would be much appreciated since it feels like I am starting to tumble over what little I understood yet.
Thanks for your Time.
Have a nice weekend.
mental