[Solved] Can't boot any OS after refind update

Recoba20 · 2013-08-11 02:03:52

I've updated refind to 0.7.3 version, then manualy copied files to boot partition (as it says in instructions after refind update, including refind.conf-sample to refind.conf). After computer restart I can't boot any OS. (I have a dual boot Win7 64bit and ArchLinux.) When I switch on my computer, it shows me post screen, then refind screen with an option to choose OS I want to boot, but when I select any of them, it simply hangs.
When I choose Arch to boot, I get this information.

Starting vmlinuz-arch.efi
Using load options 'root=/dev/sdd3 ro rootfstype=ext4 systemd.unit=graphical.target initrd=\EFI\arch\initramfs-arch.img'

It hangs with the message above.

Same happends when booting Win7, but different message shows.

Any idea how to fix this problem?

Last edited by Recoba20 (2013-08-12 23:24:52)

cfr · 2013-08-11 02:27:06

Where is vmlinux-arch.efi? Is it up to date i.e. did you copy it following any recent kernel upgrade? Ditto the initramfs. Was the new version copied to \EFI\arch\initramfs-arch.img?

What "different message shows"?!

Recoba20 · 2013-08-11 10:56:18

Yes. I've done that before. After every kernel update, I copy vmlinuz-linux, initramfs-linux.img and initramfs-linux-fallback.img to /boot/efi/EFI/arch/ folder.

But, in that case, when I forget to copy files to boot partition, it starts to boot, and it hangs later during boot. Also, I can boot windows, but this time, after refind update I can't boot any OS. It hangs at start at both situations.

After every refind update I copy refind_64.efi, refind.conf-sample (to refind.conf), icons and drivers to my boot partition. Since now, there was no problem with refind update.

EDIT:
When I try to boot Windows, I get this message

Starting bootmgfw.efi
Using load options ' '

Meanwhile, I copied again all necessary files from /usr/share/refind to appropriate places in /boot partition. Also, I've changed refind_linux.conf file. Changed from /dev/sdd3 to PARTUUID, according to fstab settings. Problem is still here. Can't boot any OS from rEFInd menu.

Last edited by Recoba20 (2013-08-11 12:48:10)

cfr · 2013-08-11 15:51:37

Is that what you usually see for Windows? That is, the message for Arch looks fairly normal - though only you can be sure of that, of course - but I have no idea about Windows. If that's not normal, you may be looking at two distinct problems.

In the case of Arch, you *might* be being bitten by the EFI stub loader bug. But that wouldn't affect Windows.

It should be refind_x64.efi. Is that what you meant?

Can you post lsblk -f, refind_linux.conf and the output of ls -R <path-to-ESP>?

Recoba20 · 2013-08-11 16:16:33

Yes, I usually see that message (when I choose windows to boot), but it disappears very quickly and it starts to boot OS. (Now, after refind update to 0.7.3-1, I can't boot any OS.)
I have an Asus motherboard (M5A97 Pro) and in boot options I have an option to boot windows. So, now I'm using windows boot manager instead of refind. Since I can't boot Arch anymore, I use Slax live CD as rescue disk to access linux partitions.
Yes, you're right. It's a refind_x64.efi, not refind_64.efi (Sorry for typo.)
I'll post outputs of commands in a few minutes later. (I'm wrighting this from windows, so I need to boot Slax CD.)

root@slax:~# lsblk -f
NAME   FSTYPE   LABEL   UUID                                 MOUNTPOINT
sda                                                          
├─sda1 vfat             7ED4-8595                            
├─sda2                                                       
└─sda3 ntfs             14A4ED2AA4ED0F54                     
sdb                                                          
├─sdb2                                                       
└─sdb5 ntfs             DBA830D63239F7A2                     
sdc                                                          
├─sdc1                                                       
└─sdc5 ntfs             01CBA1E200F8D760                     
sdd                                                          
├─sdd1 swap             79ee33cf-d818-4ed9-99f8-b6d0a5cd4b68 
├─sdd2 ext4             33030b5a-4693-40c7-a3da-785c5fc300e7 
├─sdd3 ext4             1941af2e-4604-41d5-9e1e-c774f47481d3 
└─sdd4 ext4             c52c7a2f-0de5-4991-85b9-1a97653ecde8 
sr0    iso9660  Slax_CD                                      /mnt/live/memory/data
loop0  squashfs                                              /mnt/live/memory/bundles/01-core.sb
loop1  squashfs                                              /mnt/live/memory/bundles/02-xorg.sb
loop2  squashfs                                              /mnt/live/memory/bundles/03-kdeps.sb
loop3  squashfs                                              /mnt/live/memory/bundles/04-kde.sb
loop4  squashfs                                              /mnt/live/memory/bundles/05-kapps.sb
loop5  squashfs                                              /mnt/live/memory/bundles/06-devel.sb
loop6  squashfs                                              /mnt/live/memory/bundles/07-ffox.sb
zram0  swap             82bc08c4-302d-4340-b4dc-a38f394b3178 [SWAP]
root@slax:~#

root@slax:~/boot/EFI/refind# cat refind.conf
#
# refind.conf
# Configuration file for the rEFInd boot menu
#

# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
#
timeout 20

# Screen saver timeout; the screen blanks after the specified number of
# seconds with no keyboard input. The screen returns after most keypresses
# (unfortunately, not including modifier keys such as Shift, Control, Alt,
# or Option). The default is 0, which disables the screen saver.
#screensaver 300

# Hide user interface elements for personal preference or to increase
# security:
#  banner      - the rEFInd title banner (built-in or loaded via "banner")
#  label       - boot option text label in the menu
#  singleuser  - remove the submenu options to boot Mac OS X in single-user
#                or verbose modes; affects ONLY MacOS X
#  safemode    - remove the submenu option to boot Mac OS X in "safe mode"
#  hwtest      - the submenu option to run Apple's hardware test
#  arrows      - scroll arrows on the OS selection tag line
#  hints       - brief command summary in the menu
#  editor      - the options editor (+, F2, or Insert on boot options menu)
#  all         - all of the above
# Default is none of these (all elements active)
#
#hideui singleuser
#hideui all

# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#
#icons_dir myicons

# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#
#banner hostname.bmp
#banner mybanner.png

# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
#
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#
#selection_big   selection-big.bmp
#selection_small selection-small.bmp

# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#
#font myfont.png

# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#
#textonly

# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#
#textmode 2

# Set the screen's video resolution. Pass this option either:
#  * two values, corresponding to the X and Y resolutions
#  * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
resolution 1024 768
#resolution 3

# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
#   osx     - Mac OS X
#   linux   - A Linux kernel with EFI stub loader
#   elilo   - The ELILO boot loader
#   grub    - The GRUB (Legacy or 2) boot loader
#   windows - Microsoft Windows
# Default value: osx
#
#use_graphics_for osx,linux

# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
#  shell           - the EFI shell (requires external program; see rEFInd
#                    documentation for details)
#  gptsync         - the (dangerous) gptsync.efi utility (requires external
#                    program; see rEFInd documentation for details)
#  apple_recovery  - boots the Apple Recovery HD partition, if present
#  mok_tool        - makes available the Machine Owner Key (MOK) maintenance
#                    tool, MokManager.efi, used on Secure Boot systems
#  about           - an "about this program" option
#  exit            - a tag to exit from rEFInd
#  shutdown        - shuts down the computer (a bug causes this to reboot
#                    EFI systems)
#  reboot          - a tag to reboot the computer
#  firmware        - a tag to reboot the computer into the firmware's
#                    user interface (ignored on older computers)
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot,firmware
#
#showtools shell, mok_tool, about, reboot, exit, firmware

# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#
#scan_driver_dirs EFI/tools/drivers,drivers

# Which types of boot loaders to search, and in what order to display them:
#  internal      - internal EFI disk-based boot loaders
#  external      - external EFI disk-based boot loaders
#  optical       - EFI optical discs (CD, DVD, etc.)
#  hdbios        - BIOS disk-based boot loaders
#  biosexternal  - BIOS external boot loaders (USB, eSATA, etc.)
#  cd            - BIOS optical-disc boot loaders
#  manual        - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#
#scanfor internal,external,optical,manual

# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#
#scan_delay 5

# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#
#also_scan_dirs boot,ESP2:EFI/linux/kernels

# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#
#dont_scan_volumes "Recovery HD"

# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell

# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,PreLoader.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#
#dont_scan_files shim.efi,MokManager.efi

# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
#
scan_all_linux_kernels

# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#
#max_tags 0

# Set the default menu selection.  The available arguments match the
# keyboard accelerators available within rEFInd.  You may select the
# default loader using:
#  - A digit between 1 and 9, in which case the Nth loader in the menu
#    will be the default. 
#  - Any substring that corresponds to a portion of the loader's title
#    (usually the OS's name or boot loader's path).
#
#default_selection 1

# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#
#include manual.conf

# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
#
#  volume    - identifies the filesystem from which subsequent files
#              are loaded. You can specify the volume by label or by
#              a number followed by a colon (as in "0:" for the first
#              filesystem or "1:" for the second).
#  loader    - identifies the boot loader file
#  initrd    - Specifies an initial RAM disk file
#  icon      - specifies a custom boot loader icon
#  ostype    - OS type code to determine boot options available by
#              pressing Insert. Valid values are "MacOS", "Linux",
#              "Windows", and "XOM". Case-sensitive.
#  graphics  - set to "on" to enable graphics-mode boot (useful
#              mainly for MacOS) or "off" for text-mode boot.
#              Default is auto-detected from loader filename.
#  options   - sets options to be passed to the boot loader; use
#              quotes if more than one option should be passed or
#              if any options use characters that might be changed
#              by rEFInd parsing procedures (=, /, #, or tab).
#  disabled  - use alone or set to "yes" to disable this entry.
#
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.

# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.

# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
        icon EFI/refind/icons/os_linux.icns
        volume KERNELS
        loader bzImage-3.3.0-rc7
        initrd initrd-3.3.0.img
        options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
        disabled
}

# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
        loader /EFI/ubuntu/grubx64.efi
        icon /EFI/refined/icons/os_linux.icns
        disabled
}

# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
        loader \EFI\elilo\elilo.efi
        disabled
}

# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
        loader \EFI\Microsoft\Boot\bootmgfw.efi
        disabled
}

# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
        icon \EFI\refind\icons\os_win.icns
        loader \EFI\tools\shell.efi
        options "fs0:\EFI\tools\launch_windows.nsh"
        disabled
}

# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
        icon \EFI\refind\icons\os_mac.icns
        volume "OS X boot"
        loader \System\Library\CoreServices\boot.efi
        disabled
}
root@slax:~/boot/EFI/refind#

root@slax:~/boot/EFI/arch# cat refind_linux.conf
## This file should be present in the same directory as the EFISTUB kernel and initramfs files
## More info at http://www.rodsbooks.com/refind/linux.html , http://www.rodsbooks.com/efi-bootloaders/efistub.html

"Boot with defaults"    "root=/dev/sdd3 rootfstype=ext4 ro"
"Boot to terminal"      "root=/dev/sdd3 rootfstype=ext4 ro systemd.unit=multi-user.target"
root@slax:~/boot/EFI/arch#

root@slax:~# ls -R boot
boot:
EFI

boot/EFI:
Microsoft  arch  refind  tools

boot/EFI/Microsoft:
Boot

boot/EFI/Microsoft/Boot:
BCD       BCD.LOG2      bootmgfw.efi  da-DK  en-US  fr-FR  ja-JP        nb-NO  pt-BR  sv-SE  zh-HK
BCD.LOG   BOOTSTAT.DAT  bootmgr.efi   de-DE  es-ES  hu-HU  ko-KR        nl-NL  pt-PT  tr-TR  zh-TW
BCD.LOG1  Fonts         cs-CZ         el-GR  fi-FI  it-IT  memtest.efi  pl-PL  ru-RU  zh-CN

boot/EFI/Microsoft/Boot/Fonts:
chs_boot.ttf  cht_boot.ttf  jpn_boot.ttf  kor_boot.ttf  wgl4_boot.ttf

boot/EFI/Microsoft/Boot/cs-CZ:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/da-DK:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/de-DE:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/el-GR:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/en-US:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

boot/EFI/Microsoft/Boot/es-ES:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/fi-FI:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/fr-FR:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/hu-HU:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/it-IT:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/ja-JP:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/ko-KR:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/nb-NO:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/nl-NL:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/pl-PL:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/pt-BR:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/pt-PT:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/ru-RU:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/sv-SE:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/tr-TR:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/zh-CN:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/zh-HK:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/Microsoft/Boot/zh-TW:
bootmgfw.efi.mui  bootmgr.efi.mui

boot/EFI/arch:
initramfs-arch-fallback.img  refind_linux.conf   vmlinuz-arch.efi
initramfs-arch.img           refind_linux.conf~

boot/EFI/refind:
icons  refind.conf  refind.conf~  refind_x64.efi

boot/EFI/refind/icons:
arrow_left.icns     os_debian.icns       os_linux.icns      os_ubuntu.icns
arrow_right.icns    os_ecomstation.icns  os_linuxmint.icns  os_unknown.icns
boot_linux.icns     os_fatdog.icns       os_lubuntu.icns    os_win.icns
boot_win.icns       os_fedora.icns       os_mac.icns        tool_apple_rescue.icns
func_about.icns     os_freebsd.icns      os_mandriva.icns   tool_mok_tool.icns
func_exit.icns      os_freedos.icns      os_netbsd.icns     tool_part.icns
func_firmware.icns  os_funtoo.icns       os_openbsd.icns    tool_shell.icns
func_reset.icns     os_gentoo.icns       os_opensuse.icns   transparent.icns
func_shutdown.icns  os_gummiboot.icns    os_redhat.icns     vol_external.icns
os_altlinux.icns    os_haiku.icns        os_refind.icns     vol_internal.icns
os_arch.icns        os_hwtest.icns       os_refit.icns      vol_optical.icns
os_centos.icns      os_kubuntu.icns      os_slackware.icns
os_chrome.icns      os_legacy.icns       os_suse.icns

boot/EFI/tools:
drivers  gptsync_x64.efi

boot/EFI/tools/drivers:
btrfs_x64.efi  ext2_x64.efi  ext4_x64.efi  hfs_x64.efi  iso9660_x64.efi  reiserfs_x64.efi
root@slax:~#

Last edited by Recoba20 (2013-08-11 16:46:09)

cfr · 2013-08-11 19:13:14

I doubt this is the real problem but if you are going to copy rEFInd's drivers to the ESP, you either should put them in \EFI\refind\drivers or \EFI\refind\drivers_x64 (i.e. put the subdirectory where everything else for rEFInd lives) or you need to edit refind.conf appropriately. rEFInd won't look in \EFI\tools\drivers by default

I'm not quite sure where you are mounting things usually because lsblk is obviously just showing stuff when slax is loaded. Can you post fstab or explain where you mount things for Arch?

I definitely think with that many disks using UUID or PARTUUID in refind_linux.conf is the way to go. You just can't count on it always being sdd.

Also, you will want to change 'ro' to 'rw' if you use the fsck hook in mkinitcpio.conf. (But don't change it if you don't use that hook.) But that certainly won't harm anything much.

Also assuming you are booting in EFI mode, can you do

modprobe efivars
efibootmgr -v

and post the output?

Recoba20 · 2013-08-11 21:05:49

I've moved folder drivers to refind folder, but then, after restart it didn't display refind menu to chose which OS I want to boot. It shows post screen, and then cursor and it hangs. Nothing happends later. I've moved back drivers folder to tools folder, and it boots to refind menu to choose OS I want to boot, but it can't boot any OS.

# 
# /etc/fstab: static file system information
#
# <file system>					<dir>		<type>		<options>			<dump>	<pass>
# /dev/sdd3
UUID=1941af2e-4604-41d5-9e1e-c774f47481d3	/         	ext4      	rw,relatime,data=ordered	0	1

# /dev/sdd4
UUID=c52c7a2f-0de5-4991-85b9-1a97653ecde8	/home     	ext4      	rw,relatime,data=ordered	0	2

# /dev/sdd2
UUID=33030b5a-4693-40c7-a3da-785c5fc300e7	/var      	ext4      	rw,relatime,data=ordered	0	2

# /dev/sda1
UUID=7ED4-8595      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/sdd1
UUID=79ee33cf-d818-4ed9-99f8-b6d0a5cd4b68	none      	swap      	defaults			0	0

# /dev/sda3
UUID=14A4ED2AA4ED0F54				/windows/win_c	ntfs-3g		gid=users,umask=0022		0	0

# /dev/sdb5
UUID=DBA830D63239F7A2				/windows/win_d	ntfs-3g		gid=users,umask=0022		0	0

# /dev/sdc5
UUID=01CBA1E200F8D760				/windows/win_e	ntfs-3g		gid=users,umask=0022		0	0

Unfortunately I can't boot Slax in UEFI mode (there's no option to boot in UEFI mode), and efibootmgr -v gives "command not found".

cfr · 2013-08-11 23:16:35

OK. That makes no sense to me at all. You don't even need those drivers to boot because both Windows and Arch have their files on your ESP. And even if you did need them, it wouldn't stop rEFInd showing a menu - it just might not have very much in it.

Hopefully srs5694 will see this thread and be able to give you some advice. (He is the author of rEFInd and knows more about this stuff than most of the rest of us put together - and then some.) Maybe he will be able to figure out what's going on because I'm clueless. I just can't see how moving the drivers folder would stop rEFInd displaying the menu under any circumstances.

When you did ls -R of your EFI partition, what commands exactly did you issue?
EDIT: I can't figure out how the directories listed map onto their usual place in your Arch file hierarchy. Did you mount your ESP somewhere else?

Last edited by cfr (2013-08-11 23:17:34)

Recoba20 · 2013-08-12 02:23:49

When I boot Slax live CD, ESP isn't mounted. So I've mounted boot partition manually. First I've made new folder and named it boot, then I've used command to mount boot partition to newly created folder.

mkdir boot
mount /dev/sda1 boot
cd boot
ls -R

I've forgot to mention that I, before posting my problem, have tried to modify refind.conf file and I've uncommented line with path to drivers

# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#
scan_driver_dirs EFI/tools/drivers,drivers

With that modification happends the same thing what happends when I've moved driver folder to refind folder. (After post screen, it didn't show me refind menu. It just hangs before that.)

cfr · 2013-08-12 02:45:12

OK. So the listing now makes more sense. What is normally at /boot/efi/EFI is at /boot/EFI, for example.

However, the drivers thing is weird. That makes me think there is something quite odd going on somewhere e.g. that something on another partition is preventing rEFInd from showing the menu because you are not getting a menu in just those cases where rEFInd has the ability to scan non-fat partitions. When it can't scan them because the drivers are in the wrong place and you've not told it where to look, it at least shows the menu.

srs5694 · 2013-08-12 02:54:15

Are you using a version from the Arch repositories? If so, please try both the regular and GNU-EFI binary builds from the rEFInd downloads page. It's conceivable that this is a bug in the Arch build, in which case my binary builds should work. OTOH, if my builds don't work, then this sounds like a new bug in rEFInd. (I did make some changes to the code that launches boot loaders, but I don't see how these changes could be causing the problem you're experiencing.)

Recoba20 · 2013-08-12 23:24:23

I'm writing this from my Arch linux. Finaly it works. Both of you are fantastic. Big thank you for helping me.
I've downloaded variant package (GNU-EFI) from link that srs5694 posted. Then, I've copied files (drivers, tools, refind_x64.efi...) to corresponding folder on my ESP. After that, it finally works.
(Before this, I have used a version from Arch repositories. Also, I'm using default Arch kernel x86_64 from core repo.)
Tomorrow I'll try with binary package from rEFInd page.
Thank you!

cfr · 2013-08-12 23:39:06

If you don't have the issue with the regular binaries from srs5694, then you should consider reporting this as a bug against the Arch package. At least, I think that's the upshot of what srs5694 said above. But you'd want to test the non-GNU-EFI version from srs5694 first because Arch doesn't build against GNU-EFI.

Recoba20 · 2013-08-13 10:39:19

I've tested with regular binaries from rEFInd site. And it boots without any problems. So, I guess, it's a some kind of bug.

srs5694 · 2013-08-13 16:04:14

I agree with cfr that you should report this as a bug in the Arch package. This could be an incompatibility with the compiler version, a bug in the specific version of the Tianocore library that Arch is using, etc. As rEFInd's developer, I'm willing to work with the Arch packagers to figure out what's wrong, but it's mostly something for them to track down.

Arch Linux

#1 2013-08-11 02:03:52

[Solved] Can't boot any OS after refind update

#2 2013-08-11 02:27:06

Re: [Solved] Can't boot any OS after refind update

#3 2013-08-11 10:56:18

Re: [Solved] Can't boot any OS after refind update

#4 2013-08-11 15:51:37

Re: [Solved] Can't boot any OS after refind update

#5 2013-08-11 16:16:33

Re: [Solved] Can't boot any OS after refind update

#6 2013-08-11 19:13:14

Re: [Solved] Can't boot any OS after refind update

#7 2013-08-11 21:05:49

Re: [Solved] Can't boot any OS after refind update

#8 2013-08-11 23:16:35

Re: [Solved] Can't boot any OS after refind update

#9 2013-08-12 02:23:49

Re: [Solved] Can't boot any OS after refind update

#10 2013-08-12 02:45:12

Re: [Solved] Can't boot any OS after refind update

#11 2013-08-12 02:54:15

Re: [Solved] Can't boot any OS after refind update

#12 2013-08-12 23:24:23

Re: [Solved] Can't boot any OS after refind update

#13 2013-08-12 23:39:06

Re: [Solved] Can't boot any OS after refind update

#14 2013-08-13 10:39:19

Re: [Solved] Can't boot any OS after refind update

#15 2013-08-13 16:04:14

Re: [Solved] Can't boot any OS after refind update

Board footer