

I realize now i may have been confused as you didn’t specify everything.Is the LUKS volume created right on the disk on a raw partition?


I realize now i may have been confused as you didn’t specify everything.Is the LUKS volume created right on the disk on a raw partition?


Edit: meant this to be a comment reply, not a post reply.


You can’t resize the filesystem without first resizing the crypted volume.
You would expand this LV. Expand the crypted volume. The decrypt the volume and expand the underlying filesystem.


Does it do screen sharing distributed via the server?


Go spam elsewhere
Not at all. I didn’t mean to imply it was plagued with issues, but I did run into them every now and then. Nothing I couldn’t ever resolve either but it’s still not something I’d recommend to a novice unless they are open to potentially breaking their system in a way that may be unknown to them.
I exclusively use Debian stable. I ran unstable for a while but in general I never felt like it gave me anything I needed. I also do not recommend running unstable unless you’re very familiar with Debian and are easily able to work out issues. They didn’t come up often, but they did come up.


Hm. Well I certainly agree that privacy invasive stuff is absolutely unwelcome but I’m also a pretty big fan of backup cameras. I bought a 2023 and while it does have the “infotainment” and backup can, outside of that it’s all quite dum and everything outside of like bluetooth paring and general infotainment stuff is all physical buttons.
So really my point is while it is unusual, even brand new vehicles can manage to avoid the privacy nightmare.


Why 2016 specifically?
I saw in another comment your lsblk output and yes I see the LUKS partition spans the whole disk.
So yes, the commands you listed should be sufficient. It will extend the decrypted logical volume to use the remaining free space of your volume group.