- The Refind Binary File Is Missing Aborting Installation .
- The Refind Binary File Is Missing Aborting Installation Management Group
- The Refind Binary File Is Missing Aborting Installation Guide
- See All Results For This Question
- Wikipedia:rEFInd
[ Previous Page | Next Page | Table of Contents ]
Version 3.6.3, May, 2000
Endpoints and Gateways
- If an endpoint is allowed to broadcast for initial login, and the login request can reach multiple gateways in different TMRs, several of the gateways might receive the request and process it. This results in one endpoint logging into multiple TMRs. One login request is honored and the rest will return 'HMAC' errors on downcalls and upcalls. (CMVC-26857)
- APAR-IX80312, IX83059, IX82918: For Windows NT, a Tivoli Remote Access Account (TRAA) or 'password invalid' error is displayed the first time you install an endpoint with InstallShield if a user name is specified in the Remote Access dialog. This error is displayed even if the Administrator account is specified. (CMVC-43621) Workaround: Cancel the installation and log off from the target computer. A certain ratio shack up rar. Log on again and restart the installation. The TRAA account will then be recognized.
- For Windows NT, binary policies do not execute properly on Windows NT endpoint managers and gateways. (CMVC-42284) Workaround: You can invoke the binary in a policy script.
- Aborting a winstlcf installation with the n response at the Continue? prompt generates the following error: (CMVC-44256) Workaround: The message is harmless and can be avoided by responding with a for 'abort' instead of n for 'no.'
- APAR-IX82542, IX82870: When the endpoint is running in console mode (lcfd -s) and an attempt is made to distribute a file package to an endpoint, the endpoint might fail with the following message: (CMVC-42993) Workaround: Run the endpoint as a service, rather than in console mode.
- Installations of NetWare 4.x endpoints with the InstallShield report that the endpoint does not log in, even when it does. (CMVC-44272) Workaround: Disregard the InstallShield message and verify if the endpoint installation directory contains the /dat/1/lcf.dat file. If the file exists, the endpoint logged in successfully. If it does not, refer to the lcfd.log file in the same location for information.
- Sixteen-bit programs (batch files) executed by an endpoint or an application that is a client of an endpoint can fail when the Pathenvironment variable is too long. Most endpoint programs are 32-bit programs and run correctly with any setting of Path. However, problems can arise when a 16-bit program is run and the Pathvalue is greater than the limit supported by Microsoft Windows 3.1. The Microsoft Windows 3.1 command interpreter limits the size of any environment variable string (VAR=VALUE) to 127 characters. With this limitation, a Pathenvironment value cannot exceed 118 characters in length. (CMVC-43537) The endpoint automatically sets the Pathfor processes (lcfd.exe). By default, the endpoint adds the following directories to Pathwhen it starts:
- The path to the endpoint library directory
- The path to the endpoint cache library directory
- The path to the endpoint tools directory
Examples of Tivoli applications and services that invoke 16-bit programs are the following:- Tivoli Software Distribution (configuration program scripts)
- Tivoli Inventory
- Tivoli Task Library (batch files)
When the endpoint executes a sixteen-bit program or batch file, the MS-DOS command interpreter (COMMAND.COM) is invoked to run the program or batch file. If the Pathvalue that is passed to COMMAND.COM is too long, the command interpreter will fail to execute correctly. The endpoint will detect this situation and log a warning to the endpoint log file (lcfd.log) if the endpoint log threshold level is set to level 1 (the default) or higher. The message logged is as follows:Workaround: To avoid this problem, install the endpoint in the Tivoli recommended default location (C:TIVOLILCF). Using this path means that the three values that are added to the endpoint path at startup will not cause the Pathvariable to exceed the 118 character limit.Using a short installation path occasionally is not enough. The endpoint also passes the Windows 3.1 system environment (from AUTOEXEC.BAT) to child processes. This can create problems if the system Pathon the user's computer has been modified to contain additional entries. This can happen when the user has installed other software packages on the system that have updated the Pathin AUTOEXEC.BAT.If a path is too long, perform one of the following actions:- Reinstall the endpoint to a location on the system with a shorter path.
- Edit the AUTOEXEC.BATfile.
- Add the following line:
- Create virtual drives for long directory names in Path as follows:
- Reboot the computer to apply the changes.
- Upgrade Windows 3.1 systems to Microsoft Windows 95 or Microsoft Windows NT. These versions of Windows do not have Pathlimitation problems when running 16-bit programs.
- If you uninstall an endpoint from a NetWare system and fail to remove the LCF.SYS file, a new installation will use the old file and rely on the previous DAT directory location. (CMVC-44108) Workaround: Follow the 'Removing Endpoints' procedure in the TME 10 Framework Planning and Installation Guide.
- When you install some OS/2 endpoints from a mounted drive on a remote computer (OS/2 Software Installer), the installation times out and causes the installation to fail. (CMVC-41705) Onyx 3 keygen crack. Workaround: Copy the directory to the target computer and perform the installation locally.
- The silent InstallShield template provided for NetWare 4.x endpoints is missing information and does not work. (CMVC-42769) Workaround: You can create a new Setup.iss file with the following command:
- The encryption of task data passed between servers and endpoints is disabled. (Task data between servers and managed node clients is still encrypted.) (CMVC-26589)
- The Edit button on the Gateway List dialog is disabled. (CMVC-27074)
- For OS/2, silent install of an OS/2 endpoint locks out the use of the keyboard. (CMVC-24920)
- Upgrades of Version 3.2 UNIX endpoints fail if you do not set the lib_dir variable. Workaround: Install the 3.2 EP. Edit the last.cfg file and add the line:Restart the endpoint and the upgrade is succesfull. (CMVC-88723)
- Gateways on HP-UX managed nodes sometimes fail. This problem occurs when large numbers of endpoints log in and the login_policy script is set to automatically upgrade endpoint software. (CMVC-84043)
- Endpoint tasks, jobs, and methods running on Windows 2000 systems may experience restricted system access due to changes in the default security settings between Windows NT 4.0 and Windows 2000. (CMVC-81288) Workaround: You can overcome this new restriction by adding the tmersrvd account (the Tivoli Unprivileged Operations Account) to the Power Users group for Windows 2000 Professional or to the Server Operators group for Windows 2000 Server. If you are concerned about the possible misuse of the tmersrvd account for interactive logins, you can disable the account.Windows NT and Windows 2000 provide both GUI and CLI utilities for account management. The NET.EXE CLI utility can be invoked from a TMA task to manage the tmersrvd account on multiple endpoints. You must execute this task with administrator privileges to successfully alter groups or accounts.The following examples illustrate group management on Windows NT 4.0 Workstation or Windows 2000 Professional. Substitute NET GROUP for NET LOCALGROUP when dealing with a domain controller. Use NET GROUP HELP (or NET LOCALGROUP HELP) for detailed usage information.To view current group membership, run the following command:To add the tmersrvd account to the Power Users group, run the following command:To remove the tmersrvd account from Power Users group, run the following command:The next examples illustrate user account management on Windows 2000. Use NET HELP USER for detailed usage information.To view current account information for the tmersrvd account, run the following command:To disable interactive logins for the tmersrvd account, run the following command:To enable interactive logins for the tmersrvd account, run the following command:
- After you upgrade a NetWare endpoint using the wadminepep_nameupgrade command, the last line of the LCF.NCF file on the NetWare endpoint may become corrupted. The NCF file works correctly, but a command not found message is displayed. (CMVC-82090)
- The wepep_label command does not work on Version 3.6.1 OS/2 managed nodes in a Version 3.6.3 TMR. Patch 3.6.1-TMF-0064 corrects this problem. (CMVC-83963)
- If an administrator with a user role tries to perform the wepset_label command, the command fails without displaying an error message and returns a zero return code. (CMVC-84172)
- If an administrator with the global senior role runs the wepmgrstop command, that administrator will not be able to run the wepmgrstart command. An error message is displayed stating that the administrator is not authorized to run the command. (CMVC-84402)
Installing rEFInd to the partition mounted at '/' Copied rEFInd binary files Copying sample configuration file as refind.conf; edit this file to configure rEFInd. WARNING: If you have an Advanced Format disk,.DO NOT. attempt to check the bless status with 'bless -info', since this is known to cause disk corruption on some systems!! Installing Security Gateway / Security Management R7720JUMBOHF.Error, Installation of Security Gateway / Security Management R7720JUMBOHF package failed!!! Failed to install package. Aborting Installation Program.
[ Top of Page | Previous Page | Next Page | Table of Contents ] by Roderick W. Smith, [email protected]
Stack Exchange Network. Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. The following localized documents are missing from the Sun Management Center 3.5 Update 1 Software CDs: Japanese Locale: Sun Management Center 3.5 Supplement for Sun Fire, Sun Blade and Netra Systems (SUNWpjasmd 817-5041-11) Korean Locale: Sun Management Center 3.5 Version 3 Release Notes for Sun Fire Midrange Systems (SUNWpkosmd 817-5622).
Originally written: 3/14/2012; last Web page update:1/3/2014, referencing rEFInd 0.7.7
I'm a technical writer and consultant specializing in Linux technologies. This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!
Donate $1.00 | Donate $2.50 | Donate $5.00 | Donate $10.00 | Donate $20.00 | Donate another value |
This page is part of the documentation for the rEFInd boot manager. If a Web search has brought you here, you may want to start at the main page.
Don't be scared by the length of this page! Only portions of this page apply to any given user, and most people can install rEFInd from an RPM or Debian package in a matter of seconds or by using the install.sh script in minute or two.
Once you've obtained a rEFInd binary file, you must install it to your computer's ESP (or conceivably to some other location). The details of how you do this depend on your OS and your computer (UEFI-based PC vs. Macintosh). The upcoming sections provide details. See the Contents sidebar to the left for links to specific installation procedures. For most Linux users, an RPM or Debian package is the best way to go. If your Linux system doesn't support these formats, though, or if you're running OS X, using the install.sh script can be a good way to go. If you're using Windows, you'll have to install manually.
Contents
- Installing rEFInd Using install.sh under Linux or Mac OS X
- Installing rEFInd Manually
- Alternative Naming Options
- Fixing a Macintosh Boot
Installing rEFInd Using an RPM or Debian Package File
Beginning with version 0.6.2, I've included RPM and Debian package files for rEFInd. If you have a working RPM-based or Debian-based Linux installation that boots in EFI mode, using one of these files is likely to be the easiest way to install rEFInd: You need only download the file and issue an appropriate installation command. In some cases, double-clicking the package in your file manager will install it. If that doesn't work, a command like the following will install the RPM on an RPM-based system:
On a Debian-based system, the equivalent command is:
Either command produces output similar to that described for using the install.sh script, so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd.
Since version 0.6.3, the installation script makes an attempt to install rEFInd in a bootable way even if you run the script from a BIOS-mode boot, and therefore the RPM and Debian packages do the same. I cannot guarantee that this will work, though, and even if it does, some of the tricks that install.sh uses might not last for long. You might therefore want to use mvrefind.sh to move your rEFInd installation to another name after you boot Linux for the first time from rEFInd.
Since version 0.6.2-2, my package files have installed the rEFInd binaries to /usr/share/refind-version, the documentation to /usr/share/doc/refind-version, and a few miscellaneous files elsewhere. Upon installation, the package runs the install.sh script to copy the files to the ESP. This enables you to re-install rEFInd after the fact by running install.sh, should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can use install.sh or install manually.
Installing rEFInd Using install.sh under Linux or Mac OS X
If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the install.sh script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, install.sh will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the extra instructions for this utility.
Quick install.sh Instructions
Under Linux, the install.sh script installs rEFInd to your disk's ESP. Under Mac OS X, the script installs rEFInd to your current OS X boot partition by default; but you can install to your ESP instead by passing the script the --esp option, or to a non-boot HFS+ partition by using the --ownhfs devicefile option. Under either OS, you can install to something other than the currently-running OS by using the --root /mountpoint option. (See Table 1 for details.)
Under Linux, install.sh will be most reliable if your ESP is already mounted at /boot or /boot/efi, as described in more detail in the Installing rEFInd Manually Using Linux section. (If you installed Linux in EFI mode, chances are your ESP is properly mounted.) If your ESP is not so mounted, install.sh will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. This precaution isn't necessary under OS X. If you run install.sh from a BIOS/legacy-mode boot, particularly on a computer that also runs Windows, you should be aware that the tricks the script uses to install itself from BIOS mode are rather delicate. You can convert to a more conventional configuration using the mvrefind.sh script.
A sample run under Linux looks something like this:
The output under OS X is a bit different:
In either case, the details of the output differ depending on your existing configuration and how you ran the program. Unless you see an obvious warning or error, you shouldn't be concerned about minor deviations from these examples. If you run into such a situation, or if you want to install in an unusual way, read on.
Extra install.sh Instructions
Imperial guard regiment name generator. Some details that can affect how the script runs include the following:
- If you run the script as an ordinary user, it attempts to acquire root privileges by using the sudo command. This works on Mac OS X and some Linux installations (such as under Ubuntu or if you've added yourself to the sudo users list), but on some Linux installations this will fail. On such systems, you should run install.sh as root.
- Under OS X, you can run the script with a mouse by opening a Terminal session and then dragging-and-dropping the install.sh file to the Terminal window. You'll need to press the Return or Enter key to run the script.
- If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, you must install rEFInd to the ESP, so the --esp option to install.sh is required. I'm still a little bit foggy about what's required to boot the system once this is done; see this forum thread for a discussion of the topic.
- If you're replacing rEFIt with rEFInd on a Mac, there's a chance that install.sh will warn you about the presence of a program called /Library/StartupItems/rEFItBlesser and ask if you want to delete it. This program is designed to keep rEFIt set as the boot manager by automatically re-blessing it if the default boot manager changes. This is obviously undesirable if you install rEFInd as your primary boot manager, so it's generally best to remove this program. If you prefer to keep your options open, you can answer N when install.sh asks if you want to delete rEFItBlesser, and instead manually copy it elsewhere. If you subsequently decide to go back to using rEFIt as your primary boot manager, you can restore rEFItBlesser to its place.
- If you're using OS X and an Advanced Format disk, heed the warning that install.sh displays and do not use bless --info to check your installation status; this combination has been reported to cause disk corruption on some Macs!
- If you intend to boot BIOS-based OSes on a UEFI-based PC, you must edit the refind.conf file's scanfor line to enable the relevant searches. This is not necessary on Macs, though; because of the popularity of dual boots with Windows on Macs, the BIOS/legacy scans are enabled by default on Macs.
- On Linux, install.sh checks the filesystem type of the /boot directory and, if a matching filesystem driver is available, installs it. Note that the '/boot directory' may be on a separate partition or it may be part of your root (/) filesystem, in which case the driver for your root filesystem is installed. This feature is unlikely to work properly from an emergency system, although it might if you have a separate /boot partition and if you mount that partition at /boot in your emergency system, and the ESP at /boot/efi.
- If you run install.sh on Linux and if /boot/refind_linux.conf doesn't already exist, install.sh creates this file and populates it with a few sample entries. If /boot is on a FAT partition (or HFS+ on a Mac), or if it's on an ext2fs, ext3fs, ext4fs, ReiserFS, or HFS+ partition and you install an appropriate driver, the result is that rEFInd will detect your kernel and will probably boot it correctly. Some systems will require manual tweaking to refind_linux.conf, though—for instance, to add dolvm to the boot options on Gentoo systems that use LVM.
In addition to these quirks, you should be aware of some options that install.sh supports to enable you to customize your installation in various ways. The syntax for install.sh is as follows:
The details of the options are summarized in Table 1. Broadly speaking, they come in four classes: installation location options (--esp, --usedefault, and --root), driver options (--nodrivers and --alldrivers), Secure Boot options (--shim and --localkeys), and a user input option (--yes). Using some of these options in unusual conditions can generate warnings and prompts to confirm your actions. In particular, using --shim or --localkeys when you're not booted in Secure Boot mode, or failing to use --shim when you are booted in Secure Boot mode, will generate a query and a request to confirm your installation. Consult the Managing Secure Boot page for more on this topic.
Option | Explanation |
---|---|
--esp | This option tells install.sh to install rEFInd to the ESP of your computer. This option is only useful on OS X; on Linux, installing to the ESP is a practical necessity, so --esp is implicit on Linux. Be aware that some users have reported sluggish boots when installing rEFInd to the ESP on Macs. Installing rEFInd anywhere but the ESP makes little sense on UEFI-based PCs, except for the partial exception of removable boot media, which you can prepare with --usedefault. |
--usedefault device-file | You can install rEFInd to a disk using the default/fallback filename of EFI/BOOT/bootx64.efi (and EFI/BOOT/bootia32.efi, if the 32-bit build is available) using this option. The device-file should be an unmounted ESP, or at least a FAT partition, as in --usedefault /dev/sdc1. Your computer's NVRAM entries will not be modified when installing in this way. The intent is that you can create a bootable USB flash drive or install rEFInd on a computer that tends to 'forget' its NVRAM settings with this option. This option is mutually exclusive with --esp and --root (except for implicit use of --esp on Linux). |
--ownhfs device-file | This option should be used only under OS X. It's used to install rEFInd to an HFS+ volume other than a standard Mac boot volume. The result should be that rEFInd will show up in the Mac's own boot manager. More importantly, suspend-to-RAM operations may work correctly. Note that this option requires an HFS+ volume that is not currently an OS X boot volume. This can be a data volume or a dedicated rEFInd partition. The ESP might also work, if it's converted to use HFS+. |
--root /mount-point | This option is intended to help install rEFInd from a 'live CD' or other emergency system. To use it, you should mount your regular installation at /mount-point, including your /boot directory (if it's separate) at /mount-point/boot and (on Linux) your ESP at that location or at /mount-point/boot/efi. The install.sh script then installs rEFInd to the appropriate location—on Linux, /mount-point/boot/EFI/refind or /mount-point/boot/efi/EFI/refind, depending on where you've mounted your ESP; or on OS X, to /mount-point/EFI/refind. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with either --esp or --usedefault, except for implicit use of --esp on Linux. Note that this option is not needed when doing a dual-boot Linux/OS X installation; just install normally in OS X. |
--nodrivers | Ordinarily install.sh attempts to install the driver required to read /boot on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the --nodrivers option. This option is the default on OS X or when you use --usedefault. |
--alldrivers | When you specify this option, install.sh copies all the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. |
--shim shim-filename or --preloader preloader-filename | If you pass this option to install.sh, the script will copy the specified shim program file to the target directory, copy the MokManager.efi file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as grubx64.efi, and register shim with the firmware. (If you also specify --usedefault, the NVRAM registration is skipped.) When the target file is identified as PreLoader, much the same thing happens, but install.sh copies HashTool.efi instead of MokManager.efi and copies rEFInd as loader.efi rather than as grubx64.efi. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's keys subdirectory under the name refind.cer. Note that I'm not providing a shim binary myself, but you can download one from here. Some distributions also provide their own shim programs, so can point to them—for instance, in /boot/efi/EFI/fedora/shim.efi. |
--localkeys | This option tells install.sh to generate a new Machine Owner Key (MOK), store it in /etc/refind.d/keys as refind_local.*, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the openssl and sbsign binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default. |
--yes | This option causes the script to assume a Y input to every yes/no prompt that can be generated under certain conditions, such as if you specify --shim but install.sh detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package. |
In any event, you should peruse the script's output to ensure that everything looks OK. install.sh displays error messages when it encounters errors, such as if the ESP is mounted read-only or if you run out of disk space. You may need to correct such problems manually and re-run the script. In some cases you may need to fall back on manual installation, which gives you better control over details such as which partition to use for installation.
Installing rEFInd Manually
Sometimes the install.sh script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list. I describe how to do this with Linux, OS X, Windows, and the EFI shell.
Installing rEFInd Manually Using Linux
The Refind Binary File Is Missing Aborting Installation .
On a UEFI-based PC, you'll normally install rEFInd to the ESP, which is usually mounted at /boot/efi. You can verify that this is the case by using the df command:
This example shows that /dev/sda1 is mounted at /boot/efi, which is a typical configuration. (The ESP can be on another disk or partition, but /dev/sda1 is the most common place for an ESP.) If your output shows /boot or / under the Mounted on column, then your ESP isn't mounted. (An exception is if you're mounting the ESP at /boot. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands.) If you get a df: `/boot/efi': No such file or directory error message, then the /boot/efi directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my EFI Boot Loader Installation page.
Assuming the ESP is mounted at /boot/efi, you can install the rEFInd files as follows (you must be root to issue these commands, or precede each of them with sudo):
- Type cp -r refind /boot/efi/EFI/ from the refind-version directory in which the refind directory exists. This copies all the files that rEFInd needs to work. Note that this includes all of rEFInd's drivers. This command also copies the rEFInd binaries as signed by me; if you prefer to re-sign the binaries yourself, you'll have to do so before or during the copy operation, as described on the Managing Secure Boot page.
- Type cd /boot/efi/EFI/refind to change into rEFInd's new directory on the ESP.
- Type rm refind_ia32.efi to remove the IA32 binary if you're using an x86-64 (64-bit) system; or type rm refind_x64.efi to remove the x86-64 binary if you're using an x86 (32-bit) system. (Note that you must keep the version that's the correct bit width for your EFI; if you've installed a 32-bit Linux on a 64-bit PC with a 64-bit EFI, you'd keep refind_x64.efi.
- Optionally, type rm -r drivers_ia32 to remove the x86 drivers from an x86-64 system, or rm -r drivers_x64 to remove the x86-64 drivers from a 32-bit x86 system. You may also want to remove some or all of the drivers for the architecture you are using. If you don't need them, they'll slow down the start process, and worse, if you're using Secure Boot, rEFInd can load just one shim/MOK-signed driver. See the page on drivers for more on this topic.
- Rename the configuration file by typing mv refind.conf-sample refind.conf. Consult the Editing the rEFInd Configuration File page for information on how to adjust your options.
- On a UEFI-based system, type efibootmgr -c -l EFIrefindrefind_x64.efi -L rEFInd to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. Adjust the path to the binary as required if you install somewhere else. You may also need to include additional options if your ESP isn't on /dev/sda1 or if your configuration is otherwise unusual; consult the efibootmgr man page for details. You may need to install this program on some systems; it's a standard part of most distributions' repositories. Also, if you're installing in Secure Boot mode, you must normally register shim.efi rather than the rEFInd binary, and rename refind_x64.efi to grubx64.efi.
- If other boot loaders are already installed, you can use efibootmgr to adjust their boot order. For instance, efibootmgr -o 3,7,2 sets the firmware to try boot loader #3 first, followed by #7, followed by #2. (The program should have displayed a list of boot loaders when you added yours in the preceding step.) Place rEFInd's number first to set it as the default boot program.
Note the use of doubled-up backslashes () rather than forward slashes (/) in the directory separators when using efibootmgr. This command will work on most systems that are already booted into EFI mode; however, it won't work if you're booted in BIOS mode. You may also need to add options if your ESP is in some unusual location or if your system is unusual in some way. Consult the efibootmgr man page if you need help.
On some systems, efibootmgr won't do what you expect. On such systems, you may have better luck renaming the rEFInd files, as described in the Alternative Naming Options section.
Installing rEFInd Manually Using Mac OS X
Before installing rEFInd on a Mac, you must determine whether it uses a 32-bit or 64-bit EFI implementation. Most Intel-based Macs have 64-bit EFIs, so you should use the refind_x64.efi file with them; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the refind_ia32.efi file. You can determine whether your Mac needs the x86-64 or IA32 build by typing the following command in a Mac Terminal window:
The Refind Binary File Is Missing Aborting Installation Management Group
The result should include either EFI32 or EFI64, indicating that you should use the refind_ia32.efi or refind_x64.efi binary, respectively.
The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you can (and probably should) install it to OS X's system partition or some other HFS+ partition rather than to the ESP, and you must use the bless utility rather than efibootmgr. To be precise, you should follow these steps:
- Open a Terminal window in which you'll type the following commands.
- If you want to install rEFInd on your ESP, you must first mount it. You can do this by typing mkdir /Volumes/esp followed by sudo mount -t msdos /dev/disk0s1 /Volumes/esp. Note that this step is usually optional, and it makes the procedure a bit more complex, so you might want to forego it. On the other hand, installing to the ESP is required if you're using the whole-disk encryption feature of OS X 10.7. Note that you may need to change /dev/disk0s1 to something else if your ESP is at an unusual location. Use a tool such as my GPT fdisk (gdisk) to examine your partition table to find your ESP if necessary.
- Type sudo mkdir -p /efi/refind to create a suitable directory for rEFInd. If you want to place rEFInd on the ESP or some other partition, you should adjust the pathname appropriately, as in /Volumes/esp/efi/refind. Alternatively, you can use the Finder to create the directory.
- Copy the files in the refind subdirectory of the rEFInd binary package to the like-named directory you've just created. You can do this in the Finder or by typing sudo cp -r refind/* /efi/refind/ in your Terminal window after changing into the rEFInd package's main directory.
- Remove the file for the version of rEFInd you're not using, as in sudo rm /efi/refind/refind_ia32.efi on a Mac with a 64-bit EFI or sudo rm /efi/refind/refind_x64.efi on a Mac with a 32-bit EFI.
- Optionally, remove the drivers directory for the architecture you're not using--/efi/refind/drivers_ia32 or /efi/refind/drivers_x64, as appropriate. You may also want to remove some or all of the drivers for the architecture you are using; if you don't need them, they'll slow down the start process. See the page on drivers for more on this topic. Note that Apple's firmware includes its own HFS+ driver, so the HFS+ driver provided with rEFInd is useless on Macs.
- If this is your first installation, type sudo mv /efi/refind/refind.conf-sample /efi/refind/refind.conf (adjusting the path as necessary) to rename the sample configuration file so that it will serve as a real configuration file. (Again, you can do this with the Finder, if you prefer.)
- 'Bless' rEFInd by typing one of the following two commands:
- If you're installing rEFInd to an ordinary HFS+ volume, type sudo bless --setBoot --folder /efi/refind --file /efi/refind/refind_x64.efi. (Adjust the path and filename as necessary if you're placing rEFInd somewhere else or using the 32-bit version.)
- If you're installing rEFInd on the ESP, type sudo bless --mount /Volumes/esp --setBoot --file /Volumes/esp/efi/refind/refind_x64.efi, adjusting the mount point and exact path to the file as appropriate for your installation.
- If you don't want to reboot immediately after installing rEFInd, you may optionally unmount the ESP by typing sudo umount /dev/disk0s1 or sudo umount /Volumes/esp. This step isn't strictly required, but if you want to keep the ESP out of your directory tree, it can be useful.
When you reboot, your Mac should bring up the rEFInd menu, and should continue to do so thereafter. If you make changes that break this association, you can re-run the bless command (if necessary, restoring the rEFInd files first). This might be necessary after installing system updates from Apple or if you upgrade rEFInd to a newer version.
If you're replacing rEFIt, you may discover that rEFInd works on the first boot, but the system reverts back to rEFIt or a direct boot to OS X on the second boot. Kousoku sentai turboranger episode 1 english sub. To fix this problem, you can remove the rEFItBlesser program, which is located at /Library/StartupItems/rEFItBlesser. This program attempts to keep rEFIt set as the default boot loader, but it also has the purpose of protecting the computer from launching the wrong OS after waking from sleep. If you want that protection, my suggestion is to install rEFIt and rEFItBlesser and then replace the refit.efi file with refind_x64.efi or refind_ia32.efi (renaming it to refit.efi. Used in this way, rEFInd will still look for its own configuration file, refind.conf, so you'll need to move it but not rename it. If you don't move the icons from the rEFInd package, your icons will continue to look like rEFIt icons, and you'll be missing the new icons for specific Linux distributions that rEFInd provides. One final caveat: It's conceivable that rEFItBlesser is what's causing filesystem corruption for some users, so if you've been having this problem with rEFIt, it might be worth disabling this program and not using it with rEFInd.
If you want to remove rEFInd from your system, you can delete its files. The Mac will revert to booting using whatever standard boot loader it can find. Alternatively, you can use bless to bless another EFI boot loader. The GUI Startup Disk utility in System Preferences provides a simplified interface that enables you to select which OS X installation to boot, but it doesn't look for non-Apple boot loaders, so you can't use it to enable rEFInd.
Installing rEFInd Manually Using Windows
To install rEFInd under Windows, you must first find a way to access the ESP, which Windows normally hides from view. One way to accomplish this goal, and to proceed forward once the ESP is accessible, is as follows:
- Locate Command Prompt in the Start menu, right-click it, and select Run as Administrator. This action opens a Command Prompt window with administrative privileges.
- Type mountvol S: /S in the Administrator Command Prompt window. This makes the ESP accessible as drive S: from that window. (You can use a drive identifier other than S: if you like.)
- Change into the main rEFInd package directory, so that the refind subdirectory is visible when you type dir.
- Type xcopy /E refind S:EFIrefind to copy the refind directory tree to the ESP's EFI directory. If you omit the trailing backslash from this command, xcopy will ask if you want to create the refind directory. Tell it to do so.
- Type S: to change to the ESP.
- Type cd EFIrefind to change into the refind subdirectory
- Type del refind_ia32.efi to delete the unused 32-bit version of rEFInd. (Windows only supports EFI boots on 64-bit EFI implementations and in 64-bit versions of Windows.)
- Optionally type rd /s drivers_ia32 to delete the drivers_ia32 directory and its contents. You may also want to selectively delete some of the drivers in the drivers_x64 directory, depending on your needs. Unnecessary drivers may slow the rEFInd start process. See the page on drivers for more on this topic.
- Type rename refind.conf-sample refind.conf to rename rEFInd's configuration file.
- Type bcdedit /set {bootmgr} path EFIrefindrefind_x64.efi to set rEFInd as the default EFI boot program. Note that {bootmgr} is entered as such; that's not a notation for a variable.
- If you like, type bcdedit /set {bootmgr} description 'rEFInd description' to set a description (change rEFInd description as you see fit).
At this point, when you reboot, rEFInd should appear as your new default boot program. One caveat: My only EFI Windows installation uses UEFI DUET, which 'forgets' its boot options upon reboot. Thus, I'm unable to test the last two steps (which were provided by a helpful user) myself. If it doesn't work for you, you have several other options, such as:
- You can rename files on the ESP. as described in the next section, Alternative Naming Options.
- You can boot from an optical disc into an emergency OS to do the job. Ubuntu, for instance, provides an EFI-bootable installer with a 'try before installation' mode. You'll need to type sudo apt-get install efibootmgr to install efibootmgr, but you can then use that program as described earlier. (If you're using Ubuntu, you'll need to precede the command with sudo.
- You may be able to use rEFInd's bootable CD image to use rEFInd to boot an OS that's been installed but rendered inoperable because of changes to your boot order. You can then use efibootmgr, bless, or some other tool to restore rEFInd as the default boot loader.
Installing rEFInd Manually Using an EFI Shell
If you can't currently boot any OS (say, because a firmware update has wiped your NVRAM entries), you may find it convenient to install rEFInd using an EFI version 2 shell. Unfortunately, the bcfg command described here is not available in the EFI version 1 shell, and the version 2 shell is unusable on many firmware implementations prior to 2.3.1. Thus, this procedure won't work for all systems.
In addition to emergency situations, using bcfg can be desirable if efibootmgr or other OS-hosted tools don't do the job. This happens under VirtualBox, for instance. An alternative in such cases can be to use alternative names for rEFInd.
To begin, you must have a way to launch your shell. Unfortunately, this can pose a dilemma, since without rEFInd or some other boot manager, many EFI implementations lack the means to launch a shell. Some will do so, though, if the shell is stored as shellx64.efi (for x86-64) or shellia32.efi (for x86) in the root directory of the ESP. Thus, you can try copying your shell file there. You can obtain EFI 2 shells here:
Note that the IA32 shell included in rEFInd's CD-R image version is a version 1 shell, so you can't use it for this purpose. You can, however, copy rEFInd's files from the CD-R. You can even launch the version 1 shell included with rEFInd and then use that to launch a version 2 shell. The x86-64 shell on the CD-R is the alternate shell, which should work on any x86-64 computer. Once you've booted the shell, you can proceed as follows:
- If you haven't installed rEFInd previously, unpack its zip file to a FAT partition. This can be the ESP itself or another partition, such as a USB flash drive. If you're simply repairing a lost NVRAM entry, you needn't move your existing rEFInd files.
- Identify your filesystems, which are labelled with the form fsn:, as in fs0: for the first filesystem, fs1: for the second, and so on. Type the filesystem number followed by the Enter key to begin using it. You can then type ls or dir to see the contents of the filesystem. Chances are your ESP will be fs0:, but it could be something else. (The following steps assume your ESP is fs0:; you'll need to adjust them if it's not.) If rEFInd's source files are on another device, you must identify it, too.
- If necessary, create a directory for rEFInd by typing mkdir fs0:EFIrefind. (If the fs0:EFI directory doesn't already exist, you must create it first, though.)
- Change to the directory in which rEFInd's files exist.
- Type cp refind_x64.efi fs0:EFIrefind to copy the rEFInd binary file. (Adjust the name if you're using a 32-bit computer.)
- Type cp refind.conf-sample fs0:EFIrefindrefind.conf to copy and rename the sample rEFInd configuration file.
- Type cp -r icons fs0:EFIrefind to copy rEFInd's icons.
- Optionally, type cp -r drivers_x64 fs0:EFIrefind to copy rEFInd's 64-bit drivers. (You could instead copy the 32-bit drivers or limit yourself to just the drivers you need, of course.)
- Type fs0:, if necessary, to change to the ESP.
- Type cd EFIrefind to change to rEFInd's installation directory.
- If you want to edit rEFInd's options, type edit refind.conf and use the shell's built-in text editor to do so. Press F2 followed by the Enter key to save your changes and F3 to exit.
- Type bcfg boot dump -b to see a list of existing NVRAM entries. Pay attention to their numbers (labelled Option: and Variable:, with the latter number preceded by the string Boot, as in Boot0007). You'll want to create a boot entry for rEFInd using a number that's not in use.
- Type bcfg boot add 3 fs0:EFIrefindrefind_x64.efi 'rEFInd', adjusting the number (3 in this example), filesystem (fs0:), and filename (EFIrefindrefind_x64.efi) as necessary for your system. If you're used to Linux, be sure to use backslashes (), not Linux-style forward slashes (/) as directory separators. Note that some shells may ignore the number you entered and use another one, so watch for this possibility.
- Type bcfg boot mv 3 0, substituting the option number for the entry you created for 3. This moves rEFInd to the top of the boot order.
- Type reset to reboot the computer.
With any luck, rEFInd will start up at this point. If not, you can check your settings using a shell or an emergency system for your OS of choice. In an EFI shell, you might type bcfg boot dump -b to view your boot loader entries and verify that rEFInd appears at the top of the list. Be sure to check the pathname for typos. If you continue to have problems, you might look into giving rEFInd a fallback filename that your firmware will recognize.
Using OS X Whole-Disk Encryption
If you're using OS X's Whole-Disk Encryption (WDE) feature, you must do two extra things:
- You must install rEFInd to the ESP. Unfortunately, as described earlier, this can result in a delay (usually of 30 seconds) as the firmware launches rEFInd. See the upcoming section on fixing sluggish Mac boots if you run into this problem.
- You must uncomment the dont_scan_volumes line in refind.conf and ensure that 'Recovery HD' is not among its options. (You can use a blank line or provide a dummy value if you want to scan all your volumes.) Alternatively, you can create a manual boot stanza to boot OS X.
Alternative Naming Options
Some EFI implementations do a poor job of honoring the boot options set via Linux's efibootmgr or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. Broadly speaking, there are two alternative names that are most useful:
- EFI/BOOT/bootarch.efi—This name is the official EFI fallback filename. It's most commonly used on bootable removable disks, but it can be used on hard disks. It's typically used only if no NVRAM entry points to a valid boot loader.
- EFI/Microsoft/Boot/bootmgfw.efi—This filename has no official special standing in the EFI specification, but as a practical matter, many EFI implementations use it as a fallback boot loader in addition to or instead of EFI/BOOT/bootarch.efi. In fact, some give it such a high precedence that you can't boot anything that's not given this name!
If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can use the mvrefind.sh script to move your installation in one step, or you can move and rename your files manually.
Using mvrefind.sh
The easiest way to move a rEFInd installation, at least in Linux, is to use the mvrefind.sh script. If you installed from one of my RPM or Debian packages, this script should be installed in /usr/sbin, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux mv command, but you pass it the directory in which a rEFInd installation appears and a target location:
This example moves rEFInd from /boot/efi/EFI/BOOT to /boot/efi/EFI/refind. It differs from mv in several ways:
- The script renames rEFInd in a way that's sensitive to its source and destination directories—for instance, mvrefind.sh knows that rEFInd (or shim, for Secure Boot installations) must be called bootx64.efi on a 64-bit installation in /boot/efi/EFI/BOOT, so it looks for rEFInd under that name when copying from this directory, or it renames rEFInd to that name when copying to it.
- The script creates a new NVRAM entry for rEFInd when it copies to any location but EFI/BOOT or EFI/Microsoft/Boot. It refuses to copy to such locations if it's not run from an EFI-mode boot.
- The script knows enough to back up existing boot loaders stored in EFI/BOOT or EFI/Microsoft/Boot when copying to these locations. For the former location, the script backs up EFI/BOOT as EFI/BOOT-rEFIndBackup; for the latter, it moves EFI/Microsoft/Boot/bootmgfw.efi to EFI/Microsoft/bootmgfw.efi.
The mvrefind.sh script is likely to be useful in resolving boot problems—if your system won't boot, you can try copying the installation to /boot/efi/EFI/BOOT, /boot/efi/EFI/Microsoft/Boot, and /boot/efi/EFI/refind in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at /boot/efi.) You could also copy a BIOS-mode install from /boot/efi/EFI/BOOT or /boot/efi/EFI/Microsoft/Boot to /boot/efi/EFI/refind to make it more robust against Windows repairs (assuming your firmware isn't broken).
Renaming Files Manually
Some EFI implementations do a poor job of honoring the boot options set via Linux's efibootmgr or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. To do this, follow these steps:
- Access your ESP and install rEFInd to it, as described in earlier sections.
- Look for an existing directory called EFI/BOOT or EFI/Microsoft/Boot. If neither of these directories exist, skip the next step. (Note that FAT is case-insensitive, so the name may vary in case.)
- Rename the existing directory or boot loader file to something else. For EFI/BOOT, try renaming it to EFI/Oldboot. For EFI/Microsoft/Boot, move or rename the bootmgfw.efi file it contains. For instance, you can move it to EFI/Microsoft. This will keep the boot loader accessible to rEFInd's menu, while preventing the firmware from launching it automatically.
- Rename/move your EFI/refind directory to EFI/BOOT. If you're working from EFI/Microsoft/Boot, you should move the contents of your rEFInd directory to EFI/Microsoft/Boot.
- Rename EFI/BOOT/refind_x64.efi to the name of the boot loader it's replacing—it should become EFI/BOOT/bootx64.efi or EFI/Microsoft/Boot/bootmgfw.efi.
When you reboot, rEFInd should come up. With any luck, it will detect your old boot loader as an option, if one was installed before.
Upgrading rEFInd
If you've installed an earlier version of rEFInd, you can upgrade a bit more easily than you can install directly:
- On a UEFI-based PC, under any OS, you should be able to replace your old rEFInd file with the new one. Make sure that the new rEFInd has the same name as the old one, and that it's for the correct CPU type. Since UEFI launches boot programs by filename, a simple file replacement will suffice to launch the new version. If the new version includes new icons, you may want to copy some or all of them.
- On a Mac, you can copy over the old rEFInd binary file from Linux and it will usually work, provided you copy directly over the old file (rather than rename or delete the old file and then copy the new one in its place). The same caveats about icons as apply to UEFI-based PCs apply in this case. This method requires an extra step in Mac OS X, though.
- In OS X, if you copy over the original file with the new one, you'll probably have to re-bless it to make it work.
- Under Linux or OS X, you can re-run the install.sh script. In most cases this works fine, but you'll end up with a duplicate of the icons directory (icons-backup, which holds the original icons, whereas icons holds the icons from the new package). Normally this just wastes some disk space; but if you've customized your icons, you'll need to copy your altered icons back. Since version 0.6.2, install.sh has searched for rEFInd in several locations on the ESP, and will upgrade whatever it finds.
- Under an RPM- or Debian-based Linux distribution, you can use your package system to install a newer version of the RPM or Debian package that I provide. This will upgrade the files in your Linux filesystem and re-run the install.sh script, so as with the previous options, you'll waste a little disk space on duplicated icons, but the process should otherwise work quite well.
In all cases, if the new version includes new or altered configuration file options, you may need to manually update your configuration file. Alternatively, if you've used the default configuration file, you can replace your working refind.conf with refind.conf-sample from the rEFInd zip file. (When using install.sh, this file will be copied to rEFInd's installation directory under its original name, so you can rename it within that directory to replace the old file.)
If you're upgrading to rEFInd from rEFIt, you can simply run the install.sh script as described earlier or perform a manual installation. Once installed, rEFInd will take over boot manager duties. You'll still be able to launch rEFIt from rEFInd; a rEFIt icon will appear in rEFInd's menu. You can eliminate this option by removing the rEFIt files, which normally reside in /EFI/refit.
Installing Additional Components
rEFInd includes the ability to launch any EFI program; however, rEFInd detects only certain programs. These include boot loaders in traditional locations and a handful of other programs. To launch most of these other programs, you must download and install them separately from rEFInd:
- shell.efi—This file, placed in the ESP's EFI/tools directory, adds the ability to launch a text-mode EFI shell from rEFInd. Note that the download link is to a 64-bit binary that must be renamed before rEFInd will recognize it. Additional shell download links appear on the Arch Linux wiki, and on other sites; try a Web search if the shell you find doesn't work to your satisfaction.
- Memtest86—This is a popular tool for performing basic hardware tests, and especially memory tests. rEFInd recognizes this program when it is stored in the EFI/tools, EFI/tools/memtest, EFI/tools/memtest86, EFI/memtest, or EFI/memtest86 directory, with a program filename of memtest86.efi, memtest86_x64.efi, memtest86x64.efi, or bootx64.efi. (Change x64 to ia32 on IA-32 systems.) Be sure to download the EFI version of the program. If you get the USB flash drive version, you should mount the flash drive's ESP (partition 2) and copy the EFI/BOOT directory to your own ESP's EFI/tools/memtest or other Memtest86 directory name, as just specified. rEFInd should then recognize it, provided the showtools line includes the memtest or memtest86 token.
- gptsync.efi or gptsync_arch.efi—This program creates a hybrid MBR from your regular GPT disk. A hybrid MBR is a dangerous hack that enables Windows and OS X to coexist on a Macintosh disk. If you're using a UEFI-based PC, a hybrid MBR is likely to be useless at best, so you shouldn't create one, and it's safest to not install gptsync.efi. If you're using a hybrid MBR to enable dual-booting Windows and OS X on a Mac, though, placing this program file in the ESP's or Mac boot partition's EFI/tools directory will enable you to regenerate your hybrid MBR should some other tool convert the MBR to a standard protective MBR. You can obtain the file from the original rEFIt package, or beginning with rEFInd 0.6.9, an updated version is included in the rEFInd package. The rEFInd version of gptsync_arch.efi uses a more sophisticated algorithm for determining what GPT partitions to duplicate in the MBR and it includes additional safeguards to minimize the risk of damage should you run the program on a disk that might have been damaged. The original rEFIt version of the program usually goes by the filename gptsync.efi, whereas the updated rEFInd version ships with an architecture code, as in gptsync_x64.efi or gptsync_ia32.efi. The rEFInd install.sh script installs gptsync_arch.efi when run under OS X, but not when run on Linux. In addition to installing the program, you must edit refind.conf, uncomment the showtools line, and add gptsync to its list of options.
- Drivers—You can install drivers to extend the capabilities of the EFI. rEFInd ships with filesystem drivers for ext2fs, ext4fs, and ReiserFS, which can enable you to boot a Linux kernel with EFI stub support from an ext2fs, ext3fs, ext4fs, or ReiserFS partition. (rEFInd also provides ISO-9660 and HFS+ drivers.) You can find additional drivers from other sources, although they're still on the scarce side. See the Using EFI Drivers page for more on this topic.
- Secure Boot files—If you're running on a system that supports Secure Boot, chances are you'll need extra support files, such as shim.efi and MokManager.efi. I describe these in detail on the Managing Secure Boot page.
I've seen links to other versions of these tools from time to time on the Web, so if you try one of these programs and it crashes or behaves strangely, try performing a Web search; you may turn up something that works better for you than the one to which I've linked.
Fixing a Sluggish Macintosh Boot
I've received a few reports of a sluggish boot process (a delay of about 30 seconds before starting rEFInd) on some Macs after installing rEFInd. I've been unable to replicate this problem myself, and its true cause remains mysterious to me. I have found three possible solutions, though: moving rEFInd to an HFS+ volume,using the fallback filename, and clearing NVRAM entries.
Moving rEFInd to an HFS+ Volume
Most of the reports of sluggish Macintosh boots I've seen note that the user installed rEFInd to the ESP rather than to the OS X root partition. Some users have reported that re-installing rEFInd to the OS X root partition clears up the problem. This is obviously a straightforward solution to the problem, if it works. Note that rEFInd can launch boot loaders that are stored on any partition that the EFI can read no matter where it's installed; therefore, you'll still be able to launch boot loaders stored on the ESP (or elsewhere) if you install it in this way.
The Refind Binary File Is Missing Aborting Installation Guide
The biggest drawback to this approach is that you won't be able to edit the rEFInd configuration file or move rEFInd-related binaries from an EFI shell if you install it in this way, since Apple's HFS+ driver for EFI is read-only. (The same is true of rEFInd's HFS+ driver, so it won't help you overcome this limitation.) You may also be limited in making changes to your rEFInd configuration from Linux or other OSes, too, since Linux's HFS+ drivers disable write support by default on volumes with an active journal. You can force write access by using the force option to mount; however, this procedure is noted as being risky in the Linux HFS+ documentation, so I don't recommend doing this on a regular basis. As a compromise, you might try creating a small non-journaled HFS+ volume that's dedicated to holding rEFInd. You could even mount it as the Linux /boot partition, in which case it would also hold the Linux kernel and related files. You'll need to install rEFInd manually if you try this.
A variant of this solution is suggested in this blog post, which recommends placing rEFInd on an HFS+ volume on the first SATA channel. D16 group lush 101 vst torrent. (In the blogger's case, that channel used to hold an optical drive, but that drive was replaced by a hard disk.)
Using the Fallback Filename
I've received a few reports that installing rEFInd to the ESP using the fallback filename (EFI/BOOT/bootx64.efi on most systems, or EFI/BOOT/bootia32.efi on very old Macs) can work around the problem.
Clearing the NVRAM Entries
The first is a Web forum post that describes a possible fix. Be aware, though, that this procedure involves using the efibootmgr utility on Macs, which has been known to damage the firmware on some Macs. Other reports indicate that this problem has been fixed with 3.3.0 and later kernels. Thus, I present this information cautiously and with a strong 'use at your own risk' warning. If you care to proceed, I recommend you update your Linux kernel to the latest possible version and then proceed as follows:
- Boot into Linux.
- Type efibootmgr as root to obtain a list of your boot loader entries. Each entry includes a boot number, as in Boot0003 or Boot0027.
- Remove all of the boot loader entries except rEFInd's by using efibootmgr's -b bootnum option to specify the boot entry and -B to delete it. For instance, typing efibootmgr -b 0027 -B as root deletes boot entry Boot0027. Issue a separate efibootmgr command for each boot entry.
- Re-install rEFInd using the install script. It's unclear from the original post if this meant installing from Linux or from OS X.
Some sources suggest that delayed launches of rEFInd on Macs are more common when installing rEFInd to the ESP, so if you've done this, you could try re-installing it to your OS X boot partition.
Uninstalling rEFInd
If you decide you don't want to keep rEFInd, you can uninstall it. Doing so is a matter of removing the rEFInd files from your ESP (or from your OS X boot partition, if you installed the program there). Butter project mac. In Linux, a command like the following, typed as root, should do the trick:
This example assumes that your ESP is mounted at /boot/efi and that rEFInd is installed in EFI/refind on that partition. If you've mounted your ESP elsewhere, or installed rEFInd elsewhere, you should adjust the command appropriately.
The same procedure works in OS X, with the caveat that the ESP isn't normally mounted in OS X and rEFInd is installed to the OS X boot partition by default. You'll also need to use sudo to acquire root privileges. Thus, you'd probably use a command like the following in OS X:
Many variants of both of these commands are possible on both OS X and Linux. For instance, you'd probably use sudo on Ubuntu; and if you installed rEFInd to your ESP on a Mac, you'd need to first mount the ESP and include its path in the rm command.
If you installed via an RPM or Debian package in Linux, using your package manager will remove the package files, but not the files that the installer places on your ESP. Thus, you must uninstall those files manually, as just described. To complete the job, you'll also have to remove /boot/refind_linux.conf, and perhaps the /etc/refind.d directory.
From Windows, you must reverse the directions for installing in Windows—type mountvol S: /S to mount your ESP as S:, then navigate to the S:EFI directory and delete the refind subdirectory.
See All Results For This Question
In any of these cases, when the computer boots and cannot find the rEFInd files, it should move on to the next boot loader in its list. In my experience, some EFI firmware implementations remove boot loaders they can't find from their NVRAM lists, so nothing else will be required, provided you have another working boot loader in your firmware's list. If your firmware doesn't automatically clean up its NVRAM entries, rEFInd's entry will do little harm; however, you can delete it with the efibootmgr utility in Linux:
This example shows use of efibootmgr's --verbose (-v) option to display boot loaders so as to identify which one is rEFInd, followed by --delete-bootnum (-B) to delete a boot program and --bootnum (-b) to identify which one to delete. Of course, in this example there's not much else left, so you'd presumably want to install another boot loader at this point! If you already have another one installed, you may want to check the BootOrder line to determine which one will take precedence when you reboot. If you don't like what it shows, you can adjust it with the --bootorder (-o) option; consult efibootmgr's man page for details.
If you're not using Linux, you may be able to find a utility that serves a similar function. The OS X bless utility (or its GUI equivalent, the Startup Disk item in System Preferences) should do the trick; but Macs pick up standard OS X boot loaders when they boot and find that a configured non-standard boot loader is missing, so this shouldn't be necessary on Macs. Under Windows, the bcdedit command, described in the section on installing rEFInd under Windows, may work, although I've not attempted this.
copyright © 2012–2014 by Roderick W. Smith
This document is licensed under the terms of the GNU Free Documentation License (FDL), version 1.3.
If you have problems with or comments about this Web page, please e-mail me at [email protected]. Thanks.
Wikipedia:rEFInd
Return to my main Web page.