APSF partition map corrupted - What options?

[treekram]

Quick note, the borked SSD was pulled out of a forever reliable 2010 MBP and put in ext. usb housing to connect to mac mini for diagnostic purposes.

Thanks for extensive post - I am reading now.

So the SSD was in the 2010 MBP when the problem occurred? What brand/model SSD do you have?

I made a mistake in my calculations - it would have taken 45 min. to image my 240GB SSD, not 5 minutes. A couple more cautions if you decide to do this. 1) Don't write to your boot disk - running out of space there can have bad consequences. 2) Making a mistake in the disk # designation doesn't won't hurt much when creating the image file but when you write the image to a disk you can overwrite data on the wrong disk if you have wrong disk # ("disk0" vs. "disk1"). However, the program won't write to a mounted file system so there are safeguards against making a mistake.

 

[Omega Mac]

So the SSD was in the 2010 MBP when the problem occurred? What brand/model SSD do you have?

13' MBP, Samsung EVO, 540/550 (Grey Square logo) I think - it was the 2nd Samsung in that model.

I installed another in a 15" 2010 MBP and also ext. boot SSD for MM, is a Samsung EVO 550 (Grey).

 

[Fishrrman]

I know I sound like the broken record, but once more -- if one sticks to HFS+ and eschews APFS, predicaments like the OP's are less likely.

Apple has not fully documented APFS, and just about all the "Mac utility apps" out there can't support it yet.

Stick with a known file system that works with fewer problems...!

 

[treekram]

13' MBP, Samsung EVO, 540/550 (Grey Square logo) I think - it was the 2nd Samsung in that model.

I installed another in a 15" 2010 MBP and also ext. boot SSD for MM, is a Samsung EVO 550 (Grey).

Do you mean a 840 Evo or 850 Evo? I don't think Samsung made a 540 or 550 Evo. And actually the difference between the 840 Evo and the 850 Evo is major but the 840 is pretty old - I think the 850 was introduced in 2014. And which specific model was in which specific 2010 MBP (13" vs. 15", I'm getting confused) which got corrupted?

 

[Omega Mac]

Do you mean a 840 Evo or 850 Evo? I don't think Samsung made a 540 or 550 Evo. And actually the difference between the 840 Evo and the 850 Evo is major but the 840 is pretty old - I think the 850 was introduced in 2014. And which specific model was in which specific 2010 MBP (13" vs. 15", I'm getting confused) which got corrupted?

13" 2010 MBP, 1TB EVO 850 (will double check), partition mapped nuked during 10.13.4 > 10.13.5 update.

 

[treekram]

13" 2010 MBP, 1TB EVO 850 (will double check), partition mapped nuked during 10.13.4 > 10.13.5 update.

The reason I'm interested is that certain hardware is more problematical that others, certain combinations can cause issues. I don't think your particular combination raises any red flags (other than High Sierra seems to work more reliably on newer hardware).

Considering that data loss doesn't seem too critical for you, I think a course of action is to image the SSD to a file if you have 1TB of space on a non-boot disk (even if you compress it, you won't know how much it can compress). Try First-Aid in Disk Utility. See if the partition table for the container you have in post #19 improves (error messages disappear). If it gets worse, revert back to the saved image. If it isn't fixed, try whatever disk repair software that becomes available. If that doesn't fix it and you worked with the post Disk Utility First-Aid SSD, you can revert to your saved image and try the disk repair software on that.

 

[farnoud]

Quick note, the borked SSD was pulled out of a forever reliable 2010 MBP and put in ext. usb housing to connect to mac mini for diagnostic purposes.

Thanks for extensive post - I am reading now.

I have the exact issue. Would you please keep me updated? It seems like my backup is also gone bad.