CathalKilkenny
Level 1 (0 points)

Q: 0xc000000e Error on Windows after Partition Resize

Hi Guys,

 

So I have been facing this issue for the past couple of days, and have scoured these forums here and elsewhere trying to find a solution but no luck. I think I'm pretty close but need some help.

 

I had a bootcamp setup, with pretty much a 50/50 split on my disk space for windows 10 and OSX El Capitan.

I decided to shrink my OSX partition, so i could create Shared partition, in exFat to hold files that I would want to access between OSs. I thought this would be a cleaner solution than using a 3rd Party OSX app to read/write NTFS volumes.

 

Resize went well, created the new partition, and later went to boot into Windows and got startup error 0xc000000e.

 

Heres what I know:

 

  1. Windows shows up in 'Startup Disk' in Utilities.
  2. Windows appears in the boot menu when holding the alt key on boot.
  3. The NTFS Volume seems to be intact, and i can access files.

 

Im new to OSX and have been a heavy user of windows for many years, although going deep into OSX or Linux is alien to me.

 

I created a bootable windows usb and went into startup repair, navigating to the NTFS volume ran bootrec commands.

When running rebuild BCD it searched for OSs and found my windows installation, but when attempting to add it to the MBR i get the error 'The requested system device cannot be found.'

 

I removed the partition and extended the OSX partition to go back to where it was before the issue arose hoping that putting the partition table back the way it was might fix the problem. Unfortunately it didn't.

 

Below is the current outputs from diskutil and fdisk and gpt -vv commands.

 

I have tried many other things i could find on this forum but to no avail.

 

Thanks so much to anyone who can help me with this,

I dont want to have to do a full reinstall, and cant imagine that would be necessary given all files are accessible, as i have a lot of software needed for where i work, CAD software etc. and it would be awkward to get all of those configured properly again.

 

The PC is a 2015 Macbook Pro 15"

 

Thanks, Cathal.

 

Cathals-MacBook-Pro:~ codwyer$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *251.0 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:          Apple_CoreStorage Macintosh HD            149.4 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:       Microsoft Basic Data BOOTCAMP                79.3 GB    disk0s4

   5:           Windows Recovery                         471.9 MB   disk0s5

   6:       Microsoft Basic Data SWAP                    21.0 GB    disk0s6

/dev/disk1 (internal, virtual):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Macintosh HD           +149.0 GB   disk1

                                 Logical Volume on disk0s2

                                 863CB3BB-A6AB-4DAE-ADA3-05E638AC7DFA

                                 Unencrypted

/dev/disk2 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:     FDisk_partition_scheme                        *8.0 GB     disk2

   1:                 DOS_FAT_32 ESD-USB                 8.0 GB     disk2s1

Cathals-MacBook-Pro:~ codwyer$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group CC294E48-2B02-4AEA-B5B8-01B51E22AC6F

    =========================================================

    Name:         Macintosh HD

    Status:       Online

    Size:         149361356800 B (149.4 GB)

    Free Space:   8921088 B (8.9 MB)

    |

    +-< Physical Volume 5B650C2C-8DD7-4EE0-8E7B-5AD35807F33A

    |   ----------------------------------------------------

    |   Index:    0

    |   Disk:     disk0s2

    |   Status:   Online

    |   Size:     149361356800 B (149.4 GB)

    |

    +-> Logical Volume Family 35277226-FDE5-4762-B821-BCFBC8970258

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

        Encryption Type:         None

        |

        +-> Logical Volume 863CB3BB-A6AB-4DAE-ADA3-05E638AC7DFA

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

            Disk:                  disk1

            Status:                Online

            Size (Total):          149000114176 B (149.0 GB)

            Revertible:            Yes (no decryption required)

            LV Name:               Macintosh HD

            Volume Name:           Macintosh HD

            Content Hint:          Apple_HFS

Cathals-MacBook-Pro:~ codwyer$ fdisk /dev/disk0

fdisk: /dev/disk0: Permission denied

Cathals-MacBook-Pro:~ codwyer$ 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 -     409639] <Unknown ID>

2: AC 1023 254  63 - 1023 254  63 [    409640 -  291721400] <Unknown ID>

3: AB 1023 254  63 - 1023 254  63 [ 292131040 -    1269536] Darwin Boot

*4: 07 1023 254  63 - 1023 254  63 [ 293400576 -  154951680] HPFS/QNX/AUX

Cathals-MacBook-Pro:~ codwyer$ sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752

gpt show: /dev/disk0: Suspicious MBR at sector 0

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

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

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         32         Pri GPT table

         34          6        

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

     409640  291721400      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

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

  293400576  154951680      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  448352256     921600      5  GPT part - DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

  449273856   40957952      6  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  490231808       2911        

  490234719         32         Sec GPT table

  490234751          1         Sec GPT header

Cathals-MacBook-Pro:~ codwyer$

MacBook Pro (Retina, 15-inch, Mid 2015), OS X El Capitan (10.11.1), null

Posted on Dec 30, 2015 11:57 AM

Close
CathalKilkenny

Q: 0xc000000e Error on Windows after Partition Resize

  • All replies
  • Helpful answers

Previous Page 2

  • by Loner T,

    Loner T Loner T Jan 6, 2016 11:22 AM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 6, 2016 11:22 AM in response to CathalKilkenny

    C: on the legacy installations should map to BIOS hardware paths on disks. Let me dig why the EFI partition is giving us grief regarding a drive letter.

  • by Loner T,

    Loner T Loner T Jan 6, 2016 11:41 AM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 6, 2016 11:41 AM in response to CathalKilkenny

    Do you want to try this - http://superuser.com/questions/662823/how-do-i-mount-the-efi-partition-on-window s-8-1-so-that-it-is-readable-and-write ?

  • by CathalKilkenny,

    CathalKilkenny CathalKilkenny Jan 6, 2016 1:14 PM in response to Loner T
    Level 1 (0 points)
    Jan 6, 2016 1:14 PM in response to Loner T

    I have already seen that thread I'm afraid. I get the error "There is no volume specified, please select a volume and try again." I believe there is meant to be an associated volume with the partition or something which in this case isn't there.

     

    I can select partition 1, the EFI partition, but typing 'assign' afterward gives me the error above; and listing volumes, as I said, there is no sign of the EFI partition.

  • by CathalKilkenny,

    CathalKilkenny CathalKilkenny Jan 9, 2016 9:58 AM in response to Loner T
    Level 1 (0 points)
    Jan 9, 2016 9:58 AM in response to Loner T

    You didn't manage to get the BCD file I mentioned from another PC Loner T ?

     

    Tell me its not time to bite the bullet and backup and reformat ?

  • by Loner T,

    Loner T Loner T Jan 9, 2016 11:56 AM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 9, 2016 11:56 AM in response to CathalKilkenny

    Please wait till tonight. I should have access to the machine tonight.

  • by Loner T,

    Loner T Loner T Jan 9, 2016 6:50 PM in response to Loner T
    Level 7 (23,623 points)
    Safari
    Jan 9, 2016 6:50 PM in response to Loner T

    This is what I currently have...

     

    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device                  partition=\Device\HarddiskVolume1
    path                    \EFI\Microsoft\Boot\bootmgfw.efi
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    integrityservices       Enable
    default                 {ed9bfd8d-1558-11e4-b9d2-96781b9d737f}
    resumeobject            {ed9bfd8c-1558-11e4-b9d2-96781b9d737f}
    displayorder            {ed9bfd8d-1558-11e4-b9d2-96781b9d737f}
                            {ed9bfd89-1558-11e4-b9d2-96781b9d737f}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30

    Windows Boot Loader
    -------------------
    identifier              {ed9bfd8d-1558-11e4-b9d2-96781b9d737f}
    device                  partition=C:
    path                    \Windows\system32\winload.efi
    description             Windows 8.1
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {ed9bfd8e-1558-11e4-b9d2-96781b9d737f}
    integrityservices       Enable
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {ed9bfd8c-1558-11e4-b9d2-96781b9d737f}
    nx                      OptIn
    bootmenupolicy          Standard

    Windows Boot Loader
    -------------------
    identifier              {ed9bfd89-1558-11e4-b9d2-96781b9d737f}
    device                  unknown
    path                    \Windows\system32\winload.efi
    description             Windows 8.1
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {ed9bfd8a-1558-11e4-b9d2-96781b9d737f}
    integrityservices       Enable
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                unknown
    systemroot              \Windows
    resumeobject            {ed9bfd88-1558-11e4-b9d2-96781b9d737f}
    nx                      OptIn
    bootmenupolicy          Standard

     

    And the Diskpart output is ...

     

    W8.1-DiskPart-withEFI.PNG

     

    W8.1-DiskPart-withEFI-andDriveLetter.PNG

  • by CathalKilkenny,

    CathalKilkenny CathalKilkenny Jan 11, 2016 10:24 AM in response to Loner T
    Level 1 (0 points)
    Jan 11, 2016 10:24 AM in response to Loner T

    Thanks for getting that to me Loner T.

     

    I tried fiddling with the settings in the BCD making them similar to yours but to no avail. Same error. I feel like if we could just mount the EFI the world would be a much better place.

     

    12516505_996167660426807_2568135_n.jpg

    That is my diskpart output.

     

    You can see that EFI shows as a partition but not as a volume, so it wont let me mount it. I also tried running TESTDISK from an ubuntu USB (as the HDD cannot be mounted during a test) to see if there was any partition table errors, but it found none.

     

    I have also been trying to mount the EFI using mountvol. Using the /s parameter (The official way of mounting the EFI) i get error "the system cannot find the file specified"

     

    Using mountvol to attempt to mount the EFI partition using its GUID:

     

    mountvol \sysmount \\?\Volume\{53746F72-6167-11AA-AA11-00306543ECAC}\

     

    I get error "the parameter is incorrect"

     

    I believe that is the correct GUID for the ESP from looking at the fdisk output in my original post. If I'm wrong please correct me.

     

    There seems to be no information online about a situation where a volume does not show in diskpart but is clearly accessible in any other OS.

     

    Any idea why the volume isn't appearing ?

     

    Thanks again,

     

    Cathal.

  • by Loner T,

    Loner T Loner T Jan 11, 2016 10:33 AM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 11, 2016 10:33 AM in response to CathalKilkenny

    You can try this, but please backup all your data first.

     

    1. Use DD to create a copy of the current EFI partition.

    2. Erase the EFI partition.

    3. Use Diskpart create as

         create partition efi[size=200mb] [offset=512b] [noerr]

    4. DD the dump you have back to the newly create EFI partition.

    5. Test that you can assign a drive letter. If you can, run a BCD Repair and test.

  • by CathalKilkenny,

    CathalKilkenny CathalKilkenny Jan 11, 2016 11:23 AM in response to Loner T
    Level 1 (0 points)
    Jan 11, 2016 11:23 AM in response to Loner T

    I backed up the EFI partition and deleted it. In diskpart creating the new EFI partition I get the error:

     

    EFI partitions are only supported on GPT disks. Convert the disk to GPT and try again.

     

    Is it safe to attempt to convert the disk to GPT ?

     

    The hybrid MBR/GPT probably was the reason I couldn't see the EFI partition in the first place...

  • by Loner T,

    Loner T Loner T Jan 11, 2016 11:38 AM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 11, 2016 11:38 AM in response to CathalKilkenny

    You do have a GPT disk and you did have an EFI before you created a new one. Can you post the output of

     

    diskutil list

    sudo gpt -vv -r show /dev/disk0

    sudo fdisk /dev/disk0

  • by CathalKilkenny,

    CathalKilkenny CathalKilkenny Jan 11, 2016 12:43 PM in response to Loner T
    Level 1 (0 points)
    Jan 11, 2016 12:43 PM in response to Loner T

    Unfortunately the backup of the EFI partition I made wont work now. Instead of using dd like you suggested, I used 'disks' in Ubuntu to create an image from a partition. Thought it would be just as easy. Now when attempting to restore the partition from the image it is giving me an error "the image exceeds the size of the partition by 1.0MB"

     

    I don't know of any way of recreating the EFI partition and will try find a method of restoring it from the .img file I have, although I don't know if that's possible.

     

    current output of the commands you asked for are as follows:

     

    I can still boot into OSX

    Cathals-MacBook-Pro:~ codwyer$ diskutil list\

    /dev/disk0 (internal, physical):\

      #: TYPE NAME SIZE IDENTIFIER\

      0: GUID_partition_scheme *251.0 GB disk0\

      1: Microsoft Basic Data 208.7 MB disk0s1\

      2: Apple_CoreStorage Macintosh HD 149.4 GB disk0s2\

      3: Apple_Boot Recovery HD 650.0 MB disk0s3\

      4: Microsoft Basic Data BOOTCAMP 79.3 GB disk0s4\

      5: Windows Recovery 471.9 MB disk0s5\

      6: Microsoft Basic Data SWAP 21.0 GB disk0s6\

    /dev/disk1 (internal, virtual):\

      #: TYPE NAME SIZE IDENTIFIER\

      0: Apple_HFS Macintosh HD +149.0 GB disk1\

      Logical Volume on disk0s2\

      863CB3BB-A6AB-4DAE-ADA3-05E638AC7DFA\

      Unencrypted\

    Cathals-MacBook-Pro:~ codwyer$ sudo gpt -vv -r show /dev/disk0\

    gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752\

    gpt show: /dev/disk0: Suspicious MBR at sector 0\

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

    gpt show: /dev/disk0: Sec GPT at sector 490234751\

      start size index contents\

      0 1 MBR\

      1 1 Pri GPT header\

      2 32 Pri GPT table\

      34 2014 \

      2048 407552 1 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7\

      409600 40 \

      409640 291721400 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC\

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

      293400576 154951680 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7\

      448352256 921600 5 GPT part - DE94BBA4-06D1-4D40-A16A-BFD50179D6AC\

      449273856 40957952 6 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7\

      490231808 2911 \

      490234719 32 Sec GPT table\

      490234751 1 Sec GPT header\

    Cathals-MacBook-Pro:~ codwyer$ sudo fdisk /dev/disk0\

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

    Signature: 0xAA55\

      Starting Ending\

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

    ------------------------------------------------------------------------\

    1: EE 0 0 1 - 1023 254 63 [ 1 - 2047] <Unknown ID>\

    2: 0B 1023 254 63 - 1023 254 63 [ 2048 - 407552] Win95 FAT-32\

    *3: AF 1023 254 63 - 1023 254 63 [ 409640 - 291721400] HFS+ \

    4: AF 1023 254 63 - 1023 254 63 [ 292131040 - 1269536] HFS+ \

    Cathals-MacBook-Pro:~ codwyer$ \

     

    I'm very frustrated at this stage, and am willing to backup and wipe the disk and start again if needs be. Its a lot of work reconfiguring all of my work software (some of which needs to be done by IT) and reinstalling windows, but at this point it seems like it may be quicker than the path I'm going down.

  • by Loner T,

    Loner T Loner T Jan 11, 2016 1:23 PM in response to CathalKilkenny
    Level 7 (23,623 points)
    Safari
    Jan 11, 2016 1:23 PM in response to CathalKilkenny

    The error message is correct. The number of sectors in EFI should be 409600, but you only have 407552 sectors. Your EFI needs to start at sector 40 and extend to 409639 sectors.

     

    What you currently have is

     

    34 2014 \

      2048 407552 1 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7\

      409600 40 \

     

    Here is an example of a working partition.

     

    sudo gpt -vv -r show /dev/disk0

    Password:

    gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

    gpt show: /dev/disk0: Suspicious MBR at sector 0

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

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

           start        size  index  contents

               0           1         MBR

               1           1         Pri GPT header

               2          32         Pri GPT table

              34           6        

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

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

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

      1450303824        1712        

      1450305536   503904256      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1954209792         295        

      1954210087          32         Sec GPT table

      1954210119           1         Sec GPT header

     

    Can you create a partition with the exact sectors and start and then try to restore the EFI?

Previous Page 2