No Boot after update. Grub File Filters Not Found

Forum Forums General Tips and Tricks No Boot after update. Grub File Filters Not Found

  • This topic has 2 replies, 2 voices, and was last updated Jun 7-12:11 pm by ModdIt.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #36953
    Member
    ModdIt

      Still dealing with a spate of no boot after update error. Grub File Filters Not Found seems
      to be an issue that affects all distros on occasion.

      Getting broken systems up and running priority as kids panicking. Some final exams tomorrow.
      Requested no further updating until I get some idea what went wrong and why.

      After some searching I found following: https://debianforum.de/forum/viewtopic.php?t=174204.
      The post from von Michael1978 » 31.07.2019 21:46:47 was most useful.

      Grub 2 and Rescatux disks failed so moved on to boot with Live Antix.

      Used the AntiX chroot rescue tool to get in to broken system, then mostly followed
      the instructions here: https://debianforum.de/forum/viewtopic.php?t=174204

      In Terminal do #dpkg -l *grub* |grep ii to list your installed grub packages
      ii grub-common 2.04-3mx19+3 amd64 GRand Unified Bootloader (common files)
      ii grub-efi-amd64-bin 2.04-3mx19+3 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
      ii grub-efi-ia32-bin 2.04-3mx19+3 amd64 GRand Unified Bootloader, version 2 (EFI-IA32 modules)
      ii grub-pc 2.04-3mx19+3 amd64 GRand Unified Bootloader, version 2 (PC/BIOS version)
      ii grub-pc-bin 2.04-3mx19+3 amd64 GRand Unified Bootloader, version 2 (PC/BIOS modules)
      ii grub2-common 2.04-3mx19+3 amd64 GRand Unified Bootloader (common files for version 2)
      ii grubcc-antix 0.1.2 all Set Grub menu image – jpg only.
      then do
      apt purge grub*
      and copied the list of files to be removed in to featherpad, and for safety saved to live stick.
      More than just grub will be removed.
      Once you complete the command you will have no boot loader !!!

      #apt install followed by a space separated list of All REMOVED PACKAGES restored broken boot capability.

      This was first ever boot failure after update experience among users in AntiX. No data loss and was able to
      recover systems so “yet another crazy Sunday afternoon”.

      #36955
      Forum Admin
      anticapitalista
        Helpful
        Up
        0
        ::

        Why do you have the MX repo enabled?

        Philosophers have interpreted the world in many ways; the point is to change it.

        antiX with runit - leaner and meaner.

        #36972
        Member
        ModdIt
          Helpful
          Up
          0
          ::

          Hallo Anti, unfortunately I am unable to establish exactly why MX repo was enabled. While users tried to fix
          problems, before I came along, a live MX stick was used on the system. I am guessing the repos were updated/changed
          somehow. As I wrote final exam time is bad when something goes wrong. antix and MX are so good nobody is frightened to upgrade !, in this case caution until after Monday exam might have saved some stress.

          i am not blaming AntiX or anyone, just wanted a solution in forum in case anyone else is hit. Kids also look
          first if I am not on phone.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.