You are not logged in.
Pages: 1
Topic closed
Hi, I was in the process of updating my Arch installation with sudo pacman -Syyu and then a lightning struck nearby and tripped my breaker, powering down my house. After the storm have cleared I booted the system, but now I get this message:
error: file `/boot/intramfs-linux.img` not found.
And it doesn't go any further with booting past this. Any ideas how can I fix it all without re-installing Arch?
Offline
Do you have "fallback initramfs" menu entry in bootloader? If yes, boot fallback and rebuild initramfs with
# mkinitcpio -p linux
Offline
Do you have "fallback initramfs" menu entry in bootloader? If yes, boot fallback and rebuild initramfs with
# mkinitcpio -p linux
I do have this option under "Advanced options for Arch Linux", but it boots with the exact same message. I have a USB stick flashed with Arch, can I use it to fix the issue?
Offline
I have a USB stick flashed with Arch, can I use it to fix the issue?
Yes, you can. Boot with USB stick, mount your rootfs, run arch-chroot to mount point of rootfs and rebuild initramfs. It's hard to provide exact commands without knowing your filesystems layout.
Offline
sv-cheats-1 wrote:I have a USB stick flashed with Arch, can I use it to fix the issue?
Yes, you can. Boot with USB stick, mount your rootfs, run arch-chroot to mount point of rootfs and rebuild initramfs. It's hard to provide exact commands without knowing your filesystems layout.
Thank you for a suggestion! Can you please link some Wiki page so that I can figure out what commands to use? I don't know what "roofs" is.
Offline
Yes! It all worked! Here's a step-by-step guide for anyone who encounters the same issue:
1. Get a USB stick with Arch Linux on it
2. Boot into it
3. Run fdisk -l and figure out on what partition you have your linux installation
4. Mount this partition with: mount /dev/path/to/partition /mnt
5. arch-chroot into it: arch-chroot /mnt
6. Rebuild initramfs: mkinitcpio -p linux
Reboot and that's it!
Offline
Glad you were able to solve your issue. It's also very thoughtful to add a step-by-step guide.
Consider marking your thread as [SOLVED] by editing the title.
Offline
I had to take a few extra steps which I want to document here for others having the same problem:
1. Get a USB stick with Arch Linux on it
2. Boot into it
3. Run fdisk -l and figure out on what partition you have your linux installation
3a. Also figure out what your EFI partition's name is.
4. Mount this partition with: mount /dev/path/to/partition /mnt
4.a After mounting your linux partition, mount the EFI partiton: mount /dev/path/to/EFI /mnt/boot
5. arch-chroot into it: arch-chroot /mnt
6. Rebuild initramfs: mkinitcpio -p linux
The additional steps were required for the new initramfs file to be installed properly to the EFI partition.
Also, in my case step 6 (mkinitcpio) failed because of unconsistent kernel versions.
This was easily fixed by running: pacman -S linux.
This installed the proper kernel version and also runs mkinitcpio as post installation hook.
After this, my problems were solved. Hope this may help anyone in the future.
Edit: typo
Last edited by fablb (2024-03-21 14:38:34)
Offline
I had to take a few extra steps which I want to document here for others having the same problem:
1. Get a USB stick with Arch Linux on it
2. Boot into it
3. Run fdisk -l and figure out on what partition you have your linux installation
3a. Also figure out what your EFI partition's name is.
4. Mount this partition with: mount /dev/path/to/partition /mnt
4.a After mounting your linux partition, mount the EFI partiton: mount /dev/path/to/EFI /mnt/boot
5. arch-chroot into it: arch-chroot /mnt
6. Rebuild initramfs: mkinitcpio -p linuxThe additional steps were required for the new initramfs file to be installed properly to the EFI partition.
Also, in my case step 6 (mkinitcpio) failed because of unconsistent kernel versions.
This was easily fixed by running: pacman -S linux.This installed the proper kernel version and also runs mkinitcpio as post installation hook.
After this, my problems were solved. Hope this may help anyone in the future.
Edit: typo
I know this is a late post, but THANKS A LOT because what you wrote was EXACTLY was fixed it for me. A BIG HUG!!
Offline
https://wiki.archlinux.org/title/Genera … bumping%22
Closing this old thread.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1
Topic closed