Chosen Solution
Out of nowhere suddenly my MacBook Pro got into the folder with blinking question mark mode and I wasn’t able to boot. I then started up from internet recovery, it seems that my SSD is messed up. In the process of erasing it, it got into an error like “waiting for disks to reappear” At that point I took out the SSD and used an adaptor to connect to other Mac, still I can’t erase the disk using MacOS GUID partition mapping and create a journal format partition from the other Mac while formatting, Wiping volume data to prevent future accidental probing failed - Operation failed! Update (02/08/2018)
images of my ssd and some terminal usage to check functionality of ssd
There’s only few logical problems in here: Your SSD is corruptedYour SSD has been damaged Best solution here is to try with another drive to boot, or get a new one if you still have warranty on it. If the drive is still detected but won’t read, write, boot, repair, etc, then your drive is corrupted and can’t be used sadly as this is a problem that can’t be fixed most of the time. If you can, try to at least get important files from that SSD using your other Mac if that’s still possible.
Which macOS are you using? Try to format your SSD using Disk Utility.
I had an Apple-label Samsung SSD in a Mini go bad – it could be read, sort of, but many disk operations were unsuccessful, and formatting it just crashed. So I replaced it. But eventually I was able to revive the Samsung by connecting it directly to SATA in a PC and formatting it as a Windows drive using a freebie Wintel disk formatter. Then I was able to use a USB case to connect the SSD to a Mac and format it as APFS.
I had a similar issue on a 2011 iMac. I was trying to upgrade to a SSD, and it simply would not take it. I tried multiple SSD’s, , cloning before putting it into the drive and booting from the new SSD externally(which worked when external) different format schemes, formatting using terminal, MacSales tech support, additional thermal sensor adapter, you name it, etc. Everything. I ended up putting the old HD back in and it worked fine. Total mystery. No solution.
