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

Sep 30, 2018 10:30 AM in response to shannon.young

Prosoft Data Rescue may be able to recover through a corrupted partition table. You will need a drive larger than the original. http://www.macsales.com/ offers lots of good prices on hard drives. I would only try to use it or Micromat's Techtools Pro.


One thing you have to be really careful of with 10.13 and higher is when installed, it likes to reformat drives into APFS if they are solid state. Having a regular hard drive with a Newertech external drive reader can help immensely.

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.


** 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 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.

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 10, 2018 2:30 PM in response to shannon.young

shannon.young wrote:


could I:

  1. Boot the troubled Mac using the external HDD that we clean installed Mojave on and use Disk Utility to erase and initialise the internal drive?
  2. Once erased and initialised, boot from the USB Installer (with Mojave installer app) and select the internal HDD.
  3. Start a fresh account (same login/username), then instead of a restore, transfer the data I want and re-install the Apps I want. Having a clean slate to start from.

Yes, this should work.


shannon.young wrote:


Also, aside from having Time Machine backups (which I will from now on), how do you go about installing a major OSX update like Mojave.

I usually install macOS upgrades


  • first, on a test Mac, which I am willing to wipe clean, without any data loss,
  • second, if you do not have a spare Mac, on an external disk, without touching any internal versions/files
  • third, once the results of the first two are acceptable, upgrade critical Macs to the new version


I still run Mavericks, Yosemite, Sierra (and with some exceptions like Snow Leopard, etc.). I currently have


  • High Sierra on one Mac,
  • Mojave on an external disk


I will not install Mojave on any critical machines, till 10.14.3+. This is typically, a two/three month wait. I also download and preserve each macOS version installer (I have the last PPC version, and all Intel versions).

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

Loner T wrote:


Run


sudo fsck_hfs -n -l /dev/rdisk0s2

** /dev/rdisk0s2 (NO WRITE)

Executing fsck_hfs (version hfs-407.200.4).

0000: dd78 9dc1 4bea 96e7 0100 0000 0000 0000 |.x..K...........|

0010: 1f00 0000 0000 0000 0100 0080 0000 0000 |................|

0020: 4e58 5342 0010 0000 18d8 4307 0000 0000 |NXSB......C.....|

0030: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

0040: 0200 0000 0000 0000 b449 0b89 2b37 4eee |.........I...7N.|

0050: 89b9 693e 227e 46d7 d9fa 0300 0000 0000 |..i...F.........|

0060: 2000 0000 0000 0000 1801 0000 346c 0000 |............4l..|

0070: 1100 0000 0000 0000 c1a4 0900 0000 0000 |................|

0080: 4400 0000 e207 0000 4200 0000 0200 0000 |D.......B.......|

0090: a707 0000 3b00 0000 0004 0000 0000 0000 |................|

00a0: 2fa7 1100 0000 0000 0104 0000 0000 0000 |................|

00b0: 0000 0000 6400 0000 0304 0000 0000 0000 |....d...........|

00c0: 0604 0000 0000 0000 0000 0000 0000 0000 |................|

00d0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

. . .

01f0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

Oct 5, 2018 6:07 PM in response to Loner T

We are going to try and run a non-intrusive fsck first.


sudo fsck_apfs -n -l /dev/rdisk0s2


and post the output.

** 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 MacHD was formatted by hfs_convert (945.200.129) and last modified by .

** 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 hfs_convert (945.200.129) and last modified by .

** 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.

** Performing deferred repairs.

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

Oct 5, 2018 8:13 PM in response to shannon.young

shannon.young wrote:


No words can express how happy I am to see my old HDD mounted! A million thank you's is not enough.


Where Apple 'Support' left me high and dry, you saved the day and all the photographic memories of our first child.

I am very glad to see you have your files back.

shannon.young wrote:



I am copying off the most valuable thing to me which are the photos to the clean Mojave install.

We are not done yet. Please copy files to at least two different disks, if possible. Also, your mechanical HDD may be failing.


The 2012 13-in Mac I have has had HDD issues. I replaced my original HDD with an SSD (a 1TB Samsung 850 Pro). It makes the Mac work much better and provides a more reliable machine. You can buy any suitable brand/size SSD that works for you. Also, set up a Time Machine with at least two separate destinations, which alternate for backups. For every Mac that I have, I use two destinations for safety.

Oct 10, 2018 11:40 AM in response to shannon.young

What we want to do is


  • erase and initialize the whole internal disk of the troubled MAC to Apple HFS+ using the working Mac's Disk Utility
  • install a clean copy of Mojave and verify that it can boot and function normally. Use a login/username that is different from the one you used previously on the trouble Mac
  • If you are satisfied with Mojave, then we can use Time Machine to restore User Settings and applications and files to the newly install Mojave and very that you have all the data
  • also, if you considering an upgrade from the mechanical HDD to an SSD, you should do this first, before we install a clean copy of Mojave

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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 Account.