Error installing Win 10 - can't tell if enough space

[theSeb]

I keep getting this error when trying to upgrade Windows 8.1 on my 2013 Mac Pro.

Here is a summary:

1. Apple Software Update did not show the Bootcamp 6 update, so I used the Bootcamp Assistant on OS X and it downloaded Bootcamp 6 onto a USB stick. I then used this in Windows to upgrade bootcamp. Looking at Programs and Features, I appear to have BC 6 installed.

2. I tried to use the normal download method twice and both times it came back with the same error 8007001F. I know there is another thread on this error, but I have managed to get past it (point 3)

3. I then downloaded the ISO and the USB DVD media tool to create a USB flash drive. I cannot boot from it, but when I run setup.exe I get as far as the "not enough space" error and cannot continue.

4. I have searched and followed the various suggestions, like using Trouble Shooting in Control Panel, running chkdsk /b, running Disk Clean up and so forth

I am out of ideas. Has anybody encountered this on a Mac and managed to get past it? I see some people dual booting PCs with Linux have this issue, but their solutions do not seem viable on a Mac.

 

[beady]

i have the same model MacBook and I've got the same problem. There are a few others online with the same problem but no real solution that I have found.

 

[Gjwilly]

Are either of you using any 3rd-party boot managers?

 

[theSeb]

Are either of you using any 3rd-party boot managers?

No, just normal Bootcamp with Yosemite 10.10.5

 

[beady]

No, just normal Bootcamp with Yosemite 10.10.5

Same

 

[sickntired]

I've had this same problem on my 2013 15" MBP. The only thing that helped was to do a clean install of Win 8 and upgrade from that -- had no problems upgrading when I did that.

 

[Gjwilly]

I've had this same problem on my 2013 15" MBP. The only thing that helped was to do a clean install of Win 8 and upgrade from that -- had no problems upgrading when I did that.

That's the solution I've seen on other forums.
Something about Windows 10 not being able to find or not liking the existing Windows 8 recovery partition so a new one needs to be created before Windows 10 will proceed.

 

[theSeb]

That's the solution I've seen on other forums.
Something about Windows 10 not being able to find or not liking the existing Windows 8 recovery partition so a new one needs to be created before Windows 10 will proceed.

I think that makes sense. I may have broken something with win clone a few months ago.

 

[KdParker]

I think that makes sense. I may have broken something with win clone a few months ago.

you might be able to use fdisk to redefine your partionw.

 

[theSeb]

you might be able to use fdisk to redefine your partionw.

It's been about 10 years since I've done anything interesting the command prompt, but wasn't fdisk replaced by diskpart? Regardless, I know what the tools do, but I have no idea what I should do with them in my instance

 

[theSeb]

Update: I have discovered that I have far more serious issues than just not being to upgrade to windows 10. There is something very wrong with my internal storage.

https://forums.macrumors.com/threads/cannot-see-internal-drive-when-in-recovery-mode.1910737/

Despite the issue above, I managed to install a clean version of Windows 8 and the upgrade to 10 is now working as well. I'll never be able to do a clean install of OS X on the Mac Pro now, but it's something that I have to live with. It's very odd because everything else works perfectly.

 

[macenied]

Update: I have discovered that I have far more serious issues than just not being to upgrade to windows 10. There is something very wrong with my internal storage.

https://forums.macrumors.com/threads/cannot-see-internal-drive-when-in-recovery-mode.1910737/

Despite the issue above, I managed to install a clean version of Windows 8 and the upgrade to 10 is now working as well. I'll never be able to do a clean install of OS X on the Mac Pro now, but it's something that I have to live with. It's very odd because everything else works perfectly.

Mind to share your hardware configuration & HDU / SSD you use ?

 

[theSeb]

Mind to share your hardware configuration & HDU / SSD you use ?

Mac Pro 2013
1 TB PCIe SSD
D700
6 core

Everything works fine on the surface, but there is something quite weird. I have never had this problem on any of my other Macs.

 

[macenied]

Thank you. I assume the SSD is internal.

Here is what I would do:

- Back up OSX using Time Machine, erase the Time Machine volume before the backup to get a 100% consistent backup.
- Back up any Windows Data you need

Optional: Update SSD drive firmware. Mandatory: Zero the SSD using the drive manufacturers utility. You may need another computer to do those 2 steps. The disk should be completely empty after that.

- Install OSX using Network recovery. Create only one OSX partition in this step.
- Restore your TM backup to OSX
- Install Windows using Bootcamp assistant

This should give you a clean partition layout on a working SSD so that you can progress with the SSD and W10.

 

[theSeb]

Thank you. I assume the SSD is internal.

Here is what I would do:

- Back up OSX using Time Machine, erase the Time Machine volume before the backup to get a 100% consistent backup.
- Back up any Windows Data you need

Optional: Update SSD drive firmware. Mandatory: Zero the SSD using the drive manufacturers utility. You may need another computer to do those 2 steps. The disk should be completely empty after that.

- Install OSX using Network recovery. Create only one OSX partition in this step.
- Restore your TM backup to OSX
- Install Windows using Bootcamp assistant

This should give you a clean partition layout so that you can progress with the SSD and W10.

I already managed to install Windows 10. The problem is that I can never do a clean OS X install, not even from Internet Recovery. The details of this are in the other thread I made and the link is above.

 

[macenied]

I already managed to install Windows 10. The problem is that I can never do a clean OS X install, not even from Internet Recovery. The details of this are in the other thread I made and the link is above.

My recommondation makes sure you have no hardware or partition layout issues. You can give it a try. A lot happened to this SSD already, right ?

The point is: Update SSD firmware and zero the disk. Then install from scratch and restore whatever you need. Let OSX do it´s job. No terminal commands, no 3rd party utility. A Mac not able to install OSX clean does not sound good to me. But maybe it´s only me .

 

[theSeb]

My recommondation makes sure you have no hardware or partition layout issues. You can give is a try . A lot happened to this SSD already, right ?

The point is: Update SSD firmware and zero the disk. Then install from scratch and restore whatever you need.

The SSD firmware update is an interesting suggestion, so I might give it a try, once all of my steam games finish installing.

 

[macenied]

The SSD firmware update is an interesting suggestion, so I might give it a try, once all of my steam games finish installing.

I don´t know if there will be a FW update for your disk. I think someone / something destroyed your partition information or the SSD has a defect. This can be detected / resolved by testing & zeroing the disk and letting OSX do the job. But it´s your Mac anyways so GL with it.

 

[theSeb]

I don´t know if there will be a FW update for your disk. I think someone / something destroyed your partition information or the SSD has a defect. This can be detected / resolved by testing & zeroing the disk and letting OSX do the job. But it´s your Mac anyways so GL with it.

The trouble with that theory is that I formatted the entire disk using target disk mode and another Mac, so that should have recreated the partition table. The fact that I still can't boot into the Recovery HD after formatting and recreating the recovery partition on the drive shows that there is a problem. The Mac Pro's storage is based on the Samsung XP941, as far as I can tell, and I cannot find a firmware upgrade for it.

 

[macenied]

The trouble with that theory is that I formatted the entire disk using target disk mode and another Mac, so that should have recreated the partition table. The fact that I still can't boot into the Recovery HD after formatting and recreating the recovery partition on the drive shows that there is a problem. The Mac Pro's storage is based on the Samsung XP941, as far as I can tell, and I cannot find a firmware upgrade for it.

Beratungsresistent ??? ( <--- German )

Target disk mode is certainly not the best choice for system disk partitioning. You came to the forum with a problem and I show you a way how to solve it. You can do it - or not.

 

[theSeb]

Beratungsresistent ??? ( <--- German )

Target disk mode is certainly not the best choice for system disk partitioning. You came to the forum with a problem and I show you a way how to solve it. You can do it - or not.

We seem to be talking at cross purposes. I did not partition the drive using target disk mode. I cannot follow the steps of your solution, because internet recovery does not see my internal disk and I cannot upgrade the firmware, unless google is broken for me.

 

[doynton]

Show us this then...

diskutil list - you should see something like this...

adams-mbp:~ adam$ diskutil list

/dev/disk0 (internal, physical):

  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *121.3 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s
  2:                  Apple_HFS El Capitan               54.5 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:       Microsoft Basic Data Windows10                66.0 GB   disk0s4

Then download gdisk from http://sourceforge.net/projects/gptfdisk/files/latest/download and display the GPT layout Then we can see your real partition layout...

Enter sudo gdisk /dev/disk0 <enter> then p <enter>

adams-mbp:downloads adam$ sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.0
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): p
Disk /dev/disk0: 236978176 sectors, 113.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9730D1EA-8014-43FD-A713-9AB93CD62EBE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 236978142
Partitions will be aligned on 8-sector boundaries
Total free space is 3093 sectors (1.5 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
  1              40          409639   200.0 MiB   EF00  EFI System Partition
  2          409640       106802351   50.7 GiB    AF00  Yosemite
  3       106802352       108071887   619.9 MiB   AB00  Recovery HD
  4       108072960       236976127   61.5 GiB    0700  Windows10

Command (? for help):

Then press x then o to show the mbr (if you have one)

Command (? for help): X

Expert command (? for help): o

Disk size is 236978176 sectors (113.0 GiB)
MBR disk identifier: 0x5D3CF3FA
MBR partitions:

Number  Boot  Start Sector   End Sector   Status      Code
  1                     1       409639   primary     0xEE
  2                409640    106802351   primary     0xAF
  3             106802352    108071887   primary     0xAB
  4      *      108072960    236976127   primary     0x0C

Expert command (? for help): q

Then you can press q to get out of gdisk without changing anything....

It might help....

 

[theSeb]

@doynton , hopefully you can spot something that I have missed

diskutil list

   #:                       TYPE NAME                    SIZE       IDENTIFIER

  0:      GUID_partition_scheme                        *1.0 TB     disk0

  1:                        EFI EFI                     209.7 MB   disk0s1

  2:                  Apple_HFS MacProHD                850.0 GB   disk0s2

  3:                 Apple_Boot Recovery HD             784.2 MB   disk0s3

  4:       Microsoft Basic Data BOOTCAMP                149.1 GB   disk0s4

  5: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC               471.9 MB   disk0s5

5 popped up after I upgraded to Windows 10. Doing some research it is the Windows 10 recovery partition

I don't think that gdisk gives any extra info over the built-in gpt, so I am including the output of gpt

 

[macenied]

The partition table is corrupt. Partition 5 should not be there and there may be other inconsistencies as well. Here you see a valid partition table with W10 installed. No such a thing as a Windows recovery partition. Loop back to my posting #20 in this thread.

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *480.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS OSX 159.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 320.0 GB disk0s4

 

[theSeb]

The partition table is corrupt. Partition 5 should not be there and there may be other inconsistencies as well. Here you see a valid partition table with W10 installed. No such a thing as a Windows recovery partition. Loop back to my posting #20 in this thread.

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *480.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS OSX 159.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 320.0 GB disk0s4

According to technet DE94BBA4-06D1-4D40-A16A-BFD50179D6AC (5) is the Windows recovery partition.

https://technet.microsoft.com/en-us/library/ff715563.aspx

It only appeared when I upgraded the clean install of Windows 8 to Windows 10.

Regardless of all of that, I am stuck in this kind of sort-of-working limbo. Like I mentioned, if I boot into a recovery partition on a USB install disk, a clone, a time machine backup, or internet recovery, I cannot access the internal drive (/dev/disk0). Out of those options, I can get to /dev/disk0 from internet recovery, but only momentarily...

For example, if I go into internet recovery and then straight into the terminal, I can view the partition info using gpt on /dev/disk0, but I cannot mount it. In fact, if I run gpt once on /dev/disk0, it shows the info, but if I try to run it again, or something like diskutil, then /dev/disk0 disappears. It does not show up in Disk Utility at all.

The only way I can reliably access /dev/disk0 to be able to format it is via target disk mode from another Mac. That's how I formatted it a few days ago when these troubles started. I would assume that should have recreated the partition table. However, I still have the same issues, so unless someone knows some kung-fu using diskutil, or gpt, then my only option is to try and replace the internal storage via Apple, or eBay. I recall reading that OWC might be offering something for the 2013 Mac Pro too, so that is another possible option.

To recap: I could not upgrade Windows 8 to Win 10 due to the error mentioned in the first post. I decided to remove Bootcamp to start with a clean version of Windows 8. During bootcamp removal Bootcamp assistant got stuck and froze the Mac. I restarted and a small part of the Bootcamp partition was left. Windows also showed up in the start menu (holding opt during startup). I rebooted into OS X and recreated the Bootcamp partition using BCA, and then immediately removed it again using BCA. This time it worked fine and Windows was no longer showing up in the start up menu and the BC partition was gone. This was when I wanted to do some checks on the partition table and I subsequently discovered that my internal drive (/dev/disk0) would not show up if I booted into an external recovery hd or internet recovery. I also discovered that I could not boot into the recovery hd on the internal drive at all.

I did not want to simply install Windows 8 and try to upgrade to 10, in case I was still stuck with the same error as in post 1, so I formatted the drive using target disk mode, since that was the only way to be able to access it. I did not just format just the OS X volume. I formatted the entire drive. After the format I still have the same issue with the internal drive not showing up if I boot using an external recovery hd. The way I restored is by cloning the backup of OS X back to the internal drive using target disk mode from another Mac. I then gave up on all of this and installed Windows 8 via BCA and then upgraded it to Windows 10 to see if it would work. It did, but that's when the extra partition (5) showed up.

I now have Windows 10 and it is running fine, seemingly. OS X is running too. I still cannot boot into the recovery hd on the internal drive. I also cannot do a clean install of OS X in the future, unless I can fix this issue.

I have been getting an occasional kernel panic in OS X for the last 3 months. I also used to get the occasional CACHE MANAGER blue screen in Windows 8.1. Both of these may, or may not, be related to the issue with my internal storage. Your suggestion to upgrade the firmware was a good one, but there is no firmware upgrade available for the Samsung flash storage inside the Mac Pro. At least none that I can find via searching the internet.

Edit to add: The last few kernel panics look like this

Spoiler

Anonymous UUID:       6CF8BB9D-9B28-B35E-69B7-9C0ADA5FE461

Fri Aug 28 18:08:29 2015

*** Panic Report ***
panic(cpu 2 caller 0xffffff80069c127e): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.40.9/bsd/kern/kern_exit.c:363

uuid info:
 0x7fff6a90b000    uuid = <b1b370a5-479f-3533-8ad7-97b687d4f989>
 0x10907d000    uuid = <c0446878-e8d0-3461-a226-91ff1c2b2da6>
 0x1090d1000    uuid = <4396b358-725e-3ec0-bcbb-e4bf75fe1fb0>

RAX: 0x0000000002000001, RBX: 0x0000000000000006, RCX: 0x000000010ab860e8, RDX: 0x0000000000000000
RSP: 0x000000010ab860e8, RBP: 0x000000010ab86190, RSI: 0x000000010ab85f40, RDI: 0x0000000000000001
R8:  0x0000000000000000, R9:  0x00000001090bc9f0, R10: 0x00007fff8e351b02, R11: 0x0000000000000206
R12: 0x0000000000000000, R13: 0x00007fff886727e0, R14: 0x000000010ab865d0, R15: 0x000000010ab86790
RFL: 0x0000000000000206, RIP: 0x00007fff8e34f95a, CS:  0x0000000000000007, SS:  0x0000000000000023

Thread  0xffffff805121f000
    0x00007fff8aedadab
    0x00007fff8aedaec8
    0x00007fff8aed43b4
    0x00007fff90f08a6c
    0x00000001090ab907
    0x00007fff8a3f7c13
    0x00007fff8a3fa88f
    0x00007fff8a408fe4
    0x00007fff8e9f3a9d
    0x00007fff8e9f13dd
    0x0000000000000000

Thread  0xffffff805133c970
    0x00007fff8a3faa6a
    0x0000000000000000

Thread  0xffffff80513c1000
    0x0000000109094c91
    0x00007fff8a3f7c13
    0x00007fff8a3fb365
    0x00007fff8a3fcecc
    0x00007fff8a3fa6b7
    0x00007fff8a408fe4
    0x00007fff8e9f3a9d
    0x00007fff8e9f13dd
    0x0000000000000000

Thread  0xffffff80513c1e28
    0x00007fff8a4083ad
    0x0000000000000000

Thread  0xffffff80544c8970
    0x00007fff8e9f13dd
    0x0000000000000000

Thread  0xffffff807377a5c0
    0x00007fff8a3fa468
    0x00007fff8e9f405a
    0x00007fff8e9f3fd7
    0x00007fff8e9f13ed
    0x0000000000000000

Thread  0xffffff805ffda000
    0x00007fff8df30f1a
    0x00007face672b350
    0x00007fff6a917475
    0x00007fff8e9ee7b5
    0x00007fff8aea9648
    0x00007fff886727e0
    0x00007fff88674ddf
    0x00007fff8a3f7c13
    0x00007fff8a3f8e5e
    0x00007fff886730a7
    0x00000001090a8393
    0x00007fff8a3f7c13
    0x00007fff8a3fb365
    0x00007fff8a3fcecc
    0x00007fff8a3fb154
    0x00007fff8a3fcecc
    0x00007fff8a3fa6b7
    0x00007fff8a408fe4
    0x00007fff8e9f3a9d
    0x00007fff8e9f13dd
    0x0000000000000000

Mac OS version: 14F27
Kernel version: Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64
Kernel UUID: 58F06365-45C7-3CA7-B80D-173AFD1A03C4
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)

System Profile:
Graphics: AMD FirePro D700, AMD FirePro D700, PCIe, 6144 MB
Graphics: AMD FirePro D700, AMD FirePro D700, PCIe, 6144 MB
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.6f3 16238, 3 services, 27 devices, 1 incoming serial ports
PCI Card: AMD FirePro D700, Display Controller, Slot-1
PCI Card: AMD FirePro D700, Display Controller, Slot-2
PCI Card: pci105a,8760, RAID Controller, Thunderbolt@236,0,0
PCI Card: pci1b4b,9182, AHCI Controller, Thunderbolt@155,0,0
PCI Card: pci1b4b,9182, AHCI Controller, Thunderbolt@159,0,0
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: eSata Hub, LaCie, 1, 26.1
Thunderbolt Device: Pegasus R-Series, Promise Technology, Inc., 3, 22.2
Memory Module: DIMM1, 8 GB, DDR3 ECC, 1866 MHz, 0x02FE, 0x45424A3831454738424657422D4A532D4620
Memory Module: DIMM2, 8 GB, DDR3 ECC, 1866 MHz, 0x02FE, 0x45424A3831454738424657422D4A532D4620
Memory Module: DIMM3, 8 GB, DDR3 ECC, 1866 MHz, 0x02FE, 0x45424A3831454738424657422D4A532D4620
Memory Module: DIMM4, 8 GB, DDR3 ECC, 1866 MHz, 0x02FE, 0x45424A3831454738424657422D4A532D4620
USB Device: Hub
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: MiniPro
USB Device: My Passport 0748
USB Device: USB3.0 Hub
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: Hub
USB Device: USB2.0 Hub
USB Device: USB Receiver
USB Device: Matias Keyboard
USB Device: Hub
USB Device: Display Audio
USB Device: Display iSight
USB Device: Apple LED Cinema Display
USB Device: USB2.0 Hub
Serial ATA Device: APPLE SSD SM1024F, 1 TB
Serial ATA Device: unknown
Serial ATA Device: ST1000DM003-9YN162, 1 TB
Serial ATA Device: ST1000DM003-9YN162, 1 TB
Network Service: Wi-Fi, AirPort, en2
Model: MacPro6,1, BootROM MP61.0116.B15, 6 processors, 6-Core Intel Xeon E5, 3.5 GHz, 32 GB, SMC 2.20f18