Bootcamp Partition No Longer Mounted

ahh of course, thanks. Here it is:

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt remove -i 2

usage: gpt remove -a device ...

gpt remove [-b lba] [-i index] [-s lba] [-t uuid] device ...

-bash-3.2# gpt remove -i 3

usage: gpt remove -a device ...

gpt remove [-b lba] [-i index] [-s lba] [-t uuid] device ...

-bash-3.2# gpt add -i 2 -b 409640 -s 714551256-t apfs /dev/disk0

usage: gpt add [-b lba] [-i index] [-s lba] [-t uuid] device ...

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt add -i 3 -b 714960896 -s 222740473 -t

gpt: option requires an argument -- t

usage: gpt add [-b lba] [-i index] [-s lba] [-t uuid] device ...

-bash-3.2# windows /dev/disk0

-bash: windows: command not found

-bash-3.2# gpt add -i 3 -b 714960896 -s 222740473 -t windows /dev/disk0

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

gpt add: /dev/disk0: error: entry at index 3 is not free

-bash-3.2# gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=480103981056; sectorsize=512; blocks=937703088

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 937703087

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 800575448 2 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC

800985088 136716288 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

937701376 1679

937703055 32 Sec GPT table

937703087 1 Sec GPT header

-bash-3.2#

I hope I entered that correctly. When I read your post from my phone, it looked like one of those commands was on a separate line, so I entered that on two different lines, but Terminal rejected that, so I just entered it again, but on the same line. Hopefully that's okay.

Ok, tried that again. Looks like I got a couple errors.

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt remove -i 2 /dev/disk0

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

/dev/disk0s2 removed

-bash-3.2# gpt remove -i 3 /dev/disk0

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

/dev/disk0s3 removed

-bash-3.2# gpt add -i 2 -b 409640 -s 714551256 -t apfs /dev/disk0

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

gpt add: /dev/disk0: error: no space available on device

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt add -i 3 -b 714960896 -s 222740473 -t windows /dev/disk0

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

gpt add: /dev/disk0: error: no space available on device

-bash-3.2# gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=480103981056; sectorsize=512; blocks=937703088

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 937703087

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 800575448 2 MBR part 255

800985088 136716288 3 MBR part 12

937701376 1679

937703055 32 Sec GPT table

937703087 1 Sec GPT header

This is weird. Going back into internet recovery mode, it seems like Safari is on an older version, it’s blocking certain pages with parental control even though I don’t think I’ve set any, and it’s not letting me log into the forum, so I’m typing this on my phone.

Ok actually, I just restarted again in internet recovery mode, and the new version of Safari is back! So I'm able to access the forum again. Do I still need to reinstall macOS? I don't have another hard drive besides the one with which I backed up my mac.

Ok, here it is:

-bash-3.2# diskutil apfs list

APFS Container (1 found)

|

+-- Container ERROR -69808

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

APFS Container Reference: disk1

Size (Capacity Ceiling): ERROR -69620

Capacity In Use By Volumes: ERROR -69524

Capacity Not Allocated: ERROR -69524

|

+-< Physical Store disk0s2 E8F99BDB-B3F0-40FC-8ECE-7FCD40E52CE5

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

| APFS Physical Store Disk: disk0s2

| Size: 365850243072 B (365.9 GB)

|

+-> No Volumes

I actually got an error on the repairDisk step.

-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt remove -i 2 /dev/disk0

/dev/disk0s2 removed

disk-bash-3.2# diskutil unmountDisk disk0

Unmount of all volumes on disk0 was successful

-bash-3.2# gpt add -i 2 -b 409640 -s 714551256 -t hfs /dev/disk0

/dev/disk0s2 added

-bash-3.2# diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Preparing to create trailing loader space by shrinking the volume "" on disk0s2

Creating loader space, part 1 of 3: Verifying the file system

Problems were encountered during repair of the partition map

Error: -69763: Partition map repair failed file system check while creating loader space for a data partition. You should repair that specific partition and then try repairing the partition map again

Underlying error: -69845: File system verify or repair failed

-bash-3.2# diskutil eraseDisk jhfs+ BLANK disk0s2

A volume was specified instead of a whole disk: disk0s2

Specify a whole disk, or instead use diskutil eraseVolume to erase a volume on a specific partition

Ok yes that enabled another disk called "BLANK" to be added to the other two options for destinations in the time machine restore utility. I assume I should select that then and do the restore? Here's the output in case you wanted it:

-bash-3.2# diskutil eraseVolume jhfs+ BLANK disk0s2

Started erase on disk0s2

Unmounting disk

Erasing

Initialized /dev/rdisk0s2 as a 341 GB case-insensitive HFS Plus volume with a 32768k journal

Mounting disk

Finished erase on disk0s2 BLANK

Right. At least the bootcamp drive was in that list of destinations to restore to. And it had 135 GB of space which is what it had after using mini tool partition wizard to resize it. So I feel like that’s a good sign.

This restore is saying it’s going to take about an hour and 40 minutes, so I’ll report back when it’s done.

Yes, Bootcamp is now visible in Finder, and the files inside appear to be intact. Windows is also available under Startup disks in System Preferences. I've got a good amount of homework I have to get done right now, so I'll probably just do the Gdisk steps this afternoon (I'm in California).

Question though: I know this is a long shot, but is it possible to resize the bootcamp partition again before activating it using the Gdisk steps? I'm actually running out of space again, and I'd like to give it an extra 30 or 40GB if possible. But that's not a big deal at all. Just a thought.

Ok, so should I try the steps you were talking about here (page 2 of the post)?

Last time, when I tried to do this for GPT2, you said I should boot in recovery mode to do the correct steps. So did we already do these steps in recovery mode? Or did we do something else and I still need to do this?

If I do still need to do the steps in that last screenshot, I still have the questions I asked last time, listed in the following screenshot:

Ignore the "Do I enter 'y' right here" question. Thanks!