🐧 Hai installato Linux e non sai cos’è GRUB?
Ho pubblicato una guida semplice e completa per capire dual boot, UEFI, update-grub, ripristino del boot loader e configurazioni con Windows e Batocera 👀
👉 https://incastro.altervista.org/grub-linux-guida-completa-dual-boot-update-grub/
#Linux #GRUB #LinuxMint #Ubuntu #DualBoot #Windows11 #Batocera
@ubuntu i recently tried installing kubuntu resolute with encryption and the installer has an error there:
It uses LUKS2 instead of LUKS1
Grub is by default only compartible with LUKS1
For LUKS2 ist a maunal configuration witch dracut neccecary which can be very annoying
I tried that with the help of deepseek and failed i can upload the german AI chats if someone is interested
Please fix that ubuntu team
==============
When two Hetzner servers died at the same time
On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.
Several hours went into hypotheses that turned out to be wrong:
encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered..network config to match by MAC. Useful hardening; not the cause.core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.
What it almost certainly was
Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:
filtered.Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"
One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.
Why it matters for anyone running this stack
If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.
Tooling
While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:
→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.
So. After deleting and rebuilding my `ESP`partition I don't even know how many times and trying out so many different ways of setting up either #rEFind or #GRUB and messing with the `mkinitcpio.d/linux.preset` files, I finally got my original #Arch partition and new #Artix partition booting.
I could not, for the life of me, figure out how to segregate the Arch and Artix boot loaders and initramfs. But since they appear to be the same, both being Arch under the hood...
Hm, neuerdings reagiert mein PC während der Boot-Phase, einschließlich GRUB, nicht mehr auf die Funkmaus oder Funktastatur.
Erst, wenn der Anmeldebildschirm von Kubuntu auftaucht, funktionieren Maus und Tastatur.
Bin mir nicht bewusst, im BIOS irgendetwas geändert zu haben.
Kennt jemensch das Phänomen?
Kubuntu 25.10
Wie schafft Windows das eigentlich immer wieder, das Grub-Menü, das mir beim Start des PC eigentlich auch die Option Linux zu Booten anbieten soll, so kaltzustellen, dass Windows durchbootet und man vom Grub-Menü gar nichts mehr sieht?
Ich muss dann jedesmal ins UEFI-Setup, manchmal sogar zweimal, um das wieder zu richten. 🤯
Und Nein, kein Windows ist leider keine Option. Vorerst.