EFI partition?

Similar Questions

• Disappeared from the EFI partition

  Hello

  I have a macmini end of 2012. I have the dual boot with Windows 8.1 and Yosemite. I also have a third FAT partition for data sharing.

  So, my setup looks like this, in Windows:

  

  The problem is that the EFI partition is gone, so I could do reach log Windows using an external backup drive, which also had a copy backup of the EFI partition. Yes, I basically cloned this drive for a long time and I've tested all the BONES on the external hard drive, and they were all bootable. Thus, using this trick, I managed to get into Windows.

  But now that I got under Windows I see as the missing EFI partition. I recently installed a customized for Win8.1 shell that makes it look like Win10. This software must have messed with the EFI partition, I don't see anything else that might have caused this.

  Just before the disc became starts plu I tried a few bar custom this custom, shell that uses the app mode of Win8.1 full screen, and when I tried to quit it by closing it, he suddenly threw an error message, I clicked on cancel, then the system froze.

  I pressed the power button to restart, then it's just stuck in a gray screen for minutes. Pressing ALT does not display the start menu. So, I concluded that the EFI must be wasted, so after the POWER test the computer does not find a bootable floppy. But I get no message, like the missing disk or stuff like that.

  I know that there are some tools that you can use to fix your EFI partition. It runs on Windows, because I'm not sure that I can boot into OS X Yosemite. In addition, as you can see the free space on drive D, where I installed Yosemite is not reported correctly. Which clearly indicates that there must be some data from corrupt volume information.

  Please install GPT Fdisk on the side Windows of https://sourceforge.net/projects/gptfdisk/ and your drive can be inspected.

  In most cases, EFI is usually invisible. The 200 MB in the first instalment on disk0 seems to be your EFI. It may be a problem with the MBR is structured.

• How to stop the mounting EFI partition

  Hello

  All of a sudden the EFI partition on one of my external drives moved whenever the drive is connected.  I don't want this behavior.

  I want to partition EFI stop this (or any) editing 'automatically', but for the life of me can not know how to do this.

  Any tips/tricks/pointers to help me control switch partition EFI to mount automatically would be greatly apprecaited.

  Saw stopped and restarted the MacBook behavior returns to the 'normal' - being the partition EFI is more monte when you sign this particular drive, or any drive besides.

  I'm always interested in how the automatic editing, or not (preferred), the EFI partition can be controlled.

• Z400 disks with EFI partition not mounting after the Windows 7 Pro upgrade

  HP z400: after a repair/upgrade to sp1 of Windows 7 Pro (64), no matter what external disk with an EFI partition is not installed.  Player will be present in the BIOS and the management of drive, but without a letter. Cannot assign a drive letter.  All other discs mount correctly.  Disks with EFI partition will mount on other PCs.  All the drivers seem to be current and fuctional.

  I thought about it... after two weeks of puzzle, I finally found the cause.

  I run MacDrive 8 so I can play discs with HFS + formatting.  This program should be completely uninstalled and reinstalled after the upgrade.  I had turned it off before the upgrade, but it takes more than that.  Everything works now as expected.

  But wouldn't be INCE if Windows reads discs mac natively?

• Efi partition damaged or corrupted after installing windows 10

  Well, I had another post on this subject, but I decided I want to start a new thread that I have eliminated a lot of things and feel that I reduced it down to start EFI partitions.  Here is the fall back on what has caused all this. I had a copy perfectly fine working of Windows dualbooted with Ubuntu 10. The two operating systems works great and I have not had any problems with resetting. After updating to win10 everything was peachy, but there were a few complications with grapchics drivers so I decided to do a clean install and just drag all the old baggage, which has solved THIS problem. However, when I did that, without thinking I just deleted all partitions and let the windows installation program re-create them. Which included the efi boot partition. However, windows 10 must have done something wrong with the efi boot partition because after that, I was not able to make a good restart of the operating system. Problem with Ubuntu I have installed next to her. However! I can make a stop and turn on just fine and the issue only happens when I try to reboot from an OS. I can reboot from the BIOS and for updates it occasionally resumes once, but consecutive reboots lands me to the ACER screen curtain. I can hear the hard drive Park and it does not load all simply the operating system or the bootstrapper.  I think I'm getting a bit lengthy, so I'll just mention that I've eliminated.

  Verified and tested Ram - Ram is OK

  Update Bios - Bios is fine (restarted just dandy in the process)

  Faststartup disabled - not the question

  Unplug all usb devices - nope

  Restart in diagnostic mode - nope

  safe mode - nope

  The only thing left I can think of is the only thing that I know for some changed... This efi boot partition.

  Is there a way to repair this or recreate a new in the hope that it will get done right short to reinstall everything?

  I know it is really old now, but I thought that I shouldn't keep starting probably new threads for the same problem.

  So I went through all of this and no change. Clean the disc as instructed, I tried right linux, using the recovery disk to restore to as it was from the factory and win10 once again but no dice on this, I have created. It does not restart. But I remembered something I did at the same time I forgot because it seemed really trivial. I have problems with my wifi connection drops pretty frequently and suspect interference as well as map of the factory did not offer the 5 GHz band, I replaced it with an Intel Ultimate N card I had lying around from a previous laptop. Who would possibly spoil reboot? I don't think that would interfere with it, but it's the last thing that could have changed. However, the laptop is a model of AMD. So, hmm, I guess I can try to Exchange on the map of the factory, now.

• With EFI partitions will not rise

  HP z400: after a repair/upgrade to sp1 of Windows 7 Pro (64), no matter what external disk with an EFI partition is not installed.  Player will be present in the BIOS and the management of drive, but without a letter. Cannot assign a drive letter.  All other discs mount correctly.  Disks with EFI partition will mount on other PCs.  All the drivers seem to be current and fuctional.

  Hello

  I never got a message error... all options have been grayed out.  And I tried the guest... but it has not yet been recognized in disk management.

  But after two weeks of puzzle, I finally found the cause.  I run MacDrive 8 so I can play discs with HFS + formatting.  This program should be completely uninstalled and reinstalled after the upgrade.  I had turned it off before the upgrade, but it takes more than that.  Everything works now as expected.

  But it would be really nice if Windows reads HFS disks...

  Thank you

  Scott

• HP Envy Rove: Boot with MBR instead of EFI without removing the GPT partitions

  Hello

  I activated the Legacy Startup Mode in the Configuration of the UEFI and I would how I can give greater priority to the Legacy boot (boot MBR) vs the EFI Boot.

  I mean, how do I start using the MBR without destroying GPT partitions or files EFI?

  I don't have an option in the BIOS to select the 'priority '.

  I have the BIOS with the e.17 Rev.A (latest) firmware

  Thank you.

  Best regards

  Alfredo.

  @afeno

  Welcome to the HP Forums, it's a great place to get help, find answers and advice,
  Thanks for posting your request, I'll be more than happy to help you

  If I understand correctly you want to use the trunk legacy rather than the UEFI boot, before getting into the details, however,

  Here is the difference between Boot EFI and start-up of the legacy
  
  This is the process used by the firmware to find the target of starting:
  
  Legacy boot is used by the firmware BIOS boot process.
  The firmware keeps a list of installed storage devices can be bootable (Floppy Disk Drives, hard drives, optical drives, tape drives, etc.) and list them in a configurable priority. the POST procedure has finished, the firmware loads the first sector of each target of memory storage and it scans for a valid Master Boot Record (MBR). If a valid MBR is found, the firmware passes execution of code found in the MBR, bootloader that allows the user to select a partition to boot from. If we don't get, it proceeds to the following equipment in the boot order. If no MBR is found at all, the user is presented with the famous "Please insert system disk".
  
  UEFI boot is used by the UEFI firmware boot process.
  Firmware maintains a list of volumes of valid boot called EFI Service of Partitions. During the POST firmware procedure UEFI scans all bootable storage devices that are connected to the system for a valid GPT GUID Partition Table (). Unlike a MBR, a GPT does not contain a boot loader. The firmware itself scanning the closure for a score of Service EFI to boot from. If no boot EFI partition is found, the firmware can fall back on the boot of the legacy method. If boot UEFI and legacy boot fail, the famous "Insert system disk" will be presented.
  
  In general, the UEFI boot is more desirable.

  And if you want to know how to convert a GPT to MBR or convert MBR to GPT disk: click here (3rd party link - please ignore the ads).

  Let me know how that pans,.
  I wish you a good day
  And do not hesitate to ask questions that this forum has some of the best people in the world, available and ready to help.
  Kind regards

• Install the EFI on new SSD partition when doing 10 costs of Windows Installer

  I have a similar problem to this topic. Windows was originally (and still is) installed on my HARD drive and I just installed my SSD recently. When I did a clean install of Windows 10 on my new SSD it has not installed the EFI partition.

  Is there a way to create a new partition on the SSD EFI (of course I have to do another new facility) or do I have to physically unplug my HARD drive before you begin?

  my personal rule, I always disconnect a disk with a partition bootable OS, just to reduce the troubles and do not mix the boot managers (I prefer to select the BIOS boot device)

• EFI disk0s1 not mounted. screen shows gray with help file when I restart

  I had these problems with my recent Mac.

  1. it freezes for a few seconds. Then begins to work properly. And then freezes. The beachball keeps spinning and I can't access any of the applications.

  I tried restarting. But came up with another question. The gray screen of the charges and file aid continues to Flash.

  I tried from the recovery mode, but I get the Internet (OS X Lion). I'm under El Capitan. In disk utility, I check and repair the drive. Stop and try again. Now, there are two current icons and off - no logo entry sign and apple. If I'm lucky then after 40-50 seconds, Mac starts up.

  Now, I tried to make the EtreCheck, and he gave me more results for disc

  Disk information: ⓘ

  HTS545050A7E362 disk HARD APPLE disk0: (500,11 GB) (rotation)

  EFI (disk0s1) < not mounted >: 210 MB

  Macintosh HD (disk0s2) /: 499,25 (Go 110,18 free) - 70 errors

  Drive failure!

  Recovery HD (disk0s3) < not mounted > [recovery]: 650 MB

  HL-DT-ST DVD - RW GS41N)

  
  

  That's what worry?

  
  

  What can I do to fix these problems?

  Disk0 unit 1 is not the problem. This is the EFI partition, which is never mounted, because it is used only by the bootstrapper, long before that the file system is initialized.

  Your problem is 70 errors in disk0 tranche 2, the volume Macintosh HD. This hard drive (the entire disc) was his. Dead. in ruins. You need a new drive.

• Partition missing Bootcamp after sleeping

  Hi guys,.

  I have the following problem. I have a Macbook Pro with OS X El Capitan 10.11.5 on it. I have multi boot, with 8.1 Windows it still works well, but I was in need of some extra HARD drive space on my OS X partition, so I was sleeping with a partitioner of third party and deleted by mistake a 200 MB required (I think than EFI) partition. After that, I was not able to boot to OS X, only point 8.1 Windows

  After a while of playing with it, I suddenly could start under OS X new. But, when I press the Option key at startup, my Bootcamp partition has now disappeared all of a sudden. When I went back to OS X and checked with disk utility, I could see the Bootcamp partition. Also in the floppy start, but when I chose the Bootcamp partition as boot drive and the Macbook restarted, I got the 'no such device' error while trying to boot Windows.

  So, I completely messed up something. I tried Windows recovery (reboot), but after this was not a success either, the whole Bootcamp partition is now gone when I check the disc utilities. So, maybe someone can help? Here are a few screenshots:

  

  

  

  

  Thank you very much in advance!

  Make no mistake.

  The partition GUID type is incorrect. What is the year/model of your Mac?

  Please download GPT Fdisk from https://sourceforge.net/projects/gptfdisk/ and install it. It will help you to correct the GPT.

• How to change the size of the protection GPT Partition

  I have a MacBook Pro (mid-2012) with 250 GB SSD. Next to OSX, I used BootCamp to install Windows 8 and then improved to 8.1 Windows and Windows 10. Everything worked well to 8.1 Windows but when I upgraded to Windows 10, she could not make backups of image. Support Microsoft informs me that it is because the size of protective Partition is too small and must be increased at least 300 MB to 200 MB to reach its current size. Here's my current disk configuration:

  View of MAC:

  #: NAME SIZE TYPE IDENTIFIER

  0: GUID_partition_scheme * GB 251,0 disk0

  1: disk0s1 EFI EFI 209.7 MB

  2: Apple_HFS Macintosh HD 100.0 GB disk0s2

  3: disk0s3 Apple_Boot Recovery 650.0 MB HD

  4: Microsoft database BOOTCAMP 150,0 GB disk0s4

  Windows display:

  1 - protection GPT partition Partition - 200 MB

  Partition 2 - d: Partition first, HFS - 100 GB (this is where OS x is installed)

  Partition 3 - primary partition - 620 MB (no idea what it is and how it got underway)

  4 - C: partition BootCamp - NTFS - 139,83 GB

  The OSX partition has plenty of space available (61GB). My knowledge of Mac OS x is very limited. I don't want to do something that could make the system unbootable or require reinstallation of the operating system and its applications. How to resize this partition to provide a space for the GPT partition resizing?

  Thank you for looking into this.

  It seems that what Microsoft calls GPT partition protection is the EFI partition in OSX. Wonder why its size limits the ability of Windows 10 to backup image.

• How can I perform a clean installation of Mac OS x for my iMAC, retina 5K late 2014 with drive of Fusion with the intact Recovery HD partition?

  How can I perform a clean installation of Mac OS x for my iMAC, retina 5K late 2014 with drive of Fusion with the intact Recovery HD partition?

  Pure how to install OSX on a Fusion drive and keep the recovery disc function

  These instructions assume that your iMAC partitions or file systems has been damaged and you want to restore to the way most efficiency with fusion drive and the recovery partition, similar to what was built in the factory.

  These instructions work for the iMAC, retina 5K end 2014 version comes with OSX Yosemite. The scores of major drive of the 128 G SSD and 3 TB of HARD drive has been configured as a logical drive (merger by car).

  WARNING: These instructions here are shared for interest only. Readers to take their own risk by following these instructions. The author is not responsible for any damage caused by following these instructions.

  This is the target disk partitions, and the configuration that we want to achieve.

  Disk0 is the 128 GB SSD - solid state drive and holds the start of the partition (disk0s3)

  Disk1 is the 3.0 to HDD - mechanical transmission and holds the Recovery HD partition.

  There are two EFI partitions to partition table GUID on both hard drives (disk0s1, disk1s1).

  Disk space remaining (partition disk0s2 and disk1s2) are used to create the disc of Fusion 3.1 to named "Macintosh HD".

  / dev/disk0 (internal, physical):

  #: NAME SIZE TYPE IDENTIFIER

  0: GUID_partition_scheme * GB 121,3 disk0

  1: disk0s1 EFI EFI 209.7 MB

  2: Apple_CoreStorage GB LVG 121.0 disk0s2

  3: disk0s3 Apple_Boot Boot OS X 134,2 MB

  / dev/disk1 (internal, physical):

  #: NAME SIZE TYPE IDENTIFIER

  0: GUID_partition_scheme * 3.0 to disk1

  1: EFI EFI 209.7 MB disk1s1

  2: disk1s2 Apple_CoreStorage TB 3.0 LVG

  3: disk1s3 Apple_Boot Recovery 650.0 MB HD

  / dev/disk2 (internal, virtual):

  #: NAME SIZE TYPE IDENTIFIER

  0: Apple_HFS Macintosh HD + 3.1 TB disk2

  Logical volume on disk0s2, disk1s2

  0D807F6E-FB7C-418F-AAF4-EF3EA3525D10

  Fusion unencrypted drive

  Here's how we do it.

  • A. clean reinstallation of Mac OS x.
  • 1. make sure that you back up all your data on the hard drive using Time Machine or other means. The following procedure will delete all data.
  • 2. create the OSX install USB, insert it to the MAC workstation.
  • 3. given that us will be operated on the internal trunk of the reader of the Mac, it must start on OSX install USB (see Y.).
  • 4. in the menu at the top of the screen, select disk utilities.
  • 5. turn highlighted the volume of disk Fusion called "Macintosh HD." Click clear to clean.
  • 6. If his success, then go ahead to install OSX new to that partition, as usual.
  • 7. otherwise, if it does not, that means fusion drive has been damaged.
  • 8 follow the instructions below to fix it.
  • . B. Split disc Fusion in the physical hard disks
  • 1. Since us will be operated on the internal drive of the Mac trunk, assumes that we already have boot up OSX install USB drive (see Y.).
  • 2. in the menu at the top of the screen, select utilities and Terminal.
  • 3. on the screen of the terminal type:
  • Cs diskutil list.
  • You will see something similar to the screen below.
  • 4 copy the long string after Logical Volume and replace the UUID with it in the following command to delete the logical volume of the disc fusion (aka coreStorage of logical volume):
  • diskutil deletevolume cs UUID
  • For example:
  • diskutil deletevolume E59B5A99-F8C1-461A-AE54-6EC11B095161 cs
  • 5 copy the long string after the logical volume group and replace the UUID with it in the following command to remove the drive (aka coreStorage) fusion:
  • diskutil cs remove UUID
  • p. ex. diskutil cs remove E03B3F30-6A1B-4DCD-9E14-5E927BC3F5DC
  • 6. at this stage, the fusion drive has been deleted, and hardsisk SSD and mechanical hard drive will be reappear in diskutil or separate records.
  • 7. If step 5 or 6 takes more than 30 minutes to complete, this means that the fusion drive has been corrupted. You can follow the commands below to clear the table to partition the hard way. First command clears the SSD drive, second command erases the HARD drive.
  • The command does not return a response, after 1 minute, press Ctrl + Z to complete orders. 1 minute is enough data to code and erase the partition table on the disk.
  • cat/etc/random >/dev/disk0
  • cat/etc/random >/dev/disk1
  • . C install a new copy of Mac OS x for the hard drive HDD and tested this disk partition hard recovery work.
  • 1. go on diskutil to create a partition called Macintosh HD HDD hard drive using all the space there.
  • 2 do the same with the mechanical hard drive.
  • 3. follow the usual procedure to boot from the installation of OSX USB and install a new copy of Mac OS x hard disk SSD.
  • 4. This will create the correct priming of the partitions, recovery hard drive partitions and PSX partitions hard disk HDD.
  • 5. once the installation is complete, test if OSX may start successfully, but no need to go through the initial MAC OS x didn't put in place that we're going to waste this and do the installation again later.
  • 6. we must now test if the recovery hard drive partition works.
  • 7. reboot for hard drive recovery (see X - by pressing command and R at the same time during boot right after that you hear sound start and release only a few seconds after you see the apple logo and the progress bar for loading...)
  • 8. it is important to test and make sure that the partition of hard drive recovery.
  • D. recreate the fusion drive
  • 1 since us will be operated on the internal trunk of the reader of the Mac, it must start on OSX install USB (see Y.).
  • 2. in the menu at the top of the screen, select utilities and Terminal.
  • 3
  . on the screen of the terminal type:
• diskutil list.
• You should find that we have a list of disk group hard physical volume only, no logic here still.
• 4. you will see something similar to the screen below.
• 5. search for the largest partition on the SSD hard drive, which should be close to the maximum size of HDD to the SSD (121 G, for example) and mark the name of the device, this will usually be something like/dev/disk0s2
• 6. search the largest disk partition mechanical forming fusion with the SSD hard drive. This should be close to the maximum size of the mechanical hard drive (for example 3 TB) hard disk and mark the name of the device, this will usually be something like/dev/disk1s2
• 7
. Now let's create the merger in car (group alias logical volume) in the Terminal, type: diskutil cs create nom_lecteur driveIDs
• The number of the driveIDs is unlimited, it may be a number of discs, or a number of disk partitions. Always put the faster discs first, for example for our SSD disk0s2
• For example:
• diskutil cs create fusiondrive disk0s2 disk1s2
• diskutil - the version of disk utility command line.
  cs - This calls for Core Storage, which is necessary for the merger.
  create - creates a basic storage group.
  nom_lecteur - is the name of the drive and how you want that he
• appear in the disk utility (not the Finder - that comes later). You can call it what you like; in our example, we named our Fusion table "Fusion".

driveIDs - Here is the Player IDs of the readers you want as part of your Fusion table, separated by a space. In our example, they are 'disk0' and 'disk1', but it may be different in your configuration.
• It is important that the faster hard drive appears first in the command, which in our case the disk0s2 (a partition in the SSD). In this way, drive fusion will use this disk as primary and the cache. The second disc in the command, in this case disk1s2 (a partition on the HARD disk). The secondary disk (HARD drive) is used to store less frequently used files.  Otherwise, the fusion drive performance will be worse that it is designed for.
• 8. you will see something like below appear on the screen:
• Creation Volume logical storage of kernel
• Move isk0s2 storage of carrots
• Disk1s2 of switching for the storage of carrots
• Waiting for logical volume group appear
• Discovered the new group of logical volumes 'DBFEB690-107B-4EA6-905B-2971D10F5B53 '.
• Store LVG UUID: DBFEB690-107B-4EA6-905B-2971D10F5B53
• Finished CoreStorage operation
• 9 copy to the bottom of the string after "Discovering new Volume Logic Group" using the command + C
• 10. next, create the partition of the merger (alias logical volume) drive named "Macintosh HD".
• In the Terminal, type: diskutil createVolume groupString jhfs cs + size volumeName
• For example:
• Diskutil createVolume DBFEB690-107B-4EA6-905B-2971D10F5B53 jhfs cs + 'Macintosh HD' 100%
• diskutil - once again, this is the version of disk utility command line.
• cs - called the basic storage functions, which are necessary for this arrangement.
• createVolume - this is the command to create the storage area real for the reader who is represented by an icon on your desktop.
• groupstring - this is the long alphanumeric string you copied in the previous step. It identifies the table you created such as getting a volume placed on it.
• jhfs + -the format of the disc. It is Apple (journaled) extended Format, which is recommended for drives with an operating system installed on it.
• VolumeName - the actual name of the volume, how it should appear under the icon. If there is a space in the name, you must put the full name in quotes ("name") or put a slash before the (name Drive\) space. In our example, we made these, naming our volume "Macintosh HD".
• size : this is the size of the volume. In our example, we had a 1.1 TB drive. We used '1100g' to describe what 1100 GB (1.1 TB to base 10). Otherwise, we could have also used 1.1 T or even 100% as a size.
• 11. go to diskutil to verify that you can see this new partition on the list.
• 12. test by erasing all the data from it.
• 13. then you can go ahead to start on the USB drive to install OSX and install a new copy of Mac OS x on it.
• 14. This will allow you to keep the recovery disk feature.
• X. how Prime to recover partition
• Press and hold the command and button R set immediately after hearing the bells to boot.
• Only release it 2 seconds after you see the Apple logo on the screen and the progress bar for the start. This will start the partition of hard drive recovery.
• Y. how-to boot OSX install USB
• Press and hold the command and the optionkey together immediately after hearing the ringing of boot.
• Only release it 2 seconds after you see the Apple logo on the screen and it will give you a list of startup disk choice, choose the OSX install USB to boot from.

• Satellite Z930 - question on Win8 SSD partitions

  Just got the new Z930 satellite with the following 128 GB SSD partitions

  450 MB recovery partition
  260 MB EFI system partition *.
  9.66 Gb recovery partition
  Primary partition 8 GB *.
  100.76 GB boot, page file, crash dump, primary partition *.

  Only those that are marked with * are allowed to be deleted using the windows disk management tool.

  I'm assuming that the 8 GB partition is the recovery for a factory restore media. I intend on creating recovery media of course USB (9Gbrequired according to the creator of recovery media - 16 Gb USB recommended). Delete this partition, and then expand the main partition.

  Questions:

  1. someone knows what is the 9.66 GB partition and why it cannot be deleted? Possibly put into hibernation linked, but why 9.66 when there are only 6 GB of RAM installed (which would make the hibernation 4 GB partition)

  2. What is the EFI partition for?

  3. it is curious that if you take 4 GB (what the file hibernation for 6 GB of RAM should be) the 9.66 5,66 remaining and the score of 8 GB are basically the same size as the main 13.5 GB partition reported here for the z930 portege. Why Toshiba would squirrel away from the recovery media as well as space for hibernation? A way to recover the full 13.5 GB asmentioned in the z930 portege post?

  Thanks in advance

  > 1. Anyone know what is the 9.66 GB partition and why it cannot be deleted? Possibly put into hibernation linked, but why 9.66 when there are only 6 GB of RAM installed (which would make the hibernation 4 GB partition)

  I guess that the 9.66 GB partition called recovery partition is created for HARD drive recovery.
  You can retrieve the laptop using recovery of HARD drive and does not require recovery or recovery USB memory stick drive.
  But I wouldn't delete this partition because you will lose the ability to recover the HARD drive recovery unit

  > 2. What is the EFI partition for?
  EFi partition contains the program loader initialization for all the operating systems (in other partitions) on the HARD disk. If don t touch.

• Satellite 855D-S5120 - wouldn't boot efi file on the HARD drive

  I had no problem to boot from a usb port or a live cd in grub or gummiboot, but I was not able to do the same with the hard drive.

  The NVRAM settings are not persistent. I was able to set a uefi shell using the two Jean efibootmgr or significant, but they are reset to zero when you restart.

  I was able to initiate gummiboot out of USB by renaming the BOOTX64.efi file

  My efi partition is fat32 and marked as boot-able. I understand that some implementations of UEFI aren't complete implementations by the UEFI specification. which I think is the case here.

  Since the NVRAM apears does not have to be definable. I need to know where and what this implementation is looking for hard disk. Someone at - it the answer?

  Hello

  I'm not sure that understand your problem.

  You are installing a U/EFI OS on the HARD drive but is unable to do start?

  I myself 13.04 successfully installed Ubuntu and Fedora 18/19, the start of UEFI.
  Of course, the installers to take care of the difficult things for me so I know little about these details.

  Please specify what you want to achieve, and let's see if I can be of any assistance.

  Tom BR

• Bootcamp for repair after changing partitions in El Capitan

  (For a better format version, please visit this link.) I did have luck with answers on itself)

  I wanted to create a shared partition that I could access between my install Bootcamp and OS X I have been on Yosemite and utility disk would allow me to resize or create new partitions, but I heard that I could do it by upgrading to El Capitan.

  It worked well, I could reduce my OSX partition and create a new partition with the remaining space, however, when I try to start directly in my bootcamp partition running Windows 8.1, I now get an error:

  
  Your PC needs to be repaired 
  
  An unexpected error has occurred. 
  
  Error code: 0xc000000e 
  

  According to some messages that I found, this may indicate that the hybrid MBR is damaged and needs to be recreated, so I tried this by following this link.

  I also tried to boot into a Windows and running recovery disk

  bootrec /rebuildbcd 

  but it does not work. It returns

  The requested system device cannot be found. 

  So, looks like it has something to do with my EFI partition, because according to other messages, maybe I need to assign a drive letter to the EFI partition, but it does not appear when I use diskpart. I see the output similar to:

  
  > list vol 
  
  Volume ### Ltr Label        Fs  Type      Size    Status 
  
  ---------- --- ------------ ----- --------- -------- ---------- 
  
  Volume 0 E IRV_CCSA_X6      UDF  DVD-ROM  4120 MB  Healthy 
  
  Volume 1 C BOOTCAMP        NTFS  Partition 93 GB    Healthy 
  
  Volume 2 D Removable                        0 B      No Media 
  

  However, I think that's because I see when I run diskutil in OS x:

  
  $ diskutil list 
  
  /dev/disk0 (internal, physical): 
  
   #: TYPE NAME SIZE IDENTIFIER
  
  0: GUID_partition_scheme *500.3 GB disk0
  
  1: EFI EFI 209.7 MB disk0s1
  
  2: Apple_CoreStorage Macintosh HD 340.5 GB disk0s2
  
  3: Apple_Boot Recovery HD 650.0 MB disk0s3
  
  4: Microsoft Basic Data Storage 58.7 GB disk0s4
  
  5: Microsoft Basic Data BOOTCAMP 100.1 GB disk0s5
  
  /dev/disk1 (internal, virtual):
  
  #: TYPE NAME SIZE IDENTIFIER
  
  0: Apple_HFS Macintosh HD +340.1 GB disk1 Logical Volume on disk0s2 E516E87A-D86D-459A-904F-FD299B379969 Unencrypted
  

  I even tried refined, that doesn't seem to change anything.

  Another note, my Windows partition is fine, because I can always start using Parallels, just a direct start in Bootcamp is not.

  I am quite confused where to go from here. Nothing seems to work and I've tried several dozen approaches with no luck. How can I fix Bootcamp?

  Article Nerder is one of the worst possible solutions and causes more data loss. It also provides a clear warning. Can you post the output of the following OS X Terminal commands?

  diskutil list

  Cs diskutil list

  sudo TPG - vv - r see the/dev/disk0

  sudo fdisk/dev/disk0

  The "sudo" commands will prompt to enter your password, and there do not appear to come back. You can also see caution against improper use 'sudo' and the potential loss of data due to an "abuse" of the order.