PC boots into BIOS

[titan]

After DU today machine boots into BIOS , I saw other thread and tried setting/changing boot order but just get  error "grub_file_filters not found"

[charlyheinz]

This is because grub-efi-amd64-bin has been updated during DU.
You have to reinstall grub as it is shown here:
https://forum.siduction.org/index.php?topic=6065.msg49947#msg49947
What I have to do is to mount /sys different:

mount --rbind /sys mnt/where you chroot/sys

otherwiese I get an installation-warning!!

[titan]

I am not duel booting just siduction not using uefi

[hendrikL]

Well, I used a live siduction-iso (mow/giants).
Booted it from a USB-Stick, clicked on the chroot-helper icon and after being root in the chrooted system (the dialog is telling all important things) I ran grub-install and to be sure after it an update-grub!
Rebooted, all is fine again!

[ghstryder]

Dual-Booting w/Windows 10 here.

All it took was:

chroot w/USB
# grub-install
# update-grub

[hendrikL]

So, I run on a second laptop an "apt full-upgrade" (it could also be nala-upgrade or apt dist-upgrade), grub got its upgrade,
After that full-upgrade, I ran "grub-install /dev/sdb" (sdb is my boot disk) and afterwards "update-grub" (I don't know if this is necessary), rebooted, and I do not have any problems so far.

Code Select Expand


apt policy grub-common
grub-common:
  Installed: 2.12~rc1-7
  Candidate: 2.12~rc1-7


[titan]

Thanks, I have tried everything here still get same error, I have had enough I am off down the woods on my bike to chill out.

[hendrikL]

So maybe you should downgrade it, if possible.

http://snapshot.debian.org/package/grub2/2.06-14/#grub2-common_2.06-14

[dibl]

The new chroot-helper is the star of the show, today!  Nice job!

[ghstryder]

The new chroot-helper is the star of the show, today!  Nice job!

You can say that again dibl, thanks Team!

[Teriarch]

As far as I can tell the problem occurs with the update of grub from
version 2.06-13 to version 2.12~rc1-7 on the 4th of September.

Only UEFI (with or w/o Secure Boot) Mode is affected. The developer
changed the lines in file /etc/grub.d/30_uefi-firmware:

if [ "\$grub_platform" = "efi" ]; then
        fwsetup --is-supported
        if [ "\$?" = 0 ]; then
                menuentry '$LABEL' \$menuentry_id_option 'uefi-firmware' {
                        fwsetup
                }
        fi

The offending command
"fwsetup --is-supported"
has no consequence for grubx64.efi in version 2.12 but causes
version 2.06 to enter the bios fw settings (obviously version 2.06
ignores the option "--is-supported" and enters the firmware settings
instead).

In rare circumstances the old grubx64.efi is not replaced by the new one.
Comment the offending line in /etc/grub.d/30_uefi-firmware as a quick fix
and run update-grub in a chroot environment as suggested.

[hendrikL]

One short information to the chroot-helper and  encrypted systems. First you have to open your crypted system before chrooting in to it.
So you have to do it by hand, sorry.

[bevo]

@ Teriarch: Bingo great job, thank you !!

[Jeef]

One short information to the chroot-helper and  encrypted systems. First you have to open your crypted system before chrooting in to it.
So you have to do it by hand, sorry.

Did you decrypt via cli or from another method. I've been trying luksopen the running chroot-helper but get prompted drive is already in use. Might need to chroot manually

[titan]

I gave up with my original install, and did a clean install, with new ssd of latest siduction but after du it has same problem but Teriarch's solution fixed it