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

Upgrade from High Sierra to Mojave corrupted my partition table, unusable MBP.

It's a long post, but I am listing everything I have done so far.

I performed an upgrade to Mojave (day one release from App store), the app installed and I ran through the setup steps, I left it running unattended as it was ‘52 minutes remaining’ I came back to a ‘Disk management error’ (I did not catch the error number at the time), I restarted the machine, and since that point it boots to the Apple logo and the progress bar reaches about ~75% complete before turning into the prohibited symbol.


I have scoured the Apple Support forums and seen some really helpful suggestions from the community, which have led me to the point I am at now, and I’m hoping someone with some greater experience can help, calling out community member LonerT as some posts he has helped others with seem to be part of my issue.


Stupid mistake on my part is not having any backup whatsoever, and the HDD contains family images which is why I’m reluctant to give up and reformat the drive.

I am not too bothered about recovering the whole drive, a satisfactory outcome for me would be the drive is mountable and I can extract the data I want, and from there I don't mind a fresh install.


So here is where I am at, and what I have done:

  • I can load into recovery mode (cmd + r).
  • In disk utility I am only able to see the hardware name of my internal drive (APPLE HDD HT…), in the view menu I ensured ‘Show all devices’ is enabled, still no volume name for which I would expect to see ‘Macintosh HD’.
  • I can see the OS X Base system.
  • At this point I contacted official Apple support (online), once I explained I could see no drive names listed under my internal HDD, they stopped helping and said I would need to reinstall the OS.
  • Tried Target disk mode on another Mac with OSX High Sierra, it could only see the hardware name of my internal drive (APPLE HDD HT…), no volumes.
  • Tried Internet recovery mode, the globe 'spins' then the machine reboots back to into the prohibited symbol.

Output from Recovery mode Disk Utility on the Internal HDD

First Aid found corruption that needs to be repaired.

Checking Core Storage Physical Volume partitions

Problems were found with the partition map, which might prevent booting.

Output from diskutil list


/dev/disk0 (internal, physical):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
GUID_partition_scheme
*500.1 GB
disk0

1:
EFI EFI


209.7 MB
disk0s1

2:
Apple_CoreStorage
499.2 GB

disk0s2

3:
Apple_Boot Recovery HD
650.0 MB disk0s3

/dev/disk1 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
GUID_partition_scheme
+2.1 GB

disk1

1:
Apple_HFS OS X Base System 2.0 GB

disk1s1

/dev/disk2 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+5.2 MB
disk2

/dev/disk3 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB
disk3

/dev/disk4 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB disk4

/dev/disk5 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled +524.3 KB
disk5

/dev/disk6 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+2.1 MB

disk6

/dev/disk7 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB
disk7

/dev/disk8 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB
disk8

/dev/disk9 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+12.6 MB disk9

/dev/disk10 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+4.2 MB disk10

/dev/disk11 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+1.0 MB disk11

/dev/disk12 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+2.1 MB

disk12

/dev/disk13 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB disk13

/dev/disk14 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB
disk14

/dev/disk15 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+1.0 MB

disk15

/dev/disk16 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+6.3 MB

disk16

/dev/disk17 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+6.3 MB disk17

/dev/disk18 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled


+524.3 KB disk18

/dev/disk19 (disk image):

#:
TYPE NAME

SIZE

IDENTIFIER

0:
untitled +2.1 MB
disk19

Output from diskutil cs list

No CoreStorage logical volume groups found

Output from gpt show disk0

-bash-3.2# gpt show 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 975093952 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

975503592 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

976773128 7

976773135 32 Sec GPT table

976773167 1 Sec GPT header

I booted into Gparted, and what I'm hoping is a positive sign is it can see 'Macintosh HD', but on the flip side a file system of 'unknown' does not fill me with hope. This is where I stopped and thought it's best for someone with better experience to help guide me through any potential data recovery.


User uploaded file

Thank you in advance.

Tools at my disposal:

  • A secondary MBP (same-ish year)
  • Firewire 800 cable
  • External USB with GParted ready to boot
  • External USB blank 150gb HDD

MacBook Pro, macOS High Sierra (10.13.6)

Posted on Sep 30, 2018 9:28 AM

Reply

Similar questions

61 replies

Oct 4, 2018 1:01 PM in response to Loner T

-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

Checking booter partitions

Checking booter partition disk0s3

Verifying file system

Volume is already unmounted

Performing fsck_hfs -fn -x /dev/rdisk0s3

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

The volume Recovery HD appears to be OK

File system check exit code is 0

Restoring the original state found as unmounted

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Problems were encountered during repair of the partition map

Error: -69808: Some information was unavailable during an internal lookup

Oct 4, 2018 1:07 PM in response to shannon.young

shannon.young wrote:


Checking Core Storage Physical Volume partitions

Problems were encountered during repair of the partition map

Error: -69808: Some information was unavailable during an internal lookup


This is strange.


DU needs to check disk0s2 and figure out that it is a CS and then run fsck_cs.


Can you post the output of


sudo dd if=/dev/rdisk0s2 count=5 2>/dev/null | hexdump -C

Oct 4, 2018 2:29 PM in response to Loner T

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage Macintosh HD 499.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3



/dev/disk1 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD +498.9 GB disk1

Logical Volume on disk0s2

E1B1D7A3-076F-43A1-AE71-68D5E30B10C7

Unencrypted

Oct 4, 2018 2:37 PM in response to shannon.young

If your troubled Mac is properly connected via the FW800 cable and shows the floating FW/USB icon, then you should also see an external disk.


Also, you have another option. Put the working Mac in TDM, reboot your troubled Mac, and hold Alt/Option. Do you see the working Mac's internal disk as a selection in the troubled Mac's Boot Manager? If yes, select it and post the output of


diskutil list

Oct 4, 2018 3:05 PM in response to Loner T

The second option worked better, I could see the working Mac's internal disk on the troubled Mac's Boot manager.


I booted into it and here is the output of diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 499.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3



/dev/disk1 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage Macintosh HD 499.2 GB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s3



/dev/disk2 (external, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD +498.9 GB disk2

Logical Volume on disk1s2

E1B1D7A3-076F-43A1-AE71-68D5E30B10C7

Unencrypted

Oct 5, 2018 6:35 AM in response to shannon.young

You have the troubled Mac booted from a 'full' macOS installation using the internal disk of the working Mac. Disk0 is the one that is the internal boot disk of the troubled Mac. Currently, you are using an external boot disk (working Mac's internal disk). We need to see what is in the partition header of the CS on the the troubled Mac's internal disk, which is currently disk0.


This is the one we are interested in. Notice that it does not have 'Macintosh HD' next to CS.

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 499.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

Mojave upgrade did something bad, which it should not/must not do.

Oct 5, 2018 10:26 AM in response to Loner T

Loner T wrote:


Can you try the dd command on disk0s2?

Loner T wrote:


sudo dd if=/dev/rdisk0s2 count=5 2>/dev/null | hexdump -C

Can you confirm that with the Mac's hooked up (troubled Mac booted into working Mac from Boot manager using the FireWire cable) that you want me to run the same command as instructed before? (I assume so Hexdump will work)


The only difference from your original comment and your most recent one is disk0s2 and rdisk0s2.

I just want to ensure I'm running the correct command.

Oct 5, 2018 10:46 AM in response to Loner T

00000000
dd 78 9d c1 4b ea 96 e7
01 00 00 00 00 00 00 00
|.x..K...........|

00000010
1f 00 00 00 00 00 00 00
01 00 00 80 00 00 00 00
|................|

00000020
4e 58 53 42 00 10 00 00
18 d8 43 07 00 00 00 00
|NXSB......C.....|

00000030
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

00000040
02 00 00 00 00 00 00 00
b4 49 0b 89 2b 37 4e ee
|.........I..+7N.|

00000050
89 b9 69 3e 22 7e 46 d7
d9 fa 03 00 00 00 00 00
|..i>"~F.........|

00000060
20 00 00 00 00 00 00 00
18 01 00 00 34 6c 00 00
| ...........4l..|

00000070
11 00 00 00 00 00 00 00
c1 a4 09 00 00 00 00 00
|................|

00000080
44 00 00 00 e2 07 00 00
42 00 00 00 02 00 00 00
|D.......B.......|

00000090
a7 07 00 00 3b 00 00 00
00 04 00 00 00 00 00 00
|....;...........|

000000a0
2f a7 11 00 00 00 00 00
01 04 00 00 00 00 00 00
|/...............|

000000b0
00 00 00 00 64 00 00 00
03 04 00 00 00 00 00 00
|....d...........|

000000c0
06 04 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

000000d0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

*

000003d0
00 00 00 00 00 00 00 00
7c cd 06 00 00 00 00 00
|........|.......|

000003e0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

*

000004f0
00 00 00 00 00 00 00 00
3b 01 00 00 00 00 00 00
|........;.......|

00000500
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

*

00000520
01 00 04 00 08 00 00 00
00 00 00 00 00 00 00 00
|................|

00000530
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
|................|

*

00000a00

Oct 5, 2018 12:03 PM in response to Loner T

Executing fsck_cs (version 546.50.1)

** Checking volume

** disk0s2: Scan for Volume Headers

Invalid Volume Header @ 0: invalid field value

Invalid Volume Header @ 499248102912: unsupported format

** disk0s2 did not complete formatting as a CoreStorage volume

The secondary (working) MBP I am borrowing from work so I can keep hold of for a while, the only critical information/data is family photos which I would like to retrieve, aside from that I don't care much for restoring the whole system. I have no backup whatsoever (in hindsight very very stupid).

How would I go about installing fresh Mojave onto the external HDD? Is it the same method as creating a bootable live CD?

Oct 5, 2018 1:53 PM in response to Loner T

Thanks I will try this out.


What do you make of this article? It seems to be the situation I'm in.


Specifically this:

Well, there’s the cause. I suppose this is rather a good thing, as the volume was not empty and Time Machine gave no warning that formatting was in it’s plan. So what about the data? Turns out that a simple mount -t hfs /dev/disk1s3 /tmpmntpoint attached the volume successfully and all of the data was still there.

Would it be destructive to try this? Also do you know where/what the article is referring to by using a temporary mounting point /tmpmntpoint, does it have to be a specific location on a disk?

Oct 5, 2018 2:35 PM in response to shannon.young

You can create a directory under /Volumes, using


sudo mkdir -p /Volumes/tmpmntpoint


and then run


mount -t hfs /dev/disk0s2 /Volumes/tmpmntpoint

The mount operation does modify the file system with timestamps, but you should be fine. The link used it on a disk slice that was being converted from HFS+ to CS. In your case, it was from CS to APFS, which can cause problems. Try it. If it does not work, we need to try and do the APFS conversion and see if the conversion process will also repair it.

Upgrade from High Sierra to Mojave corrupted my partition table, unusable MBP.

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