After an upgrade to #kernel 6.5.8 I found the following line in the boot log:
MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Here's a quick HowTo prevent this:
su
vi /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT=... mds=full,nosmt
...
:wq
ubdate-grub
exit
Reboot.
Most modern VMs are configured to skip the GRUB bootloader for a seamless experience. However, you might need to access the GRUB menu at times. For example, if you want to switch back to the older kernel or get into recovery mode for resetting the password.
It is certainly also a useful way to test any changes to GRUB before doing so on your production machine too. In this way if for example you’d like to add colour themes to your main machine’s GRUB, test it out first on the VM’s GRUB until you have it like you want it, then apply to your main machine.
See https://itsfoss.com/access-grub-virtual-machine/
#Blog, #GRUB, #linux, #opensource, #technology, #VM
So, does anyone else has the problem/experience/tipps when: - I have a Debian 10 server with Raid 1 - unattended Security update. And EVERY TIME so far when i did the regular updates, and then did a reboot, my GRUB got broken, leading to a non-booting server? (which so far atm im not even able to fix..)
last time the was an official issue.
this time i couldn´t find anything. - i actually thought that i have checked that there is no grub update going on before rebooting, but then it still failed.
i tried to boot debian 11 (unfortunately) and in rescue mode, attaching the array, and installing grub again into both of the boot-drives seperately which altered the boot failure but it still did´t boot. (just recently recognized it was the not the matching debian 10 rescue system...)
apart from the immedeate problem: is there anything i can/need to config for debian to behave corretly on kernel/grub updates if iam using a software-raid?
This post based from Archlinux News Website: https://archlinux.org/news/grub-bootloader-upgrade-and-configuration-incompatibilities/
Grub bootloader upgrade and configuration incompatibilities
2022-08-30 - Christian Hesse
Recent changes in grub added a new command option to fwsetup and changed the way the command is invoked in the generated boot configuration. Depending on your system hardware and setup this could cause an unbootable system due to incompatibilities between the installed bootloader and configuration. After a grub package update it is advised to run both, installation and regeneration of configuration:
grub-install ...
grub-mkconfig -o /boot/grub/grub.cfg
For more specific information on grub-install, please refer to the wiki: GRUB - ArchWiki
:Boring with the poor boot menu appearance? Try the cool #DedSec #GRUB theme. It’s a Grub boot-loader (defaults in most Linux) theme inspired by the fictional hacker group DedSec from Watch Dogs series video game." https://ubuntuhandbook.org/index.php/2022/03/grub-theme-dedsec-watch-dogs/
"The presentation will discuss current state of #GRUB upstream development." https://fosdem.org/2022/schedule/event/grub_status_update/
I still don't get why #Debian #Linux does not do a proper full disk #encryption with /boot and /swap encrypted and #grub with the encryption setup while having #swap so big that it is sufficient for hibernation to disk. Why?
Are you an Ubuntu user? Do you need to edit your bootloader to change something, delete something, or something else? Don’t know how to do it? If so, this guide is for you.
Just bear in mind that edits to the GRUB that go wrong will bork your boot up. No need to panic as you won't lose data, but it will mean some backtracking and work from the terminal to rewrite your GRUB so it boots OK again.
See How to edit the Ubuntu bootloader with a GRUB graphical editor
Are you an Ubuntu user? Do you need to edit your bootloader to change something, delete something, or something else? Don't know how to do it? If so, this
https://gadgeteer.co.za/how-edit-ubuntu-linux-bootloader-grub-graphical-editor
Hab' diese #Nacht mit dem #BIOS eines #HP-Laptops gekämpft.
Alles läuft glatt, aber #grub lässt sich nicht installieren.
Dann muss man wissen, dass beim Start des #BIOS über das Menü die #Enter-Taste fataler Weise nicht funktioniert, beim drücken der F10 alles aber soweit klappert, nur der Eintrag #SecureBoot ausgegraut ist. Also lange und viele #Beschreibungen gelesen und ausprobiert, aber es blieb dabei, grub wollte zum verrecken nicht installiert werden!
Und #Töchtin benötigte heute Morgen das Teil für eine #Präsentation!
Gegen 03:00 Uhr dann ein kleiner englischer Kommentar in irgend einem #Forum für #Dingenskirch und andere unbekannte Sachen:
Auf der Installations-DVD von #LinuxMint ist boot-repair installiert!
Ehm, angeworfen "reparieren" gedrückt und fertig!
Was dieses Programm jetzt gemacht hat weiß ich nicht, #Hauptsache der Rechner tut es wieder.
Bei Gelegenheit muss ich mich da noch einmal drum kümmern!
