Arch Linux

zapple

Member

Registered: 2017-12-20

Posts: 1

Problems booting from rEFInd

I have an issue with rEFInd, whenever I try to boot into arch I get:

Starting vmlinuz-linux
Using load options 'root=PARTUUID=b7fd7abf-fd62-4305-800e-22d378cd5716 rw add_efi_memmap initrd=/boot/initramfs-linux.img'
Failed to open file: boot\initramfs-linux.img
Trying to load files to higher address
Failed to open file: boot\initramfs-linux.img

I checked online and created a live usb of arch, but when I boot it, it tells me

Unable to add image option measurements: Invalid parameters

, but still boots. I then checked to see if windows boots, it works just fine. I thought that windows may have messed up the PARTUUID so I checked that next, but it was correct.

I found that I might need to regenerate the initramfs-linux.img with

mkinitcpio -p linux

, which returned

==> ERROR: /proc must be mounted!

yet my setup only needs to mount / /home and /boot

So then I tried reinstalling refind with refind-install, which yielded me an error

ShimSource is none
Installing rEFInd on Linux....
df: Warning: cannot read table of mounted file systems: No such file or directory
grep: /etc/mtab: No such file or directory
The ESP doesn't seem to be mounted! Trying to find it....
lsblk: failed to access sysfs directory: /sys/dev/block: No such file or directory
///boot doesn't seem to be on a VFAT filesystem. the ESP must be mounted at //boot or //boot/efi and it must be VFAT! Aborting!
The comptuer appears to be running in BIOS mode and has no ESP. You should create an ESP, and ideally boot in EFI Mode, before installing rEFInd

So I tried using lsblk, which gave me an error

lsblk: failed to access sysfs directory: /sys/dev/block: No such file or directory

to which I listed the contents of /sys/ which was nothing.

I then listed /etc/ and I saw that mtab existed but was labeled mtad@

Then listed /dev/ which only contains a file named null. and listed /proc which is also empty.

My computer is definitely running in UEFI and the ESP is definitely a VFAT filesystem.

I suspect that this has to do with the live usb returning the error on boot, or windows tried accessing Linux and messed something up.