#mkinitcpio — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mkinitcpio, aggregated by home.social.
-
Actualicé mi @archlinux y pasó lo que tenía que pasar:
- comenzó a reiniciarse de forma random.
- actualicé de nuevo: nueva versión del núcleo.
- se apagó, se rompió el grub.
- reinicié con un live.
- no estaba el núcleo compilado en el /boot.
- hice chroot al / de mi instalación.
- reinstalé el núcleo Linux, los firmwares, el grub, su configuración, y creé el ramdisk.
- reinicié y acá está andando.... nada del otro mundo, bah 😅
-
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 -Syyuthe 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 22showedfilteredfrom 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:
- The
encryptsshinitcpio hook referencing a/usr/lib/initcpio/udev/11-dm-initramfs.rulesfile that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway. PermitRootLogin noinsshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd showsclosed, notfiltered.- Predictable interface-naming drift after the systemd 260 upgrade. Patched the
.networkconfig to match by MAC. Useful hardening; not the cause. - Stale GRUB stage1 +
core.imgin the MBR. Arch never re-runsgrub-installafter agrubpackage upgrade. Refreshed it. Still filtered. - Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.
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-journaldcould 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=dhcpon 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:- Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
- New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays
filtered.
Hetzner’s own documentation has been quietly moving away from
ip=dhcptoward 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=dhcpshipped byinstallimageis a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routinepacman -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) — includinghal fix static-ip, which derives the static cmdline directly from your existingsystemd-networkd.networkfile:→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original
#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd/etc/default/grubis backed up to.hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you. - The
-
Deux nouveaux hooks pour #mkinitcpio sur #ArchLinux, suite à la MAJ faite cette nuit : [systemd] et [sd-vconsole]
Conséquence liée ? À l’allumage, ce matin, entre les écrans “Chargement de Linux…” et celui d’ouverture de session, toute la phase de démarrage de systemd se fait… en écran noir complet, à l’aveugle (il n’y a plus la ligne “/dev/sda…”, ni de simple curseur texte “_” gris) ! C’est perturbant, ce changement non sollicité… >__<
-
[arch-dev-public] mkinitcpio v40, packaging changes and kernel-install
https://lists.archlinux.org/archives/list/[email protected]/thread/S2G5NU4YD7OL7TIGLN4GCV2T6F4RUPBJ/
-
Can anyone explain the advantages of using #dracut over #mkinitcpio on #arch #linux ? Assuming there are any of course
-
#DailyStandup (2/2)
Not something I did, but something that happened:
- Friday's #mkinitcpio v39 release means that my #ARM improvements are now in a stable release. #ArchLinuxARM should no longer have to patch mkinitcpio!What I'm doing today:
- Following up with the gotk4 prep PR
- Working through some of the #Parabola packaging backlog.
- Working through some of the Parabola email mailinglist backlogChallenges/blockers:
- Waiting for @amerl to email me some files I'd saved on his laptop -
And we got the draft for the next #mkinitcpio release up.
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/merge_requests/374
-
mkinitcpio hook migration and early microcode
https://archlinux.org/news/mkinitcpio-hook-migration-and-early-microcode/
-
mkinitcpio v37.1 has been released!
A bugfix for the kernel-install setup.
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v37.1
-
mkinitcpio v37 has been released!
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v37
-
Apparently there was an issue on #archlinux in #mkinitcpio package, where due to some races w/ #udev, mkinitcpio failed to discover devices and has generated the #initramfs disk w/ no modules.
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/177
-
My #Manjaro SSD install that currently boots over USB got borked after an update. Turns out it's something funky with #mkinitcpio, had to downgrade to 34.2. Fun stuff. https://forum.manjaro.org/t/system-not-booting-after-update/138827/3
-
Consolidating our mkinitcpio hooks.
https://lists.archlinux.org/archives/list/[email protected]/thread/ML3TS4745DESSGJCABMLUVPNA7MLFD2Y/
-
mkinitcpio v35.1 has been released!
Bugfix release for yesterdays release.
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v35.1
https://lists.archlinux.org/archives/list/[email protected]/thread/BOCF67FPBHKB2AD2ITHEKPXEMYSXAPIY/
-
mkinitcpio v33 has now been released!
The development has now moved to the Arch Linux GitLab instance :)