Hi Guilhem, Yes it is being run from an initramfs shell, sorry for leaving that out. Requested information is as follows;
cat /etc/crypttab sda5_crypt UUID=ec7880bc-c758-4681-8e94-b21f13752b48 none luks,discard cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> /dev/mapper/kali--vg-root / ext4 errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=5264b2eb-3b0c-4b82-896b-c44b1dd5bae6 /boot ext2 defaults 0 2 /dev/mapper/kali--vg-swap_1 none swap sw 0 0 Kind regards, Luke Flinders -----Original Message----- From: Guilhem Moulin <guil...@debian.org> Sent: 09 July 2019 15:39 To: Luke Flinders <lflind...@ip-performance.co.uk>; 931...@bugs.debian.org Subject: Re: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass Control: reassign -1 cryptsetup-initramfs 2:2.1.0 Control: tag -1 moreinfo Hi, On Tue, 09 Jul 2019 at 13:00:52 +0000, Luke Flinders wrote: > Error message is; > Error: Timeout reached while waiting for askpass > > Command run is; > cryptroot-unlock Are you running `cryptroot-unlock` from an initramfs shell? Could you please share your partitioning information (/etc/crypttab and /etc/fstab)? The message suggests that there is no cryptsetup (askpass) prompt running at this time, so I'd like to see how the device stack unfolds at initramfs stage. > The contents of this email message and any attachments are intended > solely for the addressee(s) and may contain confidential and/or > privileged information and may be legally protected from disclosure. Just for the record, this bug tracker is public :-) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931710 https://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/2019-July/008324.html Cheers, -- Guilhem.
