Error when trying to remove duplicate grub entries

I received this error when using ujust regenerate-grub or ujust configure-grub:
Generating grub configuration file ...
mount: /var/lib/os-prober/mount: fsconfig system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Generating grub configuration file ...
mount: /var/lib/os-prober/mount: fsconfig system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Any ways to solve this issue?
6 Replies
HikariKnight
HikariKnight5mo ago
cannot replicate, will need sudo dmesg | fpaste after you get the error since all you provided us is "there was an error, run dmesg to see more info"
Parmethyst
Parmethyst4mo ago
Hi, I managed to came across this issue on my end as well on my Legion Go
deck@le-go:~$ ujust regenerate-grub
Generating grub configuration file ...
mount: /var/lib/os-prober/mount: fsconfig system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
deck@le-go:~$ ujust regenerate-grub
Generating grub configuration file ...
mount: /var/lib/os-prober/mount: fsconfig system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Here's my dmesg https://paste.centos.org/view/2b8118db If it helps this install started on Fedora 39 version of Bazzite, the following being rpm-ostree status output
deck@le-go:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
Version: 41.20241104 (2024-11-04T05:01:16Z)
LayeredPackages: sunshine zerotier-one

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
Version: 41.20241104 (2024-11-04T05:01:16Z)
LayeredPackages: sunshine

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7552ff702817c06e3c84f6177985b44013b578e57fbe193c19fca823de5dfadd
Version: 40.20240914.0 (2024-09-15T21:07:53Z)
Pinned: yes

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:8aa518ddc217a916ff1524621254462a4e45645853ffd235cbeb63bb9e76c990
Version: 39.20240406.0 (2024-04-07T01:31:36Z)
LayeredPackages: sunshine zerotier-one
Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'
Pinned: yes
deck@le-go:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
Version: 41.20241104 (2024-11-04T05:01:16Z)
LayeredPackages: sunshine zerotier-one

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
Version: 41.20241104 (2024-11-04T05:01:16Z)
LayeredPackages: sunshine

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:7552ff702817c06e3c84f6177985b44013b578e57fbe193c19fca823de5dfadd
Version: 40.20240914.0 (2024-09-15T21:07:53Z)
Pinned: yes

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:8aa518ddc217a916ff1524621254462a4e45645853ffd235cbeb63bb9e76c990
Version: 39.20240406.0 (2024-04-07T01:31:36Z)
LayeredPackages: sunshine zerotier-one
Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'
Pinned: yes
Parmethyst
Parmethyst4mo ago
In case if it's a partition related issue due to dualbooting, here's my partition setup, I also have an SD Card inserted on my Legion Go
No description
Parmethyst
Parmethyst4mo ago
in case anyone stumbled upon this, disregard the unrelated image at the bottom
No description
HikariKnight
HikariKnight4mo ago
try
sudo touch /boot/grub2/.grub2-blscfg-supported
ujust regenerate-grub
sudo touch /boot/grub2/.grub2-blscfg-supported
ujust regenerate-grub
instead the grub2-switch-to-blscfg command we are using is having some trouble the os-prober error however i think you can ignore also /boot is always mounted
Parmethyst
Parmethyst4mo ago
Ok, will try, thanks! Confirmed that grub regenerated properly 👍

Did you find this page helpful?