Your message dated Thu, 31 Jul 2025 09:14:55 +0200
with message-id <[email protected]>
and subject line Re: Bug#1110143: Update from Debian 12 to 13 failed
has caused the Debian Bug report #1110143,
regarding Update from Debian 12 to 13 failed
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.)
--
1110143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110143
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: grub2
Severity: critical
Hello,
after upgrade a fresh Debian 12 to Debian 13 I get the error:
[quote]
Setting up grub-cloud-amd64 (0.1.1) ...
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may
be missing from core image..
mdadm: cannot open /dev/md: No such file or directory
grub-install: error: cannot open `/dev/md': No such file or directory.
dpkg: error processing package grub-cloud-amd64 (--configure):
installed grub-cloud-amd64 package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
grub-cloud-amd64
Error: Sub-process /usr/bin/dpkg returned an error code (1)
[/quote]
update-grub:
[quote]
> update-grub
Generating grub configuration file ...
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some
modules may be missing from core image..
Found linux image: /boot/vmlinuz-6.12.38+deb13-amd64
Found initrd image: /boot/initrd.img-6.12.38+deb13-amd64
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some
modules may be missing from core image..
Found linux image: /boot/vmlinuz-6.1.0-37-amd64
Found initrd image: /boot/initrd.img-6.1.0-37-amd64
Adding boot menu entry for UEFI Firmware Settings ...
done
[/quote]
And grub-install
[quote]
> grub-install
Installing for x86_64-efi platform.
grub-install: warning: efivarfs_get_variable:
open(/sys/firmware/efi/efivars/blk0-47c7b225-c42a-11d2-8e57-00a0c969723b): No
such file or directory.
grub-install: warning: efi_get_variable: ops->get_variable failed: No such file
or directory.
grub-install: warning: efi_va_generate_file_device_path_from_esp: could not
open device for ESP: Bad address.
grub-install: warning: efi_generate_file_device_path_from_esp: could not
generate File DP from ESP: Bad address.
grub-install: error: failed to register the EFI boot entry: Bad address.
[/quote]
/etc/default/grub:
[quote]
> cat grub
# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="rd.driver=raid1,ahci,dm_mod,part_gpt domdadm dolvm
rd.lvm.vg=vg00 rd.lvm.lv=vg00/usr net.ifnames=0 biosdevname=0 intel_iommu=off
console=ttyS1,115200 console=tty0"
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via
VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
[/quote]
If you need more infos please ask
CU
Jörg
-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hello,
thanks for your hint.
Am Mittwoch, dem 30.07.2025 um 22:23 +0200 schrieb Chris Hofstaedtler:
> On Wed, Jul 30, 2025 at 07:20:50PM +0200, Jörg Frings-Fürst wrote:
> > Hello Felix,
> >
> > thanks for you quick answer.
> >
> >
> > Am Mittwoch, dem 30.07.2025 um 18:56 +0200 schrieb Felix Zielcke:
> > > Am Mittwoch, dem 30.07.2025 um 18:35 +0200 schrieb Jörg Frings-
> > > Fürst:
> > > > Source: grub2
> > > > Severity: critical
> > > >
> > > > Hello,
> > > >
> > > > after upgrade a fresh Debian 12 to Debian 13 I get the error:
> > > >
> > > >
> > > > [quote]
> > > > Setting up grub-cloud-amd64 (0.1.1) ...
> ^^^^^
>
> > A good question: I don't know. Its an dedicated Server from Ionos.
> ^^^^^^^^^
>
> How did you end up with the grub-cloud-amd64 installed? Please check
> your logs how it got installed.
>
> As far as I understand the grub-cloud-* limitations, you are
> probably outside of its design usecase.
>
Here ar the installed grub packges after new install of Debian 12 with
the IONOS image.
[quote]
# dpkg -l grub* | grep ii
ii grub-cloud-amd64 0.0.5 amd64 GRand Unified
Bootloader (cloud setup)
ii grub-common 2.06-13+deb12u1 amd64 GRand Unified
Bootloader (common files)
ii grub-efi 2.06-13+deb12u1 amd64 GRand Unified
Bootloader, version 2 (dummy package)
ii grub-efi-amd64 2.06-13+deb12u1 amd64 GRand Unified
Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.06-13+deb12u1 amd64 GRand Unified
Bootloader, version 2 (EFI-AMD64 modules)
ii grub-efi-amd64-signed 1+2.06+13+deb12u1 amd64 GRand Unified
Bootloader, version 2 (amd64 UEFI signed by Debian)
ii grub-pc-bin 2.06-13+deb12u1 amd64 GRand Unified
Bootloader, version 2 (PC/BIOS modules)
ii grub2-common 2.06-13+deb12u1 amd64 GRand Unified
Bootloader (common files for version 2)
[/quote]
The grub-cloud-amd64 was not installed by the other 4 Systems. So I have remove
them.
And the upgrade to Debian 13 runs now without any grub error.
So I close this bug.
> Chris
Many thanks.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Jörg Frings-Fürst
DE-54470 Lieser
L-Għarb, Gozo, MT-GRB 1131
git: https://git.jff.email/cgit/
Matrix: @joergff:matrix.org
My wish list:
- Please send me a picture from the nature at your home.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
