circ
November 10, 2019, 10:31pm
1
I have a new 1T drive installed in a Libem13v2.
I want to do a fresh install to a LUKS partition of 35G. That’s it.
bios-boot
LUKS volume /
empty space
Has anyone done this successfully?
The latest Live ISO installer is a fraught nightmare .
It seems that what’s possible is are the two options in the installation guide and absolutely nothing else.
I cannot :
create a 35G volume and format it to LUKS in manual install, mount /
create a 35G volume, format it to LUKS, mount it, target as ‘existing partition’
follow Advanced installation , but LUKS the root
follow default erase, install unencrypted, resize unencryped, create LUKS, restore resized image to LUKS, learn GRUB, configure grub, rebuild ramfs, chroot to install, grub-install
do anything whatsoever with any Logical Volumes.
following
Can you help with up to date docs and info?
I might just need a good resource for modern boot sequence tooling and options. This info space is a hot mess of outdated (maybe? (!?)) writing. Please say “go read this link ” (with, you know, useful stuff) because it will really help me.
I’m looking to accomplish the following on an upgraded (1G SSD) drive in a L13v2:
fresh PureOS install
other OS boots from this drive to play with (PureOS/byzantium ,Tails, Qubes, Kali, etc… I’m booting them fro…
I’m struggling to get a setup described here : New drive partitioning advice?
Can anyone explain the mounting process for the following ?
/root lives on an LV in a PV, in a LUKS container
What is the best way to get a GRUB handoff for boot? It’s failing miserably through a manual crtypsetup open /dev/sd# / mounting / chroot /mnt / grub-install (grub install is fine, boot can’t find the volume).
I guess I’m looking for the UUID relationship between GRUB, LUKS, LVM, fstab, and crypttab. grub-…
mladen
November 11, 2019, 10:56am
2
Could you please report a bug here: https://tracker.pureos.net ? Thanks!
4 Likes
circ
November 11, 2019, 7:12pm
3
Yeah, I guess I’ve been banging my head needlessly and it’s made me frustrated. I do have an installer log from one freeze, which I’m happy to file. Waiting for approval.
I’ve edited the title here to reflect my calmer demeanor today, but still feel that horrorshow is an accurate description.
I really just want to select the size of the partition created on a standard LUKS install. Just not the whole disk.
I guess I can jump on one or more of these as well or instead:
May, 2019: T750
April, 2019: T751
April, 2019: T752
April, 2019: T778
For general interest, here’s some info on booting, LUKS, GRUB, their interactions etc.
If you see errors or have other good stuff, drop it in.
I currated this through my living hell here :
TERMS
BIOS: Basic Input Output Stream
EPROM: Erasable Programmable Read Only Memory
GRUB: GRand Unified Bootloader
SEQUENCE
PureOS :
SeaBIOS
Lives on EPROM chip since it controls disks (can’t live on one), and needs acces pre-boot (can’t live in RAM)
GRUB
Lives one of many places ( boot block,…
Looks like the situation is similar to the one described in this post:
I have a Librem15rev3 which has a 512GB Samsung SSD as the only disk. The default installation of PureOS creates one large disk partition for the system and the /home-directories, plus a small /boot-partition and a swap-partition (if needed).
I would like to do the installation using (encrypted) LVM volume groups for the /root- and /home, and additional (standard-non-LVM) partitions for /boot and swap.
I have tried several ways using the PureOS-Live-distribution on a USB-Stick, but the only th…
What kind of disk is your 1T drive? I have a Samsung SSD 970 PRO, and got similar installer behavior like you.