corrupted partition table, need help fixing

Question

zero7404 Author

Level 3

816 points

corrupted partition table, need help fixing

Hello (Loner T),

I have an issue with my partition table and need to rebuild it. Would you please assist ?

Output of:

sudo gdisk /dev/disk0

GPT fdisk (gdisk) version 1.0.4

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): P

Disk /dev/disk0: 490234752 sectors, 233.8 GiB

Sector size (logical): 512 bytes

Disk identifier (GUID): 57ECCA5D-3ED3-4ECC-B8F8-568B5DF9C6D0

Partition table holds up to 128 entries

Main partition table begins at sector 2 and ends at sector 33

First usable sector is 34, last usable sector is 490234718

Partitions will be aligned on 8-sector boundaries

Total free space is 4035 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 195858431 93.2 GiB AF0A

3 195858432 469830561 130.6 GiB 0700 Basic data partition

4 469831680 470835199 490.0 MiB 2700

5 470837248 490233855 9.2 GiB AF00 Apple HFS/HFS+

Output of:

sudo gpt -r show /dev/disk0

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

195858432 273972130 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

469830562 1118

469831680 1003520 4 GPT part - DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

470835200 2048

470837248 19396608 5 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

490233856 863

490234719 32 Sec GPT table

490234751 1 Sec GPT header

MacBook Pro Retina

Posted on Aug 26, 2019 9:01 PM

Reply

Answer 1

zero7404 Author

Level 3

816 points

Sep 3, 2019 7:58 PM in response to Loner T

i have a late 2013 15" mbp, my model is 11,2. don't have an mb air.

i think the path i will take ....

create a bootable macOS mojave on a usb

boot into it, wipe my entire ssd using disk utility

install mojave on the entire ssd, let it create partitions or i will create one at time of install

boot into mojave from the ssd, create my share hfs+ partition

create a bootable windows 10 usb

start boot camp, create the windows space

follow boot camp procedure and do the windows 10 install

that should leave me with a clean GPT and no abnormalities with the partitions, correct ?

Reply

Answer 2

Loner T

Level 9

59,536 points

Aug 29, 2019 3:45 AM in response to zero7404

Can you boot into Windows, run msinfo32 and post the value of BIOS Mode?

Reply

Answer 3

Loner T

Level 9

59,536 points

Aug 30, 2019 5:32 PM in response to zero7404

Run

diskutil eraseVolume jhfs+ BC1 disk0s4

dskutil mergePartitions jhfs+ SHARE disk0s4 disk0s5

diskutil list

and post the output, before we go further.

Reply

Answer 4

zero7404 Author

Level 3

816 points

Aug 31, 2019 3:40 PM in response to Loner T

Reply

Answer 5

Loner T

Level 9

59,536 points

Aug 30, 2019 8:48 AM in response to zero7404

You have a UEFI installation on a late 2013 rMBP, so a MBR is not required. If you are able to see SHARE in Windows and macOS, and both OSes continue to work, do we need to tinker with the partitions?

Reply

Answer 6

Loner T

Level 9

59,536 points

Aug 28, 2019 4:15 AM in response to zero7404

If you have a backup of SHARE, we can erase WinRE and merge it with SHARE and restore it. However, depending on your model, we may need to recreate the MBR and Repair Windows.

Reply

Answer 7

Loner T

Level 9

59,536 points

Aug 28, 2019 1:58 PM in response to zero7404

Can you post the output of

sudo fdisk /dev/disk0

Reply

Answer 8

Loner T

Level 9

59,536 points

Sep 1, 2019 4:50 PM in response to zero7404

Install macOS (same version as the internal disk) on an external disk, and we can try to address the corruption. It is better to address it now, rather than wait.

Reply

Answer 9

zero7404 Author

Level 3

816 points

Aug 30, 2019 6:43 PM in response to Loner T

diskutil eraseVolume jhfs+ BC1 disk0s4

Started erase on disk0s4
Unmounting disk
Erasing
Initialized /dev/rdisk0s4 as a 490 MB case-insensitive HFS Plus volume with a 8192k journal
Mounting disk
Finished erase on disk0s4 BC1

diskutil mergePartitions jhfs+ SHARE disk0s4 disk0s5

Merging partitions into a new partition
     Start partition: disk0s4 BC1
     Finish partition: disk0s5 SHARE
Started partitioning on disk0
Merging partitions
Waiting for partitions to activate
Growing disk
Finished partitioning on disk0
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         100.1 GB   disk0s2
   3:       Microsoft Basic Data Windows                 140.3 GB   disk0s3
   4:                  Apple_HFS BC1                     10.3 GB    disk0s4

Reply

Answer 10

Loner T

Level 9

59,536 points

Sep 1, 2019 6:57 PM in response to zero7404

You are in Internet Recovery and the disks are images from the Apple servers. If you look at the bottom, you can see the two APFS mounts. Reboots can renumber disks, so using the disk from Single-User Mode (when no Apple images are present) to Recovery (when they are), is not a good idea.

Type

fsck_apfs

and post the output. It will show which version is available in Recovery. Also, using an older fsck_apfs version on a newer macOS is problematic. My recommendation is to install macOS on an external disk which is the same as your internal disk, if you want to address this issue.

If you want to leave it as it is, that is fine, too, as longs as the corruption does not lead to data loss.

Reply

Answer 11

Loner T

Level 9

59,536 points

Aug 31, 2019 7:15 AM in response to zero7404

You need to be in Single-User Mode - Start up your Mac in single-user mode or verbose mode - Apple Support. Also, see the footnote under step 6.

Reply

Answer 12

Loner T

Level 9

59,536 points

Aug 31, 2019 1:02 PM in response to zero7404

Are you in Single-User Mode? Reboot and hold Command+S. You should see a black-and-white console. The commands should be typed on this console window.

Reply