You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

Boot Camp internal error

Have the same problem like here https://discussions.apple.com/thread/250633590


iMac (Retina 5K, 27-inch, Late 2015)

macOS Catalina 10.15.1 (19B88)


When external hdd connected i see this one:


after remove at all times get this. restart not helps...

iMac 27", macOS 10.15

Posted on Nov 8, 2019 12:32 PM

Reply
15 replies
Sort By: 

Dec 9, 2019 7:07 PM in response to Tumbles1982

Tumbles1982 wrote:

Is there a work around for this? a config file that can be edited to make bootcamp assistant disregard checking if there's a second drive in the system?

Yes, by using a standard partitioning scheme that BC Assistant supports.

How could a totally unrelated second internal drive somehow make running bootcamp assistant not possible?

The 'second' (or nth) disk is on the same connection, and is visible to the installer, firmware, applications, etc.,.


The only Mac on which multiple independent internal drives are supported by BC Assistant is the legacy Tower MacPro. On such towers, the only supported configurations are


  • A single disk, or,
  • Two disks, one dedicated to Windows.
  • All other physical disks must be removed during the installation of Windows, but can be connected later.


BCA uses the Mac Model Identifier and supported disk layouts to allow partitioning.

Reply

Nov 9, 2019 8:03 AM in response to Loner T

** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the space manager free queue trees.

** Checking the object map.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Macintosh HD - Data was formatted by diskmanagementd (945.241.4) and last modified by apfs_kext (1412.41.1).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (1412.41.1).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Recovery was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (1412.41.1).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume VM was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (1412.41.1).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Macintosh HD was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Verifying allocated space.

** The volume /dev/rdisk1 appears to be OK.

Reply

Dec 9, 2019 7:31 PM in response to Loner T

Thanks for this reply the more info the better. Because I consider myself a power user and don't mind having to re-format drives and reinstall mac os as required, I would be very interested in how to work around this. Somewhere in the code there must be conditions stating macprox,x is support for two disks, one dedicated to windows. I would like to know where this is and insert my iMac18,3 in its place and see what happens. Are you able to point me in the right direction?


Failing that I will have to try opening up the iMac again, unplugging the main NVMe MacOS drive, boot up the second ssd and recover Mac OS, run boot camp, get windows going, clone this disk to another drive, reformat and reclone so that windows now has the whole drive, reinstall the original mac os nvme drive, then seal it all back up again!

Reply

Nov 9, 2019 12:30 PM in response to Loner T

/dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS SSD 2.0 TB disk0s2 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_APFS Container disk2 500.1 GB disk1s2 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +500.1 GB disk2 Physical Store disk1s2 1: APFS Volume Macintosh HD - Data 76.8 GB disk2s1 2: APFS Volume Preboot 131.9 MB disk2s2 3: APFS Volume Recovery 1.6 GB disk2s3 4: APFS Volume VM 2.1 GB disk2s4 5: APFS Volume Macintosh HD 10.8 GB disk2s5
APFS Container (1 found) | +-- Container disk2 588E7EBE-93AD-441F-ABD4-F7568132E395 ==================================================== APFS Container Reference: disk2 Size (Capacity Ceiling): 500068036608 B (500.1 GB) Capacity In Use By Volumes: 91636998144 B (91.6 GB) (18.3% used) Capacity Not Allocated: 408431038464 B (408.4 GB) (81.7% free) | +-< Physical Store disk1s2 7941C26F-EB25-421B-9BBF-9C1D833BEC19 | ----------------------------------------------------------- | APFS Physical Store Disk: disk1s2 | Size: 500068036608 B (500.1 GB) | +-> Volume disk2s1 03BE85A2-44B7-4FA3-9A04-CB45DFC9F322 | --------------------------------------------------- | APFS Volume Disk (Role): disk2s1 (Data) | Name: Macintosh HD - Data (Case-insensitive) | Mount Point: /System/Volumes/Data | Capacity Consumed: 76786053120 B (76.8 GB) | FileVault: No | +-> Volume disk2s2 518F8BF9-1532-4044-B2F0-8C775FDC5F19 | --------------------------------------------------- | APFS Volume Disk (Role): disk2s2 (Preboot) | Name: Preboot (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 131932160 B (131.9 MB) | FileVault: No | +-> Volume disk2s3 D0B94627-5CCA-4B6A-AF3D-CE9BB04ABC33 | --------------------------------------------------- | APFS Volume Disk (Role): disk2s3 (Recovery) | Name: Recovery (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 1564393472 B (1.6 GB) | FileVault: No | +-> Volume disk2s4 E0AE78F2-5857-4452-85C9-2FF770A48231 | --------------------------------------------------- | APFS Volume Disk (Role): disk2s4 (VM) | Name: VM (Case-insensitive) | Mount Point: /private/var/vm | Capacity Consumed: 2148552704 B (2.1 GB) | FileVault: No | +-> Volume disk2s5 13CABF57-713B-4E60-9398-E9FE1390C0DD --------------------------------------------------- APFS Volume Disk (Role): disk2s5 (System) Name: Macintosh HD (Case-insensitive) Mount Point: / Capacity Consumed: 10844561408 B (10.8 GB) FileVault: No


Reply

Boot Camp internal error

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