Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #964220 > unrolled thread
| Started by | Sebastian Ramacher <sramacher@debian.org> |
|---|---|
| First post | 2019-07-12 03:10 +0200 |
| Last post | 2019-08-07 12:00 +0200 |
| Articles | 7 — 7 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Sebastian Ramacher <sramacher@debian.org> - 2019-07-12 03:10 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Diederik de Haas <didi.debian@cknow.org> - 2019-07-12 23:50 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Colin Watson <cjwatson@debian.org> - 2019-07-16 23:30 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found dirdi <debian@dirdi.name> - 2019-07-22 06:10 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found "Max Hofer" <max-hofer@gmx.net> - 2019-07-29 22:20 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Max Hofer <max-hofer@gmx.net> - 2019-07-30 22:00 +0200
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found "J. Pietschmann" <j.deb@pietschmann.ch> - 2019-08-07 12:00 +0200
| From | Sebastian Ramacher <sramacher@debian.org> |
|---|---|
| Date | 2019-07-12 03:10 +0200 |
| Subject | Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found |
| Message-ID | <yiSet-4Yd-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Package: grub-efi-amd64
Version: 2.04-1
Severity: grave
Hi,
since the last update the grub no longer works. It fails very early with
symbol `grub_file_filters` not found
and enters the rescue shell. After downgrading it back to 2.02+dfsg1-20
everything works again as expected.
Cheers
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/neptun-vg/root / ext4 rw,relatime 0 0
/dev/sda2 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0
/dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 d7aaa367-61ca-446f-b815-c2e79b8e4dfa
else
search --no-floppy --fs-uuid --set=root d7aaa367-61ca-446f-b815-c2e79b8e4dfa
fi
font="/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 d7aaa367-61ca-446f-b815-c2e79b8e4dfa
else
search --no-floppy --fs-uuid --set=root d7aaa367-61ca-446f-b815-c2e79b8e4dfa
fi
insmod png
if background_image /grub/.background_cache.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-74ba39e5-850a-42b8-93da-84fc7730af1e' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 d7aaa367-61ca-446f-b815-c2e79b8e4dfa
else
search --no-floppy --fs-uuid --set=root d7aaa367-61ca-446f-b815-c2e79b8e4dfa
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/neptun--vg-root ro intel_iommu=off quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.19.0-5-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-74ba39e5-850a-42b8-93da-84fc7730af1e' {
menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-advanced-74ba39e5-850a-42b8-93da-84fc7730af1e' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 d7aaa367-61ca-446f-b815-c2e79b8e4dfa
else
search --no-floppy --fs-uuid --set=root d7aaa367-61ca-446f-b815-c2e79b8e4dfa
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/neptun--vg-root ro intel_iommu=off quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.19.0-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-recovery-74ba39e5-850a-42b8-93da-84fc7730af1e' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 d7aaa367-61ca-446f-b815-c2e79b8e4dfa
else
search --no-floppy --fs-uuid --set=root d7aaa367-61ca-446f-b815-c2e79b8e4dfa
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/neptun--vg-root ro single intel_iommu=off
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.19.0-5-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg
*********************** BEGIN /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
unused devices: <none>
*********************** END /proc/mdstat
*********************** BEGIN LVM
--- Volume group ---
VG Name neptun-vg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 237.73 GiB
PE Size 4.00 MiB
Total PE 60859
Alloc PE / Size 60859 / 237.73 GiB
Free PE / Size 0 / 0
VG UUID sBLfQe-g2p8-ftPp-f2cQ-vQbh-PIaA-rCkwlB
--- Physical volume ---
PV Name /dev/dm-0
VG Name neptun-vg
PV Size 237.73 GiB / not usable 3.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 60859
Free PE 0
Allocated PE 60859
PV UUID advaML-fKVT-z0Sc-SV3G-h0HK-e7tF-XKOiHC
--- Logical volume ---
LV Path /dev/neptun-vg/root
LV Name root
VG Name neptun-vg
LV UUID O0XdeR-5Dmx-DeK4-8PYl-Je7C-cASY-2dfaF2
LV Write Access read/write
LV Creation host, time neptun, 2016-04-15 00:07:45 +0200
LV Status available
# open 1
LV Size 233.82 GiB
Current LE 59858
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/neptun-vg/swap_1
LV Name swap_1
VG Name neptun-vg
LV UUID 1HVf3y-eV9S-0ub0-FRr4-quFV-U5wo-IPwhVr
LV Write Access read/write
LV Creation host, time neptun, 2016-04-15 00:07:45 +0200
LV Status available
# open 0
LV Size 3.91 GiB
Current LE 1001
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
*********************** END LVM
*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Jul 12 02:36 ata-SAMSUNG_MZNLN256HCHP-00000_S1ZWNXAGB35460 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 12 02:36 ata-SAMSUNG_MZNLN256HCHP-00000_S1ZWNXAGB35460-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 12 02:36 ata-SAMSUNG_MZNLN256HCHP-00000_S1ZWNXAGB35460-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 12 02:36 ata-SAMSUNG_MZNLN256HCHP-00000_S1ZWNXAGB35460-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Jul 12 02:36 usb-USB007_mini-USB2BU_00000000000045-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 12 02:36 usb-USB007_mini-USB2BU_00000000000045-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 12 02:36 usb-USB007_mini-USB2BU_00000000000045-0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 9 Jul 12 02:36 wwn-0x5002538d407fd2b3 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 12 02:36 wwn-0x5002538d407fd2b3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 12 02:36 wwn-0x5002538d407fd2b3-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 12 02:36 wwn-0x5002538d407fd2b3-part3 -> ../../sda3
*********************** END /dev/disk/by-id
*********************** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jul 12 02:36 2019-07-06-10-25-17-00 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 12 02:36 49A7-AD30 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 12 02:36 6E89-B020 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Jul 12 02:36 a9c8a698-c18e-4dfd-bce8-0e5f0450bb81 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 12 02:36 d7aaa367-61ca-446f-b815-c2e79b8e4dfa -> ../../sda2
*********************** END /dev/disk/by-uuid
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages grub-efi-amd64 depends on:
ii debconf [debconf-2.0] 1.5.72
ii grub-common 2.04-1
ii grub-efi-amd64-bin 2.04-1
ii grub2-common 2.04-1
ii ucf 3.0038+nmu1
grub-efi-amd64 recommends no packages.
grub-efi-amd64 suggests no packages.
-- debconf information:
* grub2/linux_cmdline_default: quiet
grub2/kfreebsd_cmdline:
grub2/kfreebsd_cmdline_default: quiet
grub2/device_map_regenerated:
* grub2/force_efi_extra_removable: false
grub2/update_nvram: true
* grub2/linux_cmdline: intel_iommu=off
[toc] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2019-07-12 23:50 +0200 |
| Message-ID | <yjbAu-8ph-3@gated-at.bofh.it> |
| In reply to | #964220 |
Package: grub-efi-amd64 Followup-For: Bug #931896 I don't have grub-efi-amd64 installed, but I ran into the same problem. The only enabled lines in /etc/default/grub are these: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" Which, afaik, is the default. The versions reported are what's currently installed as with 2.04 my system doesn't boot. I'm not sure/don't understand what Colin meant with 'firmware'. My guess would be my BIOS, but I haven't changed that recently. But up until version 2.04 grub2 has worked perfectly well and I don't recall me having configured anything manually, so I wouldn't know why it would be misconfigured. Downgrading to version 2.02+dfsg1-20 makes it work again I can send my grub.cfg in a separate email if that would help. (How can I do a followup with bugreport so that the full output is reported as you'd get with an initial filing of a bug?) I get no errors during the upgrade to 2.04: root@host:~# aptitude unhold grub-pc root@host:~# aptitude safe-upgrade Resolving dependencies... The following packages will be upgraded: grub-common grub-pc grub-pc-bin grub2-common 4 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 0 B/4,283 kB of archives. After unpacking 1,353 kB will be used. Do you want to continue? [Y/n/?] Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done Preconfiguring packages ... (Reading database ... 514663 files and directories currently installed.) Preparing to unpack .../grub2-common_2.04-1_amd64.deb ... Unpacking grub2-common (2.04-1) over (2.02+dfsg1-20) ... Preparing to unpack .../grub-pc_2.04-1_amd64.deb ... Unpacking grub-pc (2.04-1) over (2.02+dfsg1-20) ... Preparing to unpack .../grub-pc-bin_2.04-1_amd64.deb ... Unpacking grub-pc-bin (2.04-1) over (2.02+dfsg1-20) ... Preparing to unpack .../grub-common_2.04-1_amd64.deb ... Unpacking grub-common (2.04-1) over (2.02+dfsg1-20) ... Setting up grub-common (2.04-1) ... Installing new version of config file /etc/grub.d/00_header ... Installing new version of config file /etc/grub.d/10_linux ... Installing new version of config file /etc/grub.d/20_linux_xen ... Setting up grub2-common (2.04-1) ... Setting up grub-pc-bin (2.04-1) ... Setting up grub-pc (2.04-1) ... Installing for i386-pc platform. Installation finished. No error reported. Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-4.19.0-5-amd64 Found initrd image: /boot/initrd.img-4.19.0-5-amd64 Found linux image: /boot/vmlinuz-4.16.0-2-amd64 Found initrd image: /boot/initrd.img-4.16.0-2-amd64 Found linux image: /boot/vmlinuz-4.13.0-1-amd64 Found initrd image: /boot/initrd.img-4.13.0-1-amd64 Found linux image: /boot/vmlinuz-4.9.0-3-amd64 Found initrd image: /boot/initrd.img-4.9.0-3-amd64 Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin Found Microsoft Windows XP Professional on /dev/sda2 done Processing triggers for man-db (2.8.5-2) ... Processing triggers for install-info (6.6.0.dfsg.1-2) ... WinXP doesn't actually boot iirc (been a LONG while since I tried) and the remaining non-upgraded packages are due to #928631. If you want/need more info, let me know. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages grub-efi-amd64 depends on: ii debconf [debconf-2.0] 1.5.72 ii grub-common 2.02+dfsg1-20 pn grub-efi-amd64-bin <none> ii grub2-common 2.02+dfsg1-20 ii ucf 3.0038+nmu1 grub-efi-amd64 recommends no packages. grub-efi-amd64 suggests no packages.
[toc] | [prev] | [next] | [standalone]
| From | Colin Watson <cjwatson@debian.org> |
|---|---|
| Date | 2019-07-16 23:30 +0200 |
| Message-ID | <ykDbm-50t-33@gated-at.bofh.it> |
| In reply to | #964220 |
On Tue, Jul 16, 2019 at 11:08:25PM +0200, MiloMak wrote: > Updated from 2.02+dfsg1-20 to 2.04-1 like the op and get similar to the op > > [1]https://i.imgur.com/jKYXOHs.png > > when i downgrade back to 2.02 grub boots without issue. I have debian > installed as: > /dev/sdc1 /boot/efi > /dev/sdc2 / (/boot is here) > > it has been working with: > # grep 'set root' /boot/grub/grub.cfg > set root='hd2,msdos2' To save time, I'd just like to point out that whatever "set root" says in /boot/grub/grub.cfg is basically irrelevant here. That describes the expected location of GRUB's modules, but it says nothing about where grub-install is installing GRUB's core image nor about where the firmware is loading GRUB from, and what matters here is that those last two things need to match. (It's also not interesting whether "set root" in your grub.cfg matches the value of the "root" variable that you see at run-time. The "set root" command is just a fallback, and what usually takes effect instead is the following "search" command which causes GRUB to try to find a file system by UUID or similar. On systems with multiple disks, it's unsurprising for this to result in something different from the guessed value.) > i see you say that the problem is most probably caused by a > misconfiguration. > > what should i be checking and how do i fix it? I think the only thing I can say to you is to repeat the advice I gave in the message that you were replying to just now (that is, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931896#10). You should at least start by going through each one of those questions and answering them. Since you appear to have multiple disks, it seems quite likely that the firmware might be booting from an EFI System Partition that isn't the same as the one you have mounted on /boot/efi, and if so then that's something you need to correct. -- Colin Watson [cjwatson@debian.org]
[toc] | [prev] | [next] | [standalone]
| From | dirdi <debian@dirdi.name> |
|---|---|
| Date | 2019-07-22 06:10 +0200 |
| Message-ID | <ymxO9-2Ok-1@gated-at.bofh.it> |
| In reply to | #964220 |
Package: grub-pc Followup-For: Bug #931896 I ran into this bug, too. The values of all set variables (prefix, root) seemed to be sane and "ls $prefix/i386-pc" returned a list of *.mod files as expected. However, when I tried to load the "normal" module, the error was risen again: > grub rescue> insmod normal > error: symbol 'grub_file_filters' not found. Hence, I do not think that this is caused by a misconfiguration of some path variable. Downgrading to 2.02+dfsg1-20 resvoled the issue for me, too. apt log snippet: > Preparing to unpack .../19-grub-pc_2.04-1_amd64.deb ... > Unpacking grub-pc (2.04-1) over (2.02+dfsg1-20) ... > Preparing to unpack .../20-grub2-common_2.04-1_amd64.deb ... > Unpacking grub2-common (2.04-1) over (2.02+dfsg1-20) ... > Preparing to unpack .../21-grub-pc-bin_2.04-1_amd64.deb ... > Unpacking grub-pc-bin (2.04-1) over (2.02+dfsg1-20) ... > Preparing to unpack .../22-grub-common_2.04-1_amd64.deb ... > Unpacking grub-common (2.04-1) over (2.02+dfsg1-20) ... > ... > Setting up grub-common (2.04-1) ... > Installing new version of config file /etc/grub.d/00_header ... > Installing new version of config file /etc/grub.d/10_linux ... > Installing new version of config file /etc/grub.d/20_linux_xen ... > ... > Setting up grub2-common (2.04-1) ... > Setting up grub-pc-bin (2.04-1) ... > Setting up grub-pc (2.04-1) ... > Installing for i386-pc platform. > grub-install: warning: File system `ext2' doesn't support embedding. > grub-install: warning: Embedding is not possible. GRUB can only be > installed in this setup by using blocklists. However, blocklists are > UNRELIABLE and their use is discouraged.. > Installation finished. No error reported. > Generating grub configuration file ... > Found background image: .background_cache.png > Found linux image: /boot/vmlinuz-4.19.0-5-amd64 > Found initrd image: /boot/initrd.img-4.19.0-5-amd64 > Found linux image: /boot/vmlinuz-4.19.0-4-amd64 > Found initrd image: /boot/initrd.img-4.19.0-4-amd64 > done
[toc] | [prev] | [next] | [standalone]
| From | "Max Hofer" <max-hofer@gmx.net> |
|---|---|
| Date | 2019-07-29 22:20 +0200 |
| Message-ID | <ypkhI-2Y0-1@gated-at.bofh.it> |
| In reply to | #964220 |
> I was also hit by this bug after upgrading yesterday (it has been few > weeks since I updated the machine). Just like others, I also had to > downgrade the following packages to 2.02 to get it working. > > 1. grub-common > 2. grub2-common > 3. grub-efi-amd64-bin > 4. grub-efi-amd64 > 5. grub-pc-bin I hit the same problem today. Could you please provide the information, how you downgraded the packages on a non bootable system? Regards Max
[toc] | [prev] | [next] | [standalone]
| From | Max Hofer <max-hofer@gmx.net> |
|---|---|
| Date | 2019-07-30 22:00 +0200 |
| Message-ID | <ypGrU-89l-3@gated-at.bofh.it> |
| In reply to | #964220 |
Am Dienstag, 30. Juli 2019, 01:21:43 CEST schrieb Jiri Palecek: > On 29. 07. 19 22:12, Max Hofer wrote: > >> I was also hit by this bug after upgrading yesterday (it has been few > >> weeks since I updated the machine). Just like others, I also had to > >> downgrade the following packages to 2.02 to get it working. > >> > >> 1. grub-common > >> 2. grub2-common > >> 3. grub-efi-amd64-bin > >> 4. grub-efi-amd64 > >> 5. grub-pc-bin > > > > I hit the same problem today. Could you please provide the information, > > how you downgraded the packages on a non bootable system? > > You gotta find something that boots. Either installation pendrive or CD, > or live CD or another disc. Then mount your regular disk as in > somedirectory, mount /proc, /sys, /dev in somedirectory, chroot into > somedirectory and then it is a simple matter for apt. (You may have to > edit sources.list) > > I went through it with my qemu images. > > Regards > > Jiri Palecek Thx for pointing me in the right direction, I was able to fix my problem. It seems my system broke because the install_devices was configured to the partition and not the device. $ lsblk --output NAME,TYPE,SIZE,FSTYPE,MOUNTPOINT,PTTYPE,MODEL NAME TYPE SIZE FSTYPE MOUNTPOINT PTTYPE MODEL sda disk 232.9G dos Samsung_SSD_840_EVO_250GB ├─sda1 part 333M ext4 / dos ├─sda2 part 1K dos ├─sda5 part 8.4G btrfs /usr dos ├─sda6 part 2.8G btrfs /var dos ├─sda7 part 27.7G swap [SWAP] dos ├─sda8 part 380M btrfs /tmp dos └─sda9 part 193.4G btrfs /home dos # Configuration which broke my system with the upgrade from 2.02 to 2.04 $ sudo debconf-show grub-pc|grep install_devices: * grub-pc/install_devices: /dev/disk/by-id/ata- Samsung_SSD_840_EVO_250GB_S1DBNSADC65873B-part1 # Configuration which worked when I upgraded from 2.02 to 2.04 $ sudo debconf-show grub-pc|grep install_devices: * grub-pc/install_devices: /dev/disk/by-id/ata- Samsung_SSD_840_EVO_250GB_S1DBNSADC65873B I vaguely remember that one of the grub upgrades (a long time ago) asked me if I would like to change the installation location but as far as I remember I never changed it. Regards Max
[toc] | [prev] | [next] | [standalone]
| From | "J. Pietschmann" <j.deb@pietschmann.ch> |
|---|---|
| Date | 2019-08-07 12:00 +0200 |
| Message-ID | <ysqTE-6kh-11@gated-at.bofh.it> |
| In reply to | #964220 |
Hi, I have a similar problem with plain grub-pc (no EFI) I use the first two HDD as an MDM array and installed grub on both /dev/sda and /dev/sdb. A few weeks ago the first HDD failed and was replaced, and I used update-grub grub-install /dev/sda afterwards and could reboot the computer without problems. The next reboot after the upgrade to grub 2.04 failed with symbol `grub_file_filters` not found The grub update didn't show anything interesting on the console or dpgk.log The problem appears to be that grub 2.04 uses only devices by disk-id and didn't install on /dev/sda even though grub 2.02 did. Fortunately dpkg-reconfigure grub-pc fixes the calamity. What's the preferred way to reinstall grub on a new disk with 2.04? Preferrably non-interactive/scriptable. Cheers
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web