[SOLVED] rEfInd Started Hanging on Boot

Question

I have my computer set up to dual boot Arch and Windows 8 using EFISTUB and rEFIfind as described in the beginners' guide. This had been functioning well for the last month or two but this morning I found that the computer would just hang after printing out:
Starting vmlinuz-arch.efi
Using load options 'root=/dev/sda7 ro rootfstype=ext4 systemd.unit=graphical.target'
The only thing that I've done since my last Arch boot is to install and run DiskInternals Linux Reader 1.6.4.0 on my Windows partition. I needed to grab a file from the Arch ext4 root partition and didn't think that a read operation could result in any corruption. I can still run this program in Windows and everything appears to be in order on the ext4 partition so I'm not entirely sure if this is related.
I did forget to set up systemd to copy over '/boot/vmlinuz-linux', '/boot/initramfs-linux.img', and '/boot/initramfs-linux-fallback.img' to the efi partition when they change which I thought might have caused this problem. I did this manually from Windows however and it had no impact on the behavior. If anybody could point me in the right direction here I would really appreciate it.
My refind_linux.conf contents are the following:
"Boot to X" "root=/dev/sda7 ro rootfstype=ext4 systemd.unit=graphical.target"
"Boot to console" "root=/dev/sda7 ro rootfstype=ext4 systemd.unit=multi-user.target"
Last edited by neon (2013-02-21 21:49:56)

Answer 1

neon wrote:
Last night I updated all of the packages on my system and this issue returned. I tried doing the fsck again (it said it was clean) but it made no difference. I also tried copying the necessary files from /boot to the EFI partition by hand and this all made no difference. When I updated the system the kernel was updated to 3.7.9-1.
Anybody have any other ideas for what I could try?
Try reverting to kernel 3.7.7. There are some as-yet-mysterious glitches involving booting via EFI with Arch kernels 3.7.8, 3.7.9, and possibly some other releases of the 3.7.x series. The EFI problem doesn't seem to affect Arch kernel 3.7.7, though.
If you want to read about the problems -- and possibly get further confused! -- you could take a look at this thread.
Either way, I don't believe your problem is related to filesystem errors, which is what fsck addresses.
Last edited by dhave (2013-02-21 19:01:27)