You are not logged in.

#1 2013-01-30 09:55:29

MitchellSalad
Member
Registered: 2012-12-25
Posts: 13

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.

uname -m

x86_64

Partitions:

Device      Type               Name
/dev/sda1   Linux filesystem   root
/dev/sda2   Linux filesystem   boot
/dev/sda3   EFI System         efi
/dev/sda4   Linux filesystem   var
/dev/sda5   Linux filesystem   home

lsblk

Name   Type   Mountpoint
sda    disk
sda1   part   /
sda2   part   /boot
sda3   part   /boot/efi
sda4   part   /var
sda5   part   /home

Directory tree:

/boot/
   efi/
      EFI/
         arch/
            initramfs-arch-fallback.img
            initramfs-arch.img
            refind_linux.conf
            vmlinux-arch.efi
         refind/
            icons/
            refind.conf
            refind_x64.efi
   initramfs-linux-fallback.img
   initramfs-linux.img
   vmlinuz-linux

/boot/efi/EFI/arch/refind_linux.conf:

"Default boot"          "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal"      "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"

ls -l /dev/disk/by-partuuid/

lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1

efibootmgr -v

BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd)   HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)

Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.

Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.

Thank you very much!

EDIT: Some updates...

I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):

Shell> fs0:
FS0> ls

I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:

Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.

Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.

Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)

Not sure if any of that last but is relevant. Thanks again.

Tried downgrading kernel to 3.6, still won't boot.

Last edited by MitchellSalad (2013-01-30 20:05:10)

Offline

#2 2013-01-30 11:07:30

swordfish
Member
Registered: 2012-01-14
Posts: 160

Re: Arch won't boot after rEFInd update

MitchellSalad wrote:

Partitions:

Device      Type               Name
/dev/sda1   Linux filesystem   root
/dev/sda2   Linux filesystem   boot
/dev/sda3   EFI System         efi
/dev/sda4   Linux filesystem   var
/dev/sda5   Linux filesystem   home

/boot/efi/EFI/arch/refind_linux.conf:

"Default boot"          "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal"      "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"

ls -l /dev/disk/by-partuuid/

lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3

Shouldn't that be sda1? Your root-partition is /dev/sda1.


Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)

Offline

#3 2013-01-30 17:01:46

MitchellSalad
Member
Registered: 2012-12-25
Posts: 13

Re: Arch won't boot after rEFInd update

swordfish wrote:

Shouldn't that be sda1? Your root-partition is /dev/sda1.

Sorry, that was a typo in the OP that's fixed now. The UUID is that of /dev/sda1. Thanks.

Offline

#4 2013-01-30 17:42:15

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: Arch won't boot after rEFInd update

It sounds to me like you've got a damaged filesystem on your ESP and/or damaged NVRAM entries. Some EFI implementations are fussy about the FAT filesystems on their ESPs, so you might try backing it up, creating a fresh FAT32 filesystem with mkdosfs, and then restoring the files. You could also try using your firmware's setup utilities to erase all your NVRAM entries and start fresh, but if you've tweaked your firmware settings to optimize performance or whatnot, it could be a hassle to restore them all. You'd also need to re-create your boot manager entry to launch rEFInd.

Offline

#5 2013-01-30 19:54:11

MitchellSalad
Member
Registered: 2012-12-25
Posts: 13

Re: Arch won't boot after rEFInd update

srs5694 wrote:

you might try backing it up, creating a fresh FAT32 filesystem with mkdosfs, and then restoring the files.

Did that, didn't work. I'm not sure how to erase all my NVRAM entries. What made you think the ESP filesystem was damaged?

Thank you so much!

EDIT: I booted into the UEFI shell and did "dmpstore -d -all"; thought that would wipe my NVRAM. Now I get a black screen, regardless of whether or not I have a live USB in or not. Did I just brick my laptop?

Last edited by MitchellSalad (2013-01-30 20:55:11)

Offline

#6 2013-01-31 00:29:12

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: Arch won't boot after rEFInd update

I thought your filesystem might be damaged because of the bcfg error message to the effect that it couldn't open refind_x64.efi. An inability to read a file sounds like a damaged filesystem, or possibly a damaged hard disk.

As to clearing the NVRAM entries, most firmware implementations have an option in a menu to restore all settings to the default. That will usually do the job. I'd imagine that "dmpstore -d -all", but I wouldn't have recommended you try it, since I don't know what else it might delete. It's conceivable that by doing this you have bricked your computer, but I really can't be sure. Do you see any boot-time messages, like a logo for your manufacturer or a prompt to press a key to get into a setup utility? If so, try pressing whatever key you normally would (Del or a function key, usually) to launch the setup utility and see what you can do from there.

Offline

#7 2013-02-02 03:26:56

MitchellSalad
Member
Registered: 2012-12-25
Posts: 13

Re: Arch won't boot after rEFInd update

Nope, there's absolutely nothing displayed on the screen. The hard drive sees a little action, then nothing. I'm gonna send it into Lenovo (it's under warranty), but not have them wipe my hard drive, so I can resume trying to fix my OS once it's back in a week. Thanks so much for your help.

Offline

Board footer

Powered by FluxBB