Because I've had it happen on two machines. The first one I noticed was originally installed a Neptune OS https://distrowatch.com/?newsid=11892 install from Summer 2023 that I upgraded to Debian testing/trixie & removed the Neptune packages & repos at some point. I'm not concerned about that one, more fool me for installing some Debian-based variant that apparently has abominations like grub-customizer installed on it. Derivative distros are just asking for trouble, especially upgrading.
But the second installation is a pretty bog-standard Debian stable installation, albeit originally installed a longish time ago.
Old, but it is a trusty install, updated to current stable (bookworm) over the years, & I'm sure I have customized its grub plenty of times by editing /etc/default/grub. (I even have a bash alias to edit that file with vim since it is something I do often enough.) This time I went to edit the file and it was missing!
Grub was working well enough, it keeps booting the luks-encrypted system and updating the kernels. And the install never had the grub-customizer package installed on it. The OS seems to have a fairly normal assortment of grub packages installed:
That is the same assortment that is on my local Debian stable server that does have /etc/default/grub intact.
I copied the /etc/default/grub over from my server and executed "update-grub" and the operating system is now using the new file, I was able to enable & disable os-prober by editing the copied /etc/default/grub.
Has anyone seen this weirdness before?
But the second installation is a pretty bog-standard Debian stable installation, albeit originally installed a longish time ago.
cat /var/log/installer/lsb-release DISTRIB_ID=DebianDISTRIB_DESCRIPTION="Debian GNU/Linux installer"DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u1"X_INSTALLATION_MEDIUM=cdrom
Old, but it is a trusty install, updated to current stable (bookworm) over the years, & I'm sure I have customized its grub plenty of times by editing /etc/default/grub. (I even have a bash alias to edit that file with vim since it is something I do often enough.) This time I went to edit the file and it was missing!
Grub was working well enough, it keeps booting the luks-encrypted system and updating the kernels. And the install never had the grub-customizer package installed on it. The OS seems to have a fairly normal assortment of grub packages installed:
dpkg -l | grep grubii grub-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files)ii grub-efi 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (dummy package)ii grub-efi-amd64 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version)ii grub-efi-amd64-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules)ii grub-efi-amd64-signed 1+2.06+13+deb12u1 amd64 GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian)ii grub2-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files for version 2)ii grub2-splashimages 1.0.1+nmu2 all a collection of great GRUB2 splashimages
That is the same assortment that is on my local Debian stable server that does have /etc/default/grub intact.
I copied the /etc/default/grub over from my server and executed "update-grub" and the operating system is now using the new file, I was able to enable & disable os-prober by editing the copied /etc/default/grub.
Warning: os-prober will be executed to detect other bootable partitions.Warning: os-prober will not be executed to detect other bootable partitions.
Has anyone seen this weirdness before?
Statistics: Posted by Praxis — 2024-11-27 00:19 — Replies 1 — Views 46