*** This bug is a duplicate of bug 1891680 ***
https://bugs.launchpad.net/bugs/1891680
A number of upgrade issues were addressed in grub2 2.04-1ubuntu26.4 in
20.04, which was released back in September. I am going to mark this as
a duplicate of bug #1891680.
However, where the grub debconf
I also experienced this bug when upgrading my Azure VM from 18.04 to
20.04.
Attempting to correct the issue using the following suggested fix:
https://askubuntu.com/a/1188828
Is there any update to if this bug will be fixed?
--
You received this bug notification because you are a member of
I faced this issue while upgrading a cloud-based system from 18.04 to
20.04.
Naturally I had created a snapshot of the system before attempting the
upgrade it, so when the upgraded system failed to boot, and after having
read much of what may have caused it here and elsewhere, I restored the
Marking this bug as higher severity doesn't address the fundamental
problem that users encountering this issue have an Ubuntu install which
does not know where their boot disk is. Certainly, at install time
Ubuntu knew, but something has changed afterwards with the system which
causes grub on
Also hit with this problem upgrading from Kubuntu 18.04 to 20.04. I
think this really should be a higher severity bug. LTS releases should
not be encountering problems like this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hit the same problem as Walt Boring, upgrading from 18.04 to 20.04. It
was fixed with the usual live ISO + mount/chroot + grub-install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
I just hit this problem while trying to do a do-release-upgrade from
ubuntu 18.04 to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows:
I also experienced the issue after upgrading from Kubuntu 19.04 to
19.10. I am also using LVM as other posters here. I solved the issue
with the usual boot from live ISO + mount/chroot + grub-install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was able to fix it by booting my cloud provider's rescue image and do
the following:
mount /dev/sdXY /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
grub-install /dev/sdX
update-grub
exit
reboot
Before the upgrade debconf-show grup-pc output (on Ubuntu 19.04) is:
debconf-show grub-pc
grub-pc/install_devices_failed_upgrade: true
grub2/device_map_regenerated:
grub2/unsigned_kernels:
grub-pc/install_devices_empty: false
grub2/kfreebsd_cmdline_default: quiet splash
I've also deployed a new VM from a snapshot where I performed the
upgrade to 19.10. So I can provide information on the system before and
after the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sun, Nov 17, 2019 at 12:26:48PM -, sacharja wrote:
> Have an old VM 19.04 from May: after updating this system & then
> upgrading to 19.10, it will reliably destroy grub. Let me know if you
> need support to debug this, I'm reliably able to reproduce it.
What is the output of 'debconf-show
Update: not related to proprietary drivers (cannot delete/update my own
2 previous posts), even with those deinstalled, the upgrade will fail.
Have an old VM 19.04 from May: after updating this system & then
upgrading to 19.10, it will reliably destroy grub. Let me know if you
need support to
Tested several times from a 19.04 snapshot: as soon as proprietary
drivers are used (in my case virtualbox-guest-dkms-hwe) the upgrade will
fail and leave grub in this crippled state. Also I cannot deinstall
those drivers through a package manager before the upgrade.
But it would be nice if
Seems to be related to the virtualbox guest additions kernel moduls. Was
able to restore grub via
https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot .
Afterwards it was not possible to install the general kernel package.
Only after I removed the virtualbox guest additions hwe I was able
I too had this issue today. My system is relatively simple:
1) I am using LVM
2) I was running 19.04
3) I was using an nvme drive (NOT /dev/sda as it likely expected)
4) To fix it I used the chroot method outlined on the Wiki, running both
'grub-install' and 'grub-update'
System is a brand new,
Got stuck on this today after upgrading from 19.04 -> 19.10. I do dual-
boot Windows. Also Ubuntu is on a 2-disk mdadm RAID array.
- I couldn't get boot-repair-disk to work: It wouldn't recognize the
internet connection. The LXTerminal it comes with was broken too and
didn't respond to keyboard
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
Are the systems getting this set up for dual-booting at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
This has hit me too. Just now rebooting after upgrading from 19.04 to
19.10. I can't remember what version of Ubuntu I first started upgrading
to from this machine but looking at my old live discs it was either
Ubuntu 9.10 or 15.04.
--
You received this bug notification because you are a member
** Tags added: id-5dbb3420627eef18343c849d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
'grub_file_filters' not found."
** Description changed:
After upgrading to 19.10 the boot screen shows the following error:
Error: symbol 'grub_file_filters' not found.
Entering rescue mode...
+ I could fix it after i booted Ubuntu 19.10 live and used the chroot
+ repair method as described here
+
** Also affects: grub2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to
I wish to add this exact same issue (same error, same result) just
struck me after attempting to upgrade to 19.10.
I have downloaded the "boot repair disk" ISO from Sourceforge as
recommended on another Ubuntu forum, but am wondering if I should use it
or the Ubu Live/boot disk?
--
You received
This does not appear to be a new issue; but it is newly visible due to
the changes in 2.04: we've now upgraded to a new major release of GRUB,
and the modules are now no longer compatible with previous releases.
In other words, if you're running into this issue, your system was most
likely
Had same issue.
Kubuntu 19.04 VM running on Virtualbox Version 6.0.14 r133895, upgraded
via instructions on
https://help.ubuntu.com/community/CosmicUpgrades/Kubuntu as of
28/10/2019
SATA controller with dynamically allocated .vdi file set as storage, non
encrypted.
--
You received this bug
Did the dist upgrade from 19.04 to 19.10 and have exactly the same issue
error: symbol: 'grub_file_filters' not found
Entering rescue mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
I too had this problem. Same error message in the grub prompt.
I had to burn a live-cd, and boot from it. Reapairing grub from live-
system didn't work, it "failed to get canonical path of /cow". So I
reinstalled the whole System while keeping all my settings, files, stuff
in /home, and so on
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
'grub_file_filters' not found."
To manage
Same problem. Have been trying to fix this all day. Upgraded 19.04 tó 19.10 it
failed and enters grub rescue with grub_file_filters not found. Boot-Repair did
not help.
/dev/sda1 is my boot (Ext4 512 MB)
/dev/sda2 Partition 2 extended partition 240 GB
/dev/sda5 Partition 5 240 GB LUKS
I gave up trying to fix this, and instead I did a new install of 19.10 from DVD
My system works now, but I wish I had been able to do the upgrade from 19.04
like
I did with my other Linux machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
Same problem here while upgrading from 19.04 to 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
'grub_file_filters'
I my case same problem when upgrading from 19.04 to 19.10 on VirtualBox
VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
I was also affected by this problem after upgrading from 19.04 to 19.10.
I fixed it by using boot-repair, and have the log file it produced. I
can provide it, if it will provide any assistance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I should add, I upgraded from 19.04. My system was originally installed
with 13.10 and has been continuously upgraded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading
I should add, I upgraded from 19.04. My system was originally installed
with 13.10 and has been continuously upgraded.
--
Mit freundlichen Grüßen, Alexander Nolis -- Alexander Nolis Uerdinger Str.
788 47800 Krefeld Tel: +49 (0)2151 9495676
--
You received this bug notification because you are a
I'm also affected. (But I upgraded from 18.04 to 19.04 to 19.10)
dc7ia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
In live cd, I managed to mount /boot, and nm'ed all
/boot/grub/i386-pc/*.mod files
The following files contain "U grub_file_filters":
gzio.mod
lzopio.mod
offsetio.mod
verifiers.mod
xzio.mod
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I just upgraded from 19.04 to 19.10 and am also affected by this bug.
Right now trying to get the box back. The error message is indeed
'grub_file_filters not found'. This happens at the rescue prompt with
'insmod normal' as well.
--
You received this bug notification because you are a member
Yes, i am sure. I don't think i have done anything to the bootloader,
how can i check it? I found the following, if this helps:
$ sudo grep -r grub_file_filters /boot/
Binary file /boot/grub/i386-pc/offsetio.mod matches
Binary file /boot/grub/i386-pc/gzio.mod matches
Binary file
Thank you for the bug report. Are you sure of the spelling of the
symbol name, 'grub_file_filters'? There is no symbol by this name
anywhere in the grub source code. Have you previously done anything to
the bootloader on your system that would have involved installing an
out-of-tree grub module
42 matches
Mail list logo
