MBP 1,1-10,2 Recovering data from MacBook Pro with flashing folder and partition map issues

[InRecoveryWeTrust]

I believe I am in quite a lot of trouble, and I am in desperate need for some professional advice. It would mean a lot to me if the good people of this forum can share their expertise with me.

My MacBook Pro (Early 2015) started showing me a flashing folder with a question mark. After multiple failed attempts to install a macOS to an external drive through Recovery (tried both command+R and option+command+R; I kept receiving PKDownloadError error8), I finally found a workaround and successfully created a bootable flash drive using my Windows PC. Before using that flash, I tried everything I could in Disk Utility (through Recovery Mode), be it the Restore function or create image function, but nothing worked. I was unable to copy my internal SSD to my external drive, so I looked for recovery solutions that I could use through my bootable flash. I installed Mojave (macOS 10.14) on the flash, so I used the latest compatible versions with that OS. I could've installed a newer OS like Monterey, but thought it would be the smartest to use the same version that was last on my Mac, and that was Mojave.

I tried Disk Drill and SuperDuper!, but neither worked. SD! simply never started the copying process, while DD couldn't complete the whole process. I tried to use the byte-to-byte function, and it would make progress, but eventually the internal SSD would eject and the whole process would break. Interestingly enough, the size of both backups was almost identical (one was 4.64GB, the other 4.63GB). It's worth noting that after the internal SSD ejected, it doesn't show up in Disk Utility.

When all is "well", the Disk Utility tree looks as follows:

Internal
Apple SSD SM0128G Media
↳ Container disk2
↳ Macintosh HD

Disk Images
Apple disk image Media
↳ macOS Base System

I am able to see that Macintosh HD is mostly used up. After multiple failed attempts with recovery software, I finally made the decision to run Disk Utility's First Aid in the booted OS. I ran it on "Apple SSD SM0128G Media", and this is what I got:

"First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery. Click Done to continue."
and
"Problems were found with the partition map which might prevent booting"

I then booted into Internet Recovery (option+command+R), then into Disk Utility, and I ran First Aid on the same Apple SSD SM0128G Media volume. After some 2 hours, this is what I got: "First Aid process has failed. If possible back up the data on this volume. Click Done to continue" and "Problems were found with the partition map which might prevent booting Couldn't mount disk : (69842) Operation failed..."

Now, I am booted in the OS through the flash, and I tried selecting the Macintosh HD in the Folder sidebar, copied it, and tried pasting it on my external HDD. The process took some time, but eventually, the internal SSD ejected itself, and now I have a Finder pop up window that says: You may need to enter the name and password for an administrator on this computer to change the item named "Macintosh HD"

The internal SSD is once again not visible in Disk Utility. Should I click Stop or Continue on the pop up?

With this post, I am seeking advice about what my options are for data recovery. It's looking pretty ugly so far, but then, I am just a casual user. I am capable of following step-by-step instructions, so if there is a complex method to recover data from my SSD, and I can do it myself, please let me know. It's such a horrible situation to be in, and worst of all, the most important files to me are my browser bookmarks and some text files. Besides that, I have my Downloads folder with some images and other file formats.

What is possible and what isn't? From my understanding, the fact that it's an SSD complicates things, and it being in the APFS format makes some things outright impossible. I have no clue what's possible. During my Googling about, some people were talking about manually fixing the partition map, but I also came across what looks to be some wizardry: https://discussions.apple.com/thread/250837011?sortBy=rank

Please let me know what my options are. What's safe to do, what isn't, and is that solution from Apple Discussions a viable option.

Huge thanks to everyone who takes the time out of their day to reply =)

 

[Bigwaff]

Based on your efforts so far, it sounds as if your internal SSD is definitely corrupted (and possibly failing).

If you have access to another Mac, you could boot your MBP in Target Disk Mode. Hopefully the partitions will mount on the other Mac and you can copy data off. Then you can erase your internal SSD storage and reinstall macOS from clean.

Transfer files between two Mac computers using target disk mode

You can connect an Intel-based Mac to another Mac using a USB, USB-C, or Thunderbolt cable, then transfer files.

support.apple.com

If this your only Mac, options limited...

Since the internal NVMe SSD in these models is user replaceable, you can purchase replacement SSD bundled with an external enclosure for your current internal SSD. Hopefully, your current internal SSD partitions will mount using the external enclosure

OWC 240GB Aura N2 SSD Complete Upgrade Solution for... at MacSales.com

S4DAB4MB02K 240GB OWC Aura N2 SSD Complete Upgrade Solution for Select 2013 & Later Macs. With tools & OWC Envoy Pro Enclosure for MacBook Air (Mid 2013 - 2017), MacBook Pro (Retina, Late 2013 - Mid 2015)

eshop.macsales.com

caveat... it is not uncommon later macOS versions will not install w/out firmware updates, which are included and installed as part macOS install. Updating to the latest version of macOS using the currently installed Apple OEM NVMe SSD is recommended in order to get necessary firmware updates. Sort of a chicken-n-the-egg when your current internal SSD is failing or corrupted. You may first have to purchase a used Apple OEM NVMe SSD to replace your current internal, especially if you plan to eventually upgrade to latest supported version of macOS your hardware supports.

 

[Wowfunhappy]

^ I'll add that you should probably stop using that Mac immediately, until you're in a position to use Target Disk Mode to try to extract the most important data. Do not put _any_ more stress on the drive than necessary.

 

[f54da]

if byte/block level copy fails, seems like a failing SDD? Maybe boot off of a recovery partition and use DriveDX to check SMART status of drive?

Usually best practice with fs-level corruption is block-level copy to another disk which can then be mounted elsewhere and analyzed, but with failing hardware i'd guess it's better to minimize R/W traffic altogether, so maybe mount (via target disk mode) + selective copy is best? Preferably even copy via terminal to avoid unnecessary r/w from finder trying to load metadata and ds_store

Note that there are drive cloing utils that can skip bad blocks or power-cycle drives as part of the cloning process, that might be another option. I'm not sure about specific tools here, i remember ancient ddrescue but surely there must be something more modern.

 

[InRecoveryWeTrust]

Great advice from everybody!

I made the decision to take the matter in my own hands, and I successfully copied the most important files using Terminal.

Now, I can play around. I still want to try to make a healthy copy of my internal SSD. As I was told, by using the Mac I am putting stress on the internal SSD and things could go south very quickly. They did! I no longer see Macintosh HD in Disk Utility, and I also don't see it when running ls /Volumes. Before all of this, Disk Utility said it was disk2s1. Now, when running diskutil list, I only see untitled under disk2, and it's 5MB.

Can I ask for advice whether to use ddrescue, OpenSuperClone, or TestDisk?

If you have other suggestions, please let me know. I am trying to make the most out of this situation, and hopefully it can be of some value to those that find themselves in the same situation.

 

[f54da]

From what i can see OpenSuperClone seems to be more capable than ddrescue. I'd really check SMART status on the drive first though, with drivedx.

 

[InRecoveryWeTrust]

From what i can see OpenSuperClone seems to be more capable than ddrescue. I'd really check SMART status on the drive first though, with drivedx.

The last time I checked using DriveDX, it said the SMART status was OK and overall health rating was Good. But it did state there were ~1400 I/O errors, and the next time I booted up it said there were 200. I haven't used DriveDX since.

 

[InRecoveryWeTrust]

I am trying to make a copy using OpenSuperClone. I created a bootable flash, and am now booted into it. However, I cannot mount or access my external HDD because it's formatted in APFS. Do I need to reformat this drive in a different format? Or how exactly am I meant to do this whole thing?

My goal is to copy my internal SSD to my external HDD.
I realized that the format of my external HDD doesn't matter, so I formatted it to exFAT. Now, I'm confused when using OSC, because I'm not sure what to select as the source drive:

1. sda (numbers) sense-data 05 24 00
2. sdb (numbers) Generic USB Flash Disk [letters + numbers]
3. sdc (numbers) [external HDD name]
4. sdd (-3) APPLE SD Card Reader

In Terminal, (sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL), my internal drive is sda -> sda2 apfs (112.8G).

 

[f54da]

>I realized that the format of my external HDD doesn't matter
I mean format won't matter since it'll all be overwritten anyway, right? ddrescue/opensuperclone will copy at the block level anyway so it will end up with same partition table and filesystem as source.

>I'm not sure what to select as the source drive:
Don't understand the question, assuming your 112G apfs drive is the one that is corrupted and you want to clone, then choose sda as source? Also since it works off of the raw block device (/dev/sda), you probably don't want to have it mounted.

 

[InRecoveryWeTrust]

>I realized that the format of my external HDD doesn't matter
I mean format won't matter since it'll all be overwritten anyway, right? ddrescue/opensuperclone will copy at the block level anyway so it will end up with same partition table and filesystem as source.

>I'm not sure what to select as the source drive:
Don't understand the question, assuming your 112G apfs drive is the one that is corrupted and you want to clone, then choose sda as source? Also since it works off of the raw block device (/dev/sda), you probably don't want to have it mounted.

You were correct, I just had to select sda. I was confused because it didn't have the typical Apple SSD [model] media name that I was used to.

Now I have a second problems in OSC. I cannot select the internal drive as a source at all. OSC Terminal doesn't see sda at all. In macOS Recovery, I see my internal drive when running diskutil list... but I don't know how to see it in OSC.

 

[f54da]

how exactly are you running opensuperclone? It only works with linux, so if you're running it in a VM you need to pass the drive through

 

[InRecoveryWeTrust]

how exactly are you running opensuperclone? It only works with linux, so if you're running it in a VM you need to pass the drive through

I created a bootable flash. So, I just have the flash plugged, in, power the Mac on, hold alt, and select it.

This is so complicated, and something weird is clearly causing this. I am uncertain whether my internal SSD is even failing at this point. Since I am no longer able to access it through macOS Terminal, I found a way to do so through OSC in virtual disk mode. I can access and see all the files and folders on Macintosh HD (which is no longer visible anywhere). However, I run into the same problem as before, where the internal disk fully disconnects when I try copying files from it. Something is trigerring it to disconnect, but I don't know what. I feel like there are specific OSC settings that I need to configure, but I have been unable to get any help regarding this.

It feels like my files are there, on the internal SSD, but I can't copy them because the internal drive cannot handle the copying process :/

 

[macnavarra]

I believe I am in quite a lot of trouble, and I am in desperate need for some professional advice. It would mean a lot to me if the good people of this forum can share their expertise with me.

My MacBook Pro (Early 2015) started showing me a flashing folder with a question mark. After multiple failed attempts to install a macOS to an external drive through Recovery (tried both command+R and option+command+R; I kept receiving PKDownloadError error8), I finally found a workaround and successfully created a bootable flash drive using my Windows PC. Before using that flash, I tried everything I could in Disk Utility (through Recovery Mode), be it the Restore function or create image function, but nothing worked. I was unable to copy my internal SSD to my external drive, so I looked for recovery solutions that I could use through my bootable flash. I installed Mojave (macOS 10.14) on the flash, so I used the latest compatible versions with that OS. I could've installed a newer OS like Monterey, but thought it would be the smartest to use the same version that was last on my Mac, and that was Mojave.

I tried Disk Drill and SuperDuper!, but neither worked. SD! simply never started the copying process, while DD couldn't complete the whole process. I tried to use the byte-to-byte function, and it would make progress, but eventually the internal SSD would eject and the whole process would break. Interestingly enough, the size of both backups was almost identical (one was 4.64GB, the other 4.63GB). It's worth noting that after the internal SSD ejected, it doesn't show up in Disk Utility.

When all is "well", the Disk Utility tree looks as follows:

Internal
Apple SSD SM0128G Media
↳ Container disk2
↳ Macintosh HD

Disk Images
Apple disk image Media
↳ macOS Base System

I am able to see that Macintosh HD is mostly used up. After multiple failed attempts with recovery software, I finally made the decision to run Disk Utility's First Aid in the booted OS. I ran it on "Apple SSD SM0128G Media", and this is what I got:

"First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery. Click Done to continue."
and
"Problems were found with the partition map which might prevent booting"

I then booted into Internet Recovery (option+command+R), then into Disk Utility, and I ran First Aid on the same Apple SSD SM0128G Media volume. After some 2 hours, this is what I got: "First Aid process has failed. If possible back up the data on this volume. Click Done to continue" and "Problems were found with the partition map which might prevent booting Couldn't mount disk : (69842) Operation failed..."

Now, I am booted in the OS through the flash, and I tried selecting the Macintosh HD in the Folder sidebar, copied it, and tried pasting it on my external HDD. The process took some time, but eventually, the internal SSD ejected itself, and now I have a Finder pop up window that says: You may need to enter the name and password for an administrator on this computer to change the item named "Macintosh HD"

The internal SSD is once again not visible in Disk Utility. Should I click Stop or Continue on the pop up?

With this post, I am seeking advice about what my options are for data recovery. It's looking pretty ugly so far, but then, I am just a casual user. I am capable of following step-by-step instructions, so if there is a complex method to recover data from my SSD, and I can do it myself, please let me know. It's such a horrible situation to be in, and worst of all, the most important files to me are my browser bookmarks and some text files. Besides that, I have my Downloads folder with some images and other file formats.

What is possible and what isn't? From my understanding, the fact that it's an SSD complicates things, and it being in the APFS format makes some things outright impossible. I have no clue what's possible. During my Googling about, some people were talking about manually fixing the partition map, but I also came across what looks to be some wizardry: https://discussions.apple.com/thread/250837011?sortBy=rank

Please let me know what my options are. What's safe to do, what isn't, and is that solution from Apple Discussions a viable option.

Huge thanks to everyone who takes the time out of their day to reply =)

Have you traveled with you're Laptop on a plane so... data corruption is likely lol, iPads.. Amazon kindle fire reader in space are space clocked/"down7Up clocked!" Hummm ...