Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Booting into BIOS from bootcamp

After having created a bootcamp partition, I realized my original partition size was too small. To repartition I decided to start from scratch and remove the old partition and start a new partition, planning on using a system image to restore the backup of my old bootcamp. All went pretty smoothly until I was trying to use the restore and it told me:


"To restore this computer Windows needs to format the drive that the Windows Recovery environment is currently running on. To continue with the restore shut down this computer and boost it from a Windows installation disc or a system repair disc and then try the restore again."

In light of that, I made a system repair disc in the form of a usb; however, now I can't get into the BIOS menu in order to change the boot order to boot the usb in the first place.

Help...! I've been at this for hours and can't seem to find a way. The UEFI "tile" for booting is also not appearing so I can't boot it up that way, and I apparently can't press F2 fast enough to boot into BIOS that way either. I've ran a bcdedit in command which came back that it is .edi so it should be able to boot but I don't know how....

If anyone has come across this problem and knows a solution that would be greatly appreciated.

MacBook Pro with Retina display, OS X Yosemite (10.10.1)

Posted on Feb 17, 2015 11:17 PM

Reply
Question marked as Top-ranking reply

Posted on Feb 18, 2015 5:56 AM

Macs do not run BIOS, but use a compatibility layer called CSM-BIOS. There is no user interface. CSM-BIOS builds the boot device list on the fly based on what is currently plugged in.

acperry7 wrote:


In light of that, I made a system repair disc in the form of a usb; however, now I can't get into the BIOS menu in order to change the boot order to boot the usb in the first place.


Boot into OS X .

Plug-in your Windows USB Repair Disk.

Go To System Preferences -> Startup Disk.

Select your Bootcamp Windows (not your USB Repair).

Click on Restart.

Windows should boot from you USB.


Here is an example of W7 Recovery using USB - https://imgur.com/a/1DaOE#0.

25 replies
Sort By: 
Question marked as Top-ranking reply

Feb 18, 2015 5:56 AM in response to acperry7

Macs do not run BIOS, but use a compatibility layer called CSM-BIOS. There is no user interface. CSM-BIOS builds the boot device list on the fly based on what is currently plugged in.

acperry7 wrote:


In light of that, I made a system repair disc in the form of a usb; however, now I can't get into the BIOS menu in order to change the boot order to boot the usb in the first place.


Boot into OS X .

Plug-in your Windows USB Repair Disk.

Go To System Preferences -> Startup Disk.

Select your Bootcamp Windows (not your USB Repair).

Click on Restart.

Windows should boot from you USB.


Here is an example of W7 Recovery using USB - https://imgur.com/a/1DaOE#0.

Reply

Feb 19, 2015 7:17 PM in response to acperry7

You can see the gpt using sudo gpt -vv -r show /dev/disk0. The Fdisk entry you posted is called a protective MBR.


On all Macs (rom about 2006+), all disks are GPT (APM was used before that which transitioned around Leopard/Snow Leopard time frame).


http://www.rodsbooks.com/gdisk/hybrid.html

https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/gpt.8.html

http://www.mactech.com/articles/mactech/Vol.23/23.03/APMtoGPT/index.html

Reply

Feb 18, 2015 9:15 AM in response to Loner T

Oh man, thanks for the response. This was driving me crazy last night. I came across the start-up disk option but figured that it wouldn't boot properly to the usb because it was being run from the Mac OS side and that it would just boot up regular windows. I will try this when I get home tonight and update.

Reply

Feb 18, 2015 5:51 PM in response to Loner T

Hey Loner T,


So basically I was able to get my usb to boot, but not by using the startup disk method but simply holding the option button when booting; however, when I tried to run my system re-image it came up with this error:


"The system image restore failed. Windows cannot restore a system image to a computer that has different firmware. The system image was created on a computer using EFI and this computer is using BIOS."


I reinstalled windows to my bootcamp partition with the bootcamp assist the exact same way I did it the first time. The only oddity I found here was that when I had the option of running the USB I had two options:

1. "Windows"

2. "EFI"


Running Windows made it seem like all was working until I came to the error mentioned above. Running EFI did not work at all, it basically blue screen'd me and told me how something was wrong and that my PC needed to be repaired. It also gave me the options of "Other setup options" clicking F8 but it was non-responsive and sort of flicked when I pressed F8. After about a minute or so, the computer shut down.


Any idea what to do here? Would it be worth it reinstalling windows again or is this a problem between running Windows alongside a Mac OS?

Reply

Feb 18, 2015 6:34 PM in response to acperry7

What year/model is your Mac?

What is the version of Windows?

Was the old partition removed and new one created using Bootcamp Assistant or Disk Utility?


On newer (2013+) Macs, windows can be installed using EFI or MBR. MBR is the legacy (old method) and is equivalent to BIOS on a PC. EFI is the newer method and does not use a MBR. W8+ support EFI.


Resizing a Windows partition is not permitted when using the MBR method. It requires a re-install of Windows from scratch. Restoring a Windows Image backup to a larger partition is problematic on Macs. If you can, I suggest re-installing Windows from scratch. If you Mac is a late 2013 model, I recommend using the EFI method.

Reply

Feb 18, 2015 7:01 PM in response to Loner T

I got it early 2015 which I think means it is a mid 2014 15' Retina Macbook Pro. The Windows is 8.1 Pro. I removed the old partition via Bootcamp Assistant.


I basically made a USB to install windows 8.1 in the first place, all ran well but decided to re-partition. So I removed the old partition via bootcamp, made a new, bigger partition, then reinstalled windows using the same USB I made the first time around and it installed without a hitch, but now I can't seem to use the system image I made on an external hard drive.


If I installed using the same method, does that mean I'm give nan option to install windows using EFI or MBR? I didn't try resizing the bootcamp partition because I was worried that if I did so, I would end up corrupting a partition and be unable to use it so I decided to play it safe. Is there any way to for sure tell that I am using MBR? That would mean I somehow managed to install EFI the first time but MBR the second (?)

Reply

Feb 18, 2015 7:22 PM in response to Loner T

Okay so I ran MsInfo32 in "Run" and it said that for my BIOS I am running UEFI and not Legacy. So, now I'm guessing it something to do with the USB bootable that I made or the way that it is running. I made the recovery drive right out Windows which is puzzling why it is not working properly...


Are there any alternative ways to make a recovery drive using a USB?

Reply

Feb 18, 2015 7:33 PM in response to acperry7

acperry7 wrote:


I got it early 2015 which I think means it is a mid 2014 15' Retina Macbook Pro. The Windows is 8.1 Pro. I removed the old partition via Bootcamp Assistant.

It supports UEFI, so a Bootcamp Assistant is really not necessary.



I basically made a USB to install windows 8.1 in the first place, all ran well but decided to re-partition. So I removed the old partition via bootcamp, made a new, bigger partition, then reinstalled windows using the same USB I made the first time around and it installed without a hitch, but now I can't seem to use the system image I made on an external hard drive.

The USB (and the underlying Windows DVD/ISO) supports both methods, EFI and MBR. It depends whether the Alt key was used and Windows (BIOS) or EFI Boot (EFI) was chosen.

If I installed using the same method, does that mean I'm give nan option to install windows using EFI or MBR? I didn't try resizing the bootcamp partition because I was worried that if I did so, I would end up corrupting a partition and be unable to use it so I decided to play it safe. Is there any way to for sure tell that I am using MBR? That would mean I somehow managed to install EFI the first time but MBR the second (?)

You can check by looking at the output of sudo fdisk /dev/disk0. More than one entry indicates MBR (usually 4 entries) are expected.

Reply

Feb 18, 2015 7:48 PM in response to acperry7

acperry7 wrote:


Okay so I ran MsInfo32 in "Run" and it said that for my BIOS I am running UEFI and not Legacy. So, now I'm guessing it something to do with the USB bootable that I made or the way that it is running. I made the recovery drive right out Windows which is puzzling why it is not working properly...


Are there any alternative ways to make a recovery drive using a USB?

The error messages during the restore indicate you used EFI initially, which means BCA created the MBR (and the supporting GPT entries), but by choosing the EFI boot, the MBR was ignored. Subsequent install was done using the MBR, and the System Image cannot be crossed across EFI and MBR. A System Image restore on a Mac has other challenges like partition sizes, MBR recreation, etc.


Do you have data on the old System Image you want restored? If yes, use EFI Boot (without using BCA) by creating a GPT partition using Disk Utility of the size you want (I use Free Space), install Windows using EFI boot, then try a image restore. Since the image restore already has BC drivers, you will not need to re-install them (provided the image included the BC drivers to allow proper functioning).


If it is not critical data, I suggest starting from scratch and installing EFI Windows for flexibility. MBR is rigid and resizing requires re-installation.

Reply

Feb 18, 2015 9:29 PM in response to Loner T

Ahhh okay. Yeah running the sudo fdisk /dev/disk0 in terminal showed 4 entries.

Ideally I just wanted to move all my settings and some data I had stored on my old partition onto the new one because I didn't think it would be a tedious task, but I also did not expect to run into all these problems. Ironically, trying to do the "clean wipe" has managed to create more problems than possibly using a repartition tool.

So what would my plan of action be in order to make it EFI Windows again (I have no idea how I made it MBR in the first place, unless it defaults that way when you use BCA a second time)?

Can I remove the bootcamp partition using BCA (again) or will this cause problems? Then, you're saying I should use EFI boot (instead) to create a new partition to install windows on? Then ideally that will make my windows the EFI windows it was the first time?

Again, thanks A TON for answering all these questions, I would be utterly lost without your guidance.

Reply

Feb 19, 2015 5:07 AM in response to acperry7

1. Since the current installation is MBR, use only Bootcamp Assistant, nothing else, and Remove Windows. Check the output of sudo fdisk /dev/disk0 to ensure there is a single entry. Please make a backup of OSX partition.

2. Go to Disk Utility. Create a partition of the size you want and format it as Free Space.

3. Plug-in your USB with Windows/BC Drivers.

4. Power cycle Mac and hold Alt key. Choose EFI boot (not Windows).

5. Choose the newly created Free Space partition (do not touch any other partition).

6. You will be prompted for NTFS formatting. The Free Space will be split into two partitions, MSR (128MB) and MSD. MSD will become the NTFS partition.

7. Once the Windows works, try your System Image Restore.

Reply

Feb 19, 2015 8:44 AM in response to acperry7

This is the disk layout from a 2013 rMBP running W8.1 64-bit in EFI mode. The highlighted entries are the MSR and MSD partitions on this Mac.


gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 977105059

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 487712920 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

488122560 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

489392096 32

489392128 262144 4 GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE

489654272 487450624 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

977104896 131

977105027 32 Sec GPT table

977105059 1 Sec GPT header



Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 977105059] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Reply

Feb 19, 2015 10:12 AM in response to Loner T



Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 977105059] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused


Woah wait, in your sudo fdisk /dev/disk0, you also have four entries too. Did you mean that the four entries had to be used? Because my current output depicts the same four entries with 3 of the 4 being unused as well. I can't recall the former output to indicate the MSR and MSD at the moment.

Reply

Feb 19, 2015 10:26 AM in response to acperry7

For an EFI installation, MBR is not used. The entire disk is encapsulated in the first MBR entry inside a Protective MBR. MSR/MSD are EFI constructs, not MBR sub-types. You can see it when you look at size, it has the whole disk.

Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

...

1: EE 1023 254 63 - 1023 254 63 [ 1 - 977105059] <Unknown ID>

Reply

Feb 19, 2015 6:55 PM in response to Loner T

Last login: Thu Feb 19 19:47:46 on console

Alexs-MacBook-Pro:~ Perry$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 490234751] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Alexs-MacBook-Pro:~ Perry$

This is my readout, which looks like it might already be in EFI? Unless the example you had was not an example of EFI?

How do you get the GPT readout?












Reply

Booting into BIOS from bootcamp

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.