banner



Asrock Hard Drive Repair Boot Key?

This pocket-size guide has been written to walk you through a possible fix to enable your Asrock motherboard to boot correctly using UEFI, primarily for the Clover bootloader. It should just exist used if you take followed the recommended method for installing and booting using Clover, simply your organization refuses to kicking without the Unibeast USB installer.

This issue was originally identified on certain Asrock motherboards, and has been tested on the Z87E-ITX. Since we are dealing with UEFI, at that place is no reason why information technology shouldn't piece of work on other boards but has not been tested further.

An alternate method to this guide using Clover tin can exist found here, courtesy of ctyler at post #38 of this thread.

The pre-requisites where this may work for you are :

:ch: You utilise an Asrock motherboard.

:ch: You accept installed OSX using the recommended method.

:ch: Y'all have installed the Clover bootloader.

:ch: Your computer won't boot from the system bulldoze where yous installed OSX and Clover.

If you lot can tick all 4 boxes higher up then read on. If non then yous demand to get your organisation installation to the point where you can tick all the boxes.

Nosotros are not aware of this happening on whatever other model of motherboard at this time. In the case of an Asrock motherboard, information technology appears to happen because of a poor/incomplete UEFI implementation. What this means is that the board does not kick properly, even though the Clover bootloader is correctly installed.

Important : The method we employ here has proven to be non-destructive then far. No information has been lost, no fully installed organisation has disappeared. It doesn't mean that volition ever exist the case. Yous are responsible for your data and keeping proper backups of your of import stuff. Be smart and do that before you begin.

In that location are a number of considerations for this method - pay attention and read them carefully so you fully empathize the implications:

ane.

Existing Methods

. You should follow the existing guidance and brand every try to install your arrangement the recommended manner. Nosotros are primarily looking at Mac Os 10 El Capitan using the Clover bootloader. The recommended method tin can be constitute here.

2.

Search The Forums

. See if anyone else has built their system using the same motherboard as yous. They may have already discovered the correct settings to enable booting from UEFI.

3.

Reverting Changes

. The changes described here can be reversed by doing a full UEFI bios reset. This is adept in example you make a fault; the downside of this is that you will then need to go dorsum and change all your bios settings again. Nigh modernistic motherboards have the option to save your current settings to a profile, which can and then be recalled. Make use of this.

four.

UEFI Kicking Setting

. If you lot haven't already done so, make sure your system is set to boot using UEFI instead of legacy. This is usually found in the boot settings of your bios. Exist aware that well-nigh modern motherboards which use UEFI will show both UEFI and legacy boot options at the same time.

5.

Linux & The Command Line

. The style we do this is by using linux, working from the control line, using elevated privileges. If you are not comfortable with this so do not proceed. Elevated privileges mean you could easily cause damage to your otherwise shiny new OSX installation.

Finally, if your Clover install is hosed or incorrectly configured, this method volition not set up it for you. This is nigh helping the motherboard UEFI to 'see' the Clover bootloader correctly; it does not prepare a broken or incomplete Clover install.

So now you have read all that, what to exercise next ?

Follow these steps in gild; do non deviate. Take your time and read the instructions very carefully.

Part 1 : What You Demand

Our weapon of choice here is a good linux distribution. You are gratis to choose whichever you lot like, but you must make certain that it contains the parcel '

efibootmgr

', and also that information technology contains an EFI kernel module. This module if often called '

efivars

'.

The tested distribution at this time is Mint Linux. This is a mod, up-to-appointment distribution, and contains the parcel and module described higher up. It does not require a network connection, which some other distros may need. Follow this link to download the version I used successfully. The instructions in this guide assume you are using this distribution, other distributions may exist slightly different.

Y'all will need to create a bootable drive with the linux you lot downloaded. Since the download is a standard .iso image, y'all can but burn it to a DVD drive, or create a USB drive from information technology. In that location are many tools bachelor to create a USB installer; one example is 'UNetBootin' which has versions available for Windows, OSX or Linux.

Of import : Make sure you do not overwrite your OSX Unibeast installer.

Part ii : Boot The New Linux DVD/USB

Insert your new linux DVD or USB and kick your system from it. Press F11 or whichever key your arrangement uses to get to the boot selection list. In the list y'all volition see several entries, and the one you lot are looking for is UEFI and represents the drive containing your linux. Here is what mine looked like :

SelectLinuxBootDrive.JPG

In this case, I wrote the linux iso image to DVD and booted from that.

Important : Merely boot from the UEFI entry. Using not-UEFI means it will non work as expected.

It may seem odd that you have a UEFI entry for your removable drive with linux on it, but non for your arrangement drive with the OSX installation. This is the quirk we are attempting to set up with this method.

Await for the linux desktop to load. This may take a few minutes depending which medium you are booting from. Equally the desktop loads, you lot will see a login box on the screen. Don't enter annihilation here, the system will automatically log you in later on a few seconds.

Function 3 : Modify The Settings

Here is where we really get stuck in; one time again, pay shut attention.

At the lesser left of the linux desktop screen, adjacent to the carte du jour push you volition see several pocket-size icons. Click on the icon for 'Concluding'. This will open a window like to the 'Last' awarding in OSX.

LinuxTerminalIcon.JPG

Now type in the post-obit commands and press Render :

The system has already given us elevated privileges, but doing this will salve extra typing.

This tells linux to load the kernel module 'efivars'. This is needed so that linux tin can communicate with the UEFI system on your motherboard.

Code:

                  apt-become install efibootmgr                

This tells the linux system to install the 'efibootmgr' package we need. It is already on the linux system just not installed by default.

You will see some text on screen as the bundle is installed. This is what your Terminal window should look like so far :

AfterInstallationOfPackage.JPG

This runs the efibootmgr plan. Yous will see a list of drives in your system ; the verbal output volition vary. Here is what mine looked like :

FirstEFIList.JPG

In the list yous tin see I have a total of 3 drives listed. The first (Boot0001) is my SSD system drive, the second (Boot0002) is my DVD bulldoze, the 3rd (Boot0003) is likewise my DVD drive but as a UEFI device.

Each one has an ID of the format 'Boot00xx', and the boot order is shown relative to these. The currently booted bulldoze is also shown as 'BootCurrent'; this confirms I take booted UEFI from the Optiarc DVD drive.

Code:

                  efibootmgr -c -L "Clover UEFI" -l "\EFI\CLOVER\CLOVERX64.EFI"                

This instructs the organization to create a new UEFI entry.

The first part in quotes, "Clover UEFI", is the label you are giving to the new UEFI entry. This can be whatsoever description you lot like, but must be enclosed in quotes.

The 2d part in quotes, "\EFI\CLOVER\CLOVERX64.EFI" tells the UEFI organisation where to find the file it needs to start the UEFI boot procedure.

The flag in the middle of these 2 parts is a lower case 50 and not the number 1.

Important : Notice that we use dorsum slashes in the 2d part, and not forwards slashes. Make sure to get this correct otherwise it won't work.

Here is the ouput :

AddedNewEntry.JPG

You tin can see my new entry has been given an ID of 'Boot0000', and is currently at the bottom of the list. The arrangement has correctly set its boot guild, but we also want to move information technology to the elevation of the list.

This reaffirms the boot order for our new entry and puts it at the top of the kicking listing, which we volition see when nosotros reboot the computer.

The four digits we use in the command above correspond the final four digits of the ID assigned to the drive.

The correctly configured list and boot society at present looks like this :

NewBootOrder.JPG

That is the required changes now made.

A quick bank check in the bios boot lodge shows the changes accept been successful :

NewBiosList.JPG

You should now restart the reckoner and remove the linux boot DVD/USB. Once more press F11 or any central your system uses to display the listing of devices.

Go ahead and select the new UEFI entry to kick from Clover.

Y'all could also use something more descriptive. Here is some other fashion I labelled it :

ElCapOption.JPG

Whichever characterization nosotros utilise when adding the new entry is whats shown in the bios kick listing.

Overnice bear upon huh ?

:thumbup:

Oops, I Might Take Messed Up With The Guide, What Do I Do Now ?

If your system does not boot every bit expected or yous have got lost somewhere in the center of the guide and not sure what to do next so only reboot your system, get back into your bios and do a total bios reset, back to default settings. Any changes will then be wiped out and you can try once again. Think though to optimize your settings for OSX equally usual.

The changes we have made with the guide will survive reboots, but will non survive a bios reset or bios upgrade.

Note this method will not fix every single Clover boot consequence; if you find y'all can boot UEFI from the Unibeast installer but not your OSX system bulldoze, this may work for you lot.

Let us know if this method helps you out !

:)

Asrock Hard Drive Repair Boot Key?,

Source: https://www.tonymacx86.com/threads/guide-asrock-uefi-boot-fix.174726/

Posted by: garrettmatureaus.blogspot.com

0 Response to "Asrock Hard Drive Repair Boot Key?"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel