Your message dated Sat, 9 Feb 2019 08:57:53 +0000
with message-id <[email protected]>
and subject line Re: Bug#919288: grub-pc: You can resolve this, this is invalid.
has caused the Debian Bug report #919288,
regarding /usr/sbin/grub-probe: error: failed to get canonical path of
`/dev/mapper/cryptroot'.
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 [email protected]
immediately.)
--
919288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919288
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-pc
Version: 2.02+dfsg1-10
Severity: important
Dear Maintainer,
I think the changes in -10 broke something in the probe script and it does not
properly recognize that partition anymore.
The changelog shows there were changes wrt LUKS and thet target
`/dev/mapper/cryptroot' is LUKS.
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/mapper/cryptroot / ext4 rw,noatime,errors=remount-ro 0 0
*********************** END /proc/mounts
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.4 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.69
ii grub-common 2.02+dfsg1-10
ii grub-pc-bin 2.02+dfsg1-10
ii grub2-common 2.02+dfsg1-10
ii ucf 3.0038+nmu1
grub-pc recommends no packages.
grub-pc suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Mon, Jan 14, 2019 at 06:30:26PM +0100, Haldir wrote:
> You can close this as invalid, for some reason /dev/mapper/cryptroot
> was gone, a reboot to a different kernel, which recreated the mapper
> and a subsequent apt-get install fixed the problem.
OK, closing with this message; thanks.
--
Colin Watson [[email protected]]
--- End Message ---
