Bug#853756: debian-installer: no cryptsetup available in rescue mode
Toni Mueller(2017-01-31): > > Toni Mueller (2017-01-31): > > > I downloaded the testing installer using Jigdo from here: > > > http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo > > > because the Jessie installer in 8.7.1 would not work for me (#750586). > > > > Well that isn't D-I Stretch RC 1 then. That one lives under: > > http://cdimage.debian.org/cdimage/stretch_di_rc1/ > > I'm confused - the testing CD does not use the latest d-i? See description here: http://cdimage.debian.org/cdimage/weekly-builds/ “latest d-i” is ambiguous. It can be the latest d-i build (see https://d-i.debian.org/daily-images/daily-build-overview.html), or the latest d-i release (D-I Stretch RC 1 right now). The image you're trying to use uses the former definition of “latest d-i”, as explained on the link above. > > Anyway, trying this image: > > f234f4aa708bdb226c0f412e85c37541c654526e > > downloads/debian-testing-amd64-netinst.iso > > I could set up an encrypted partition in the installation procedure, > just not access it during the rescue operation. > > $ sha1sum debian-testing-amd64-netinst.iso > 1d50301e6eccba6b116253f323cf397cfccd88fe debian-testing-amd64-netinst.iso > > Your image is different. I downloaded "mine" this morning, btw. I downloaded the iso directly instead of going through the jigdo dance, because it's oh so simpler, but maybe I hit a different iso, which would be slightly surprising… Anyway, I'm busy trying to find a workaround for RC 2 right now, so I'll avoid spending more time on this. > I used the manual method, because I wanted to have a RAID1 underneath. OK, fair. I know for a fact this works with Debian 8 since I've used this many time for Debian/Linux teaching sessions, with RAID1 and encrypted LVM on top of it; purposefully breaking the encrypted LVM (removing cryptsetup) then repairing from rescue mode. > > Given my test results above, we'll need those… > > Ok. I'll see what I can do. Thanks already! KiBi. signature.asc Description: Digital signature
Bug#853756: debian-installer: no cryptsetup available in rescue mode
Hi KiBi, On Tue, Jan 31, 2017 at 09:20:53PM +0100, Cyril Brulebois wrote: > Control: notfound -1 20170112 > Control: tag -1 moreinfo > > Toni Mueller(2017-01-31): > > I downloaded the testing installer using Jigdo from here: > > http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo > > because the Jessie installer in 8.7.1 would not work for me (#750586). > > Well that isn't D-I Stretch RC 1 then. That one lives under: > http://cdimage.debian.org/cdimage/stretch_di_rc1/ I'm confused - the testing CD does not use the latest d-i? > > > Were you prompted with a passphrase for the detected LUKS partition? > > When I tried to run the installer in the "rescue" mode, it did not > > prompt me with anything, but when it said something like "partition > > disks", it did not have any crypto entries. On the console, it was > > complaining about two missing modules, one of which ended with _crypto. > > > > I looked for cryptsetup, but could not find it. > > cryptsetup is the component installed in /target (the installed system), > not what d-i uses. > > Anyway, trying this image: > f234f4aa708bdb226c0f412e85c37541c654526e > downloads/debian-testing-amd64-netinst.iso I could set up an encrypted partition in the installation procedure, just not access it during the rescue operation. $ sha1sum debian-testing-amd64-netinst.iso 1d50301e6eccba6b116253f323cf397cfccd88fe debian-testing-amd64-netinst.iso Your image is different. I downloaded "mine" this morning, btw. > with a VM installed with guided encrypted LVM, and starting graphical > rescue mode, I'm getting prompted for a passphrase to unlock /dev/sda5 > as expected, so d-i seems to behave properly. I used the manual method, because I wanted to have a RAID1 underneath. > > > Syslog might be interesting (vt4, or /var/log/syslog from another vt). > > > > :/ > > > > I am sorry, but currently I can't produce those logs. > > Given my test results above, we'll need those… Ok. I'll see what I can do. Cheers, --Toni++
Bug#853756: debian-installer: no cryptsetup available in rescue mode
Control: notfound -1 20170112 Control: tag -1 moreinfo Hi, Toni Mueller(2017-01-31): > I downloaded the testing installer using Jigdo from here: > http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo > because the Jessie installer in 8.7.1 would not work for me (#750586). Well that isn't D-I Stretch RC 1 then. That one lives under: http://cdimage.debian.org/cdimage/stretch_di_rc1/ > > Were you prompted with a passphrase for the detected LUKS partition? > > When I tried to run the installer in the "rescue" mode, it did not > prompt me with anything, but when it said something like "partition > disks", it did not have any crypto entries. On the console, it was > complaining about two missing modules, one of which ended with _crypto. > > I looked for cryptsetup, but could not find it. cryptsetup is the component installed in /target (the installed system), not what d-i uses. Anyway, trying this image: f234f4aa708bdb226c0f412e85c37541c654526e downloads/debian-testing-amd64-netinst.iso (According to syslog: Jan 31 20:15:20 cdrom-detect: Detected CD 'Debian GNU/Linux testing "Stretch" - Official Snapshot amd64 NETINST Binary-1 20170131-16:00') with a VM installed with guided encrypted LVM, and starting graphical rescue mode, I'm getting prompted for a passphrase to unlock /dev/sda5 as expected, so d-i seems to behave properly. > > Syslog might be interesting (vt4, or /var/log/syslog from another vt). > > :/ > > I am sorry, but currently I can't produce those logs. Given my test results above, we'll need those… KiBi. signature.asc Description: Digital signature
Bug#853756: debian-installer: no cryptsetup available in rescue mode
Hi KiBi, On Tue, Jan 31, 2017 at 08:06:25PM +0100, Cyril Brulebois wrote: > Toni Mueller(2017-01-31): > > I have a system which uses a LUKS partition, but when I started the > > installer (fetched today) to repair something, it would not let me > > decrypt the partition, and thus denied me access to the system. > > Which image did you use? (Download URL?) I downloaded the testing installer using Jigdo from here: http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo because the Jessie installer in 8.7.1 would not work for me (#750586). > Were you prompted with a passphrase for the detected LUKS partition? When I tried to run the installer in the "rescue" mode, it did not prompt me with anything, but when it said something like "partition disks", it did not have any crypto entries. On the console, it was complaining about two missing modules, one of which ended with _crypto. I looked for cryptsetup, but could not find it. > Syslog might be interesting (vt4, or /var/log/syslog from another vt). :/ I am sorry, but currently I can't produce those logs. Cheers, --Toni++
Bug#853756: debian-installer: no cryptsetup available in rescue mode
Control: tag -1 - important Control: found -1 20170112 Hi, Toni Mueller(2017-01-31): > I have a system which uses a LUKS partition, but when I started the > installer (fetched today) to repair something, it would not let me > decrypt the partition, and thus denied me access to the system. Which image did you use? (Download URL?) Were you prompted with a passphrase for the detected LUKS partition? Syslog might be interesting (vt4, or /var/log/syslog from another vt). KiBi. signature.asc Description: Digital signature
Bug#853756: debian-installer: no cryptsetup available in rescue mode
Package: debian-installer Version: stretch RC1 Severity: important Tags: d-i Hi, I have a system which uses a LUKS partition, but when I started the installer (fetched today) to repair something, it would not let me decrypt the partition, and thus denied me access to the system. Cheers, --Toni++ -- System Information: Debian Release: 7.11 APT prefers oldstable APT policy: (990, 'oldstable'), (500, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash