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

windows 10 installed via bootcamp does not boot after cloning harddrive

I am using a late 2012 Mac mini with a triple boot Catalina + windows 10 + linux. I uses refind as boot manager. I cloned my 256GB hard drive to a 512GB one, linux and Mac OS are booting fine. Windows however get stuck on a blinking cursor.


The bootcamp partition is mounted and visible in finder.


I have seen a few questions mentioning the use of gdisk to fix related problems. I want to give it a try but I am not sure of the correct settings:


Here is the output of gdisk for my system:


GPT fdisk (gdisk) version 1.0.8



Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

  MBR: protective

  BSD: not present

  APM: not present

  GPT: present



Found valid GPT with protective MBR; using GPT.



Command (? for help): p

Disk /dev/disk1: 976773168 sectors, 465.8 GiB

Sector size (logical): 512 bytes

Disk identifier (GUID): D96994EC-DC95-448F-8813-6BAB9472962F

Partition table holds up to 128 entries

Main partition table begins at sector 2 and ends at sector 33

First usable sector is 34, last usable sector is 976773134

Partitions will be aligned on 8-sector boundaries

Total free space is 476655927 sectors (227.3 GiB)



Number  Start (sector)    End (sector)  Size       Code  Name

   1              40          409639   200.0 MiB   EF00  EFI System Partition

   2          409640       248454879   118.3 GiB   AF0A  Systeme

   3       248455168       249503742   512.0 MiB   EF00  

   4       373456896       500117503   60.4 GiB    0700  

and here is fdisk's:

eniac314@Mac-mini-de-eniac314 ~ % sudo fdisk /dev/disk1  

Password:

Disk: /dev/disk1 geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

         Starting       Ending

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

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

 1: EE    0   0   2 - 1023 255  63 [         1 -  976773167] <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   

Any help appreciated :)

Posted on Jun 16, 2021 9:51 AM

Reply

Similar questions

13 replies

Jun 17, 2021 8:08 AM in response to eniac314

  • Is disk1s3 the EFI for disk1s4 Linux installation?
  • A MBR only supports 4 entries.
    • disk1s5 is usually the last (4th) entry in the standard Bootcamp layout on macOS Sierra and older.
    • disk1s3 is normal location on macOS High Sierra and layer versions.
  • If Linux can be re-installed or moved to an external disk, it will make the MBR a standard layout. This also allows Windows to be repaired in the future, if necessary.


Jun 17, 2021 9:29 AM in response to eniac314

  • If you do not need to natively boot Linux, but can use a VM, consider that as an option.
  • If you are willing to remove/re-install Windows and Linux, then
    • install Linux, but use the existing EFI, instead of using a separate EFI
    • install Windows as legacy BIOS
  • The layout then becomes
    • EFI - disk1s1 - MBR1
    • macOS - disk1s2 - MBR2
    • Linux - disk1s3 - MBR3
    • Windows - disk1s4 - MBR4

Jun 17, 2021 9:43 AM in response to Loner T

I am not sure I could have used the existing EFI partition for linux - I am using pop_os and aparently it requires a 512mb EFI partition, that's why I made a second one, as suggested there.


I would like to keep linux even if I have to reinstall windows.


So if I can resize the existing linux partition while keeping the system the layout would then become:

  • disk1s1 EFI - MBR1
  • disk1s2 APFS - MBR2 Mac os
  • disk1s3+disk1s4 (resized) - MBR3 Linux pop_os
  • disk1s5 - MBR4 (Bootable for legacy BIOS) windows on a 100GB partition at the end


I think I can use linux to delete the current disk1s5 and disk1s6, resize disk1s4, leave 100GB unassigned space and then reboot in mac os to do the windows install with bootcamp.


Would this work?



Jun 17, 2021 10:16 AM in response to eniac314

eniac314 wrote:

I am not sure I could have used the existing EFI partition for linux - I am using pop_os and aparently it requires a 512mb EFI partition, that's why I made a second one, as suggested there• .

If PopOS requires a larger EFI, my suggestion then is to

  • backup macOS via Time Machine
  • wipe the disk and manually create a 1-2GB EFI and restore macOS using a Time Machine backup
  • install PopOS using the 1-2GB EFI, which will support both macOS and PopOS
  • Windows, by default creates a 104MB EFI, which may be insufficient
I would like to keep linux even if I have to reinstall windows.

You may also be able to backup/restore PopOS.

So if I can resize the existing linux partition while keeping the system the layout would then become:
disk1s1 EFI - MBR1
• disk1s2 APFS - MBR2 Mac os
• disk1s3+disk1s4 (resized) - MBR3 Linux pop_os
• disk1s5 - MBR4 (Bootable for legacy BIOS) windows on a 100GB partition at the end

I do not recommend using Linux to mess with partitions.

I think I can use linux to delete the current disk1s5 and disk1s6, resize disk1s4, leave 100GB unassigned space and then reboot in mac os to do the windows install with bootcamp.

You will also need to create a MBR, before you can install Windows. This would need GPT Fdisk to derive a MBR from the new GPT, which would have a 1-2GB EFI. macOS has a default of 200MB EFI, but you can create one manually of the size you need.


This would result in

  • EFI - 1-2GB
  • macOS - 127 GB
  • Linux - 240GB
  • Windows - 128GB (100GB may be insufficient, especially on newer releases)

Jun 16, 2021 1:05 PM in response to Loner T

The other EFI partition was needed for linux I think. I know I have free space left, I'll get to it once the windows problem is fixed.



eniac314@Mac-mini-de-eniac314 ~ % diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS DATA                    250.2 GB   disk0s2

   3:           Linux Filesystem                         209.7 GB   disk0s3

   4:       Microsoft Basic Data                         540.1 GB   disk0s4



/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                 Apple_APFS Container disk2         127.0 GB   disk1s2

   3:                        EFI NO NAME                 536.9 MB   disk1s3

   4:       Microsoft Basic Data BOOTCAMP                64.9 GB    disk1s4

   5:       Microsoft Basic Data                         63.5 GB    disk1s5



/dev/disk2 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +127.0 GB   disk2

                                 Physical Store disk1s2

   1:                APFS Volume System - Données        7.4 GB     disk2s1

   2:                APFS Volume Preboot                 104.2 MB   disk2s2

   3:                APFS Volume Recovery                1.0 GB     disk2s3

   4:                APFS Volume VM                      2.1 GB     disk2s4

   5:                APFS Volume System                  11.2 GB    disk2s5

Jun 16, 2021 10:52 PM in response to Loner T

Ok I made a new partition. here are the new output from gdisk:


GPT fdisk (gdisk) version 1.0.8



Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

  MBR: hybrid

  BSD: not present

  APM: not present

  GPT: present



Found valid GPT with hybrid MBR; using GPT.




Command (? for help): O

This option deletes all partitions and creates a new protective MBR.

Proceed? (Y/N): N

Command (? for help): P

Disk /dev/disk1: 976773168 sectors, 465.8 GiB

Sector size (logical): 512 bytes

Disk identifier (GUID): D96994EC-DC95-448F-8813-6BAB9472962F

Partition table holds up to 128 entries

Main partition table begins at sector 2 and ends at sector 33

First usable sector is 34, last usable sector is 976773134

Partitions will be aligned on 8-sector boundaries

Total free space is 311 sectors (155.5 KiB)



Number  Start (sector)    End (sector)  Size       Code  Name

   1              40          409639   200.0 MiB   EF00  EFI System Partition

   2          409640       248454879   118.3 GiB   AF0A  Systeme

   3       248455168       249503742   512.0 MiB   EF00  

   4       249503744       373456894   59.1 GiB    0700  

   5       373456896       500117503   60.4 GiB    0700  

   6       500117504       976773119   227.3 GiB   0700  


diskutil list /dev/disk1:

/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                 Apple_APFS Container disk2         127.0 GB   disk1s2

   3:                        EFI NO NAME                 536.9 MB   disk1s3

   4:       Microsoft Basic Data                         63.5 GB    disk1s4

   5:       Microsoft Basic Data BOOTCAMP                64.9 GB    disk1s5

   6:       Microsoft Basic Data Spare                   244.0 GB   disk1s6


What should I do now?

Jun 17, 2021 9:05 AM in response to eniac314

Given the current layout, to create an MBR would require


disk1s1 EFI - MBR1

disk1s2 APFS - MBR2

disk1s3+disk1s4 - MBR3

disk1s5 - MBR4 (Bootable for legacy BIOS)


However, if you want to use the disk space in disk1s6, you will need to use GParted to combine the current disk1s5+disk1s6 into a new disk1s5.


Linux and macOS should boot using EFI. Be careful if you ever need to repair Windows. Do not use any other tools except GParted and GPT Fdisk. MPT should never be used on a Mac.

Jun 17, 2021 9:20 AM in response to Loner T

So if i combine disk1s5+disk1s6 into a new disk1s5 it will end up extending the windows partition?


Hypothetically could it be possible to delete the windows install, extend the linux partition disk1s4 so that it leaves about 100GB at the end of the disk and then reinstall windows via bootcamp in this 100BG space?


As linux is my daily driver I'd rather have it on the biggest space.

Jun 18, 2021 4:58 AM in response to Loner T

So after trying a clean install of Catalina, Windows 10 (directly from the installer usb, without bootcamp), pop_os and refind in that order, I had Mac OS and windows booting fine at first but the linux and/or refind install screwed things up and windows refused to boot from refind ( BlinitializeLibrary failed 0xc00000bb).


I restored the cloned partition from the old 256GB drive with clonezilla, extended the windows partition from linux gparted, which then apparently let Mac OS detect the whole 500GB and got the 3 systems booting back.

Here is the new layout:


/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         127.0 GB   disk1s2
   3:                        EFI NO NAME                 536.9 MB   disk1s3
   4:       Microsoft Basic Data BOOTCAMP                308.9 GB   disk1s4
   5:       Microsoft Basic Data                         63.5 GB    disk1s5


I have too much space on my windows partition but it'll have to do for now. I am clearly out of my depth here, I will have to do some more research on the different types of boot before I make any more potentially breaking changes.


I disabled the hibernation in windows because I read it could prevent it from booting in refind. Is there anything else I need to watch out for that could cause the boots to break again?


Thank you very much for your help!

windows 10 installed via bootcamp does not boot after cloning harddrive

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