3.0alpha1 and LUKS - cryptsetup is removed by apt autoremove

GalliumOS / galliumos-distro

Docs, issues, and artwork sources for GalliumOS

https://galliumos.org/

GNU General Public License v2.0

347 stars 11 forks source link

3.0alpha1 and LUKS - cryptsetup is removed by apt autoremove #444

Closed ttle28c closed 5 years ago

ttle28c commented 6 years ago

GalliumOS 3.0alpha1 ISO install, LULU, MrChromebox Full Rom

When Gallium is installed to an LUKS encrypted partition, an apt autoremove will remove the cryptsetup package, rendering the system unbootable.

reynhout commented 6 years ago

@ttle28c I'd expect cryptsetup to be a dependency of the other LUKS packages, and thereby blocked from casual removal. I don't think we make any changes to the pkgs involved, but I'll double check on that.

In the meantime, to prevent an accidental pkg removal, you can mark the cryptsetup package as manually installed by running apt install cryptsetup. Then the pkg won't show up in the autoremove list.

nbastin commented 6 years ago

Using apt install can be dangerous (or at least have side effects). If you just want to set the package to not be autoremoved, you can use apt-mark:

sudo apt-mark manual cryptsetup cryptsetup-bin

gkra commented 6 years ago

I'd just like to point out that this still happens in 3.0alpha2, as well. workaround above has worked for me as well, so long as I remember to do it on first-boot after install.

anilgulecha commented 6 years ago

Is there a method to fix a system via the liveusb? I've custom setup a bunch of thigns on alpha2, and would not like to lose them. Is it possible to mount the mmc and place cryptsetup files?

anilgulecha commented 6 years ago

I fixed this in the liveusb mode via the following:

boot into liveUSB.
luksOpen and mount the volume with password. (Use the same name for volume as it is by default install)
mount /boot into /mnt/boot and / under /mnt/data
mount /dev /proc and /sys into /mnt/data/<dev/proc/sys>
chroot into /mnt/data
apt-get install cryptsetup (this should update the init ram disk as well).

Finally reboot. With this I got back into my old system and state.

anilgulecha commented 6 years ago

But the actual fix is for apt-mark to be run for cryptsetup so that autoremove does not remove it.

nsmith543 commented 5 years ago

Well after 3 reinstalls and ~4 hours wasted, lesson learned. Pay attention to apt-get autoremove! Took me embarassingly long to notice cryptsetup was being removed and was the cause of the boot issue.

This is still present in alpha7 btw.

reynhout commented 5 years ago

This should be resolved in recent pkgs