Your message dated Wed, 22 Jan 2020 15:54:11 -0800
with message-id
<CAHnKnK0vRGa1XuFO=ef1znhj7urvz0umjdgiqrm1zgbwwd9...@mail.gmail.com>
and subject line Re: Bug#949130: refind-install fails to determine the ESP
partition
has caused the Debian Bug report #949130,
regarding refind-install fails to determine the ESP partition
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 ow...@bugs.debian.org
immediately.)
--
949130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: refind
Version: 0.11.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
on an existing installation, the refind package started to break apt-get
upgrade runs,
presumably with the availability of an update of the package.
The issue arrived w/o interaction on unattended upgrade runs and can easily
reproduced
by manual runs of refind-install.
The result of apt-get upgrade or unattended-upgrade runs:
> refind (0.11.4-1) wird eingerichtet ...
> Installing rEFInd to the ESP...
> mount: /boot/efi: /dev/sda2 already mounted on /boot/efi.
> dpkg: Fehler beim Bearbeiten des Paketes refind (--configure):
> »installiertes refind-Skript des Paketes post-installation«-Unterprozess gab
> den Fehlerwert 1 zurück
> Fehler traten auf beim Bearbeiten von:
> refind
The output of manually running refind-install is reproducably:
> $ sudo refind-install
> ShimSource is none
> Installing rEFInd on Linux....
> The ESP doesn't seem to be mounted! Trying to find it....
> mount: /boot/efi: /dev/sda2 already mounted on /boot/efi.
> ////boot/efi doesn't seem to be on a VFAT filesystem. The ESP must be
> mounted at //boot or //boot/efi and it must be VFAT! Aborting!
Notes:
- The ESP was mounted to /boot/efi before running refind-install, but is
unmounted by the command (and left unmounted).
- No explicit configuration of --root is given. The vast number of leading / is
produced by the script
- Running the script with /boot/efi mounted or unmounted does not change any
output
- The system is currently booting via refind using the ESP partition in
question, i.e. was set up by previous versions of refind
Expected output:
- The script should not add multiple leading slashes to the mount point and
then fail to find it in mtab or block device lists
- refind should update the installation to the new version
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages refind depends on:
ii debconf [debconf-2.0] 1.5.73
ii efibootmgr 15-1+b1
ii openssl 1.1.1d-2
ii parted 3.3-1
Versions of packages refind recommends:
ii python3 3.7.5-3
ii sbsigntool 0.9.2-2
refind suggests no packages.
-- debconf information:
* refind/install_to_esp: true
--- End Message ---
--- Begin Message ---
On Sun, 19 Jan 2020 at 09:40, Pelzi <pe...@feldner-bv.de> wrote:
> I found the cure for the problem: the ESP partition was listed as fs type
> „msdos“ in fstab. Changing this to „vfat" made refind-install work for me.
Ah nice catch! So it sounds like at most, this should be an upstream
feature request to have refind-install warn if fstab includes
"/boot/efi" but it's not vfat or something like that?
(Closing this issue accordingly as it was a system configuration
issue, not an issue with the refind package.)
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
--- End Message ---
