[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#646704: marked as done (live-installer: installer doesn't write /etc/crypttab for crypt+LVM)

Your message dated Mon, 2 Nov 2020 18:47:25 +0200
with message-id <95371f9a-427f-bc97-f9b7-0b29d3c47057@debian.org>
and subject line Fixed in previous upload
has caused the Debian Bug report #646704,
regarding live-installer: installer doesn't write /etc/crypttab for crypt+LVM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
646704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646704
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: grave
Justification: renders package unusable

I installed today a debian stable with debian-6.0.3-rescue-amd64.
I tried to use crypt+LVM, with / and /home in a Volume Group on a
crypted partition (/dev/sda6).

Hower the installation finishes well, boot on the fresh install is
impossible because initrd doesn't find this crypted Volume Group.

The problem is solved with the add of a line of this type
in /etc/crypttab :

	crypted_volume	UUID=XXXXX-XXXX-XXX-XX.... none luks

and a rebuild of initramfs. (I updated the kernel 2.6.32 -> 3.0.0-1
too.)

It's strange that Debian installer doesn't handle this step of the
process, and make the installation unusable !

Maybe there is an error because I've put my /boot on a VG too, 
but the GRUB was fine with that and all works perfectly after the
operations.

Don't hesitate to tell me if you need more informations or some
command(s) result(s).

Bests regards,
Eloi COUTANT

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
This appears to have been fixed quite some time ago in:
https://salsa.debian.org/installer-team/live-installer/-/commit/17678631e40f9fe31791bf90394fa81d87cce615

Closing bug.

--- End Message ---
Reply to: