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 multiple errors on iMac 2019

Before I update to Catalina 10.15.7:

Error: disk could not be partitioned

I've tried first aiding the drive in disk utility and it did not work. Then I tried to update Mac OS to 10.15.7.


After Mac OS update:

Error: Can’t install the software because it is not currently available from the Software Update server.

This time I'm stuck here even before being able to proceed to disk partition. I've tried disconnecting and connecting wifi and ethernet, rebooting and it still didn't work. *to add on I've also tried the "action tab method" and it prompted the same error as well.


Looking forward to a solution asap, thanks.

iMac Line (2012 and Later)

Posted on Oct 17, 2020 4:08 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 18, 2020 9:05 AM

  • Run
    • diskutil eject disk3
  • Disconnect all external storage
  • Run SMC and NVRAM Reset
  • Retry BC Assistant.
  • If you get an error, in macOS Terminal, run
    • sudo fsck_apfs -n -l /dev/rdisk2
    • and post the output



Similar questions

14 replies

Oct 18, 2020 8:04 PM in response to Loner T

  • Not sure if the partition error was fixed but prior to that partition stage I am still stuck at "Can’t install the software because it is not currently available from the Software Update server." Below is the output of "sudo fsck_apfs -n -l /dev/rdisk2":


** Checking the container superblock.


** Checking the fusion superblock.


** Checking the EFI jumpstart record.


** Checking the space manager.


** Checking the space manager free queue trees.


** Checking the object map.


** Checking the Fusion data structures.


** Checking volume.


** Checking the APFS volume superblock.


** The volume Macintosh HD was formatted by newfs_apfs (1412.11.6) and last modified by apfs_kext (1412.141.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 - Data was formatted by asr (1412.11.6) and last modified by apfs_kext (1412.141.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 asr (1412.11.6) and last modified by apfs_kext (1412.141.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 asr (1412.11.6) and last modified by apfs_kext (1412.141.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 apfs.util (1412.81.1) and last modified by apfs_kext (1412.141.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.


warning: MT mapping (0x40000001da99a -> 0x560bc3, 2, C) is not completely referenced


warning: MT mapping (0x4000000299457 -> 0x5624c1, 2, C) is not completely referenced


warning: MT mapping (0x4000000299459 -> 0x563b65, 2, C) is not completely referenced


warning: MT mapping (0x40000002cb9d4 -> 0x3c2f5c, 206, C) is not completely referenced


warning: MT mapping (0x40000002fa239 -> 0x5624e3, 4, C) is not completely referenced


warning: MT mapping (0x400000031dca3 -> 0x648ac3, 3, C) is not completely referenced


warning: MT mapping (0x400000031f228 -> 0x5640ec, 2, C) is not completely referenced


warning: MT mapping (0x400000031f240 -> 0x2f9afb, 1, C) is not completely referenced


warning: MT mapping (0x4000000344539 -> 0x56001f, 2, C) is not completely referenced


warning: MT mapping (0x400000034466c -> 0x5608b8, 2, C) is not completely referenced


warning: MT mapping (0x4000000348462 -> 0x560287, 2, C) is not completely referenced


warning: MT mapping (0x400000034982d -> 0x5631e1, 2, C) is not completely referenced


Too many warnings of this type generated; suppressing subsequent ones.


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


Oct 19, 2020 6:16 AM in response to Bananapple94

Bananapple94 wrote:


Many are reporting this issue.
Could it be due to the latest version of Catalina? If it is then it's kinda let down that Apple hasn't fix it given 10.15.7 was released almost a month ago and their official support regarding partition issue was to update the OS first..

I installed W10 on a 2018 Mini running macOS Catalina 10.15.7.




There were actually more similar warnings, I got rid some of it to fit the 5000 words limitation in that reply.

This is what I expected.

Anyways thank you for your reply! Guess I'll have to wait the next update or Big Sur then.

You should be able to make it work on macOS Catalina.

Oct 17, 2020 5:20 PM in response to Loner T

Thanks for your reply, here it is:


/dev/disk0 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        *28.0 GB    disk0


   1:                        EFI EFI                     314.6 MB   disk0s1


   2:                 Apple_APFS Container disk2         27.6 GB    disk0s2




/dev/disk1 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      GUID_partition_scheme                        *1.0 TB     disk1


   1:                        EFI EFI                     209.7 MB   disk1s1


   2:                 Apple_APFS Container disk2         1000.0 GB  disk1s2




/dev/disk2 (synthesized):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:      APFS Container Scheme -                      +1.0 TB     disk2


                                 Physical Stores disk0s2, disk1s2


   1:                APFS Volume Macintosh HD            11.2 GB    disk2s1


   2:                APFS Volume Macintosh HD - Data     107.6 GB   disk2s2


   3:                APFS Volume Preboot                 81.1 MB    disk2s3


   4:                APFS Volume Recovery                528.9 MB   disk2s4


   5:                APFS Volume VM                      2.1 GB     disk2s5




/dev/disk3 (disk image):


   #:                       TYPE NAME                    SIZE       IDENTIFIER


   0:                            CCCOMA_X64FRE_EN-US... +5.3 GB     disk3

Oct 19, 2020 4:29 AM in response to Bananapple94

Bananapple94 wrote:

Not sure if the partition error was fixed but prior to that partition stage I am still stuck at "Can’t install the software because it is not currently available from the Software Update server.• "

Many are reporting this issue.


Below is the output of "sudo fsck_apfs -n -l /dev/rdisk2":

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

Except the warnings, the file system looks relatively clean.

Oct 19, 2020 5:54 AM in response to Loner T

Many are reporting this issue.

Could it be due to the latest version of Catalina? If it is then it's kinda let down that Apple hasn't fix it given 10.15.7 was released almost a month ago and their official support regarding partition issue was to update the OS first..

Except the warnings, the file system looks relatively clean.

There were actually more similar warnings, I got rid some of it to fit the 5000 words limitation in that reply.

Anyways thank you for your reply! Guess I'll have to wait the next update or Big Sur then.

Boot camp multiple errors on iMac 2019

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