Windows 10 bootcamp lost (macOS Mojave)

Question

Level 1

9 points

Windows 10 bootcamp lost (macOS Mojave)

Hello,

my Windows 10 bootcamp partition is totally lost. I wanted to download the latest bootcamp drivers as function buttons like brightness or volume settings did not work on Win10, and I'm afraid I accidentally clicked the "Continue" button in Boot Camp Assistant, and it sent the whole Win10 partition south. Now it's not shown in the SysPref > Startup Disk or in Disk Utility. It also disappeared from the startup disk selection menu available when pressing Option during boot.

blackdog$ sudo gpt -r -vv show disk0
Password:
gpt show: disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: disk0: PMBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 977105059
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  781277144      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
  781686784  195418243         
  977105027         32         Sec GPT table
  977105059          1         Sec GPT header

blackdog$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         400.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +400.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume rMBP15 SSD              335.6 GB   disk1s1
   2:                APFS Volume Preboot                 45.9 MB    disk1s2
   3:                APFS Volume Recovery                510.4 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *31.9 GB    disk2
   1:                 DOS_FAT_32 NO NAME                 31.9 GB    disk2s1

Actually it's not that painful as I used this Win10 partition for occasionally playing Win only games, however now the 100GB partition that was assigned to Windows10 can nowhere be found. I would like to recover it to reassign and reinstall a new Boot Camp partition if recovering the lost partition is too much work (there's nothing important there that would worth hours of tinkering).

I'm on macOS Mojave (10.14.6) on a dGPU retina MacBook Pro 2015 15".

Thanks in advance!

MacBook Pro 15″, macOS 10.14

Posted on Jul 19, 2020 8:15 AM

Reply

Answer 1

blackdogone Author

Level 1

9 points

Jul 28, 2020 4:14 AM in response to Loner T

Hello Loner T,

thanks a lot for your reply. Here's the terminal output from the command you suggested:

Started APFS operation
Aligning grow delta to 100 054 138 880 bytes and targeting a new physical store size of 500 068 036 608 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 500 067 006 464 bytes
Resizing APFS Container designated by APFS Container Reference disk1
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk0s2
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 rMBP15 SSD was formatted by diskmanagementd (945.200.129) and last modified by apfs_kext (945.275.9)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_num_other_fsobjects (92) is not valid (91)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.275.9)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: directory valence check: directory (oid 0x70050): orphan directory record
warning: directory valence check: directory (oid 0x70050): orphan directory record
Checking volume
Checking the APFS volume superblock
The volume Recovery was formatted by diskmanagementd (945.200.129) and last modified by apfs_kext (945.275.9)
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 (945.200.129) and last modified by apfs_kext (945.275.9)
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: Overallocation Detected on Main device: (1940+1) bitmap address (1f14e60)

[... I cut a lot of similar messages from here, because it was too long to post...]

warning: Overallocation Detected on Main device: (162792+1) bitmap address (1f14e34)
too many warnings generated; suppressing subsequent ones
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 400 013 897 728 to 500 068 036 608 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation

Reply