Ga door naar hoofdinhoud

Released October 24, 2011 / 2.2, 2.4, or 2.5 GHz Quad-core Intel Core i7 Processor

423 Vragen Bekijk alle

SSD Unreadable after battery died.

Ok, here’s a weird one:

Last week I was using my 2011 15” MBP as normal with no issues on battery power. I was checking email when a family emergency presented itself, so I left the MBP on the kitchen counter.

Needless to say, when I returned, the MBP had gone into deep sleep as the battery had died. I plugged in my power adapter and waited until the battery was fully charged. Upon restart, I noticed that the computer was EXTREMELY sluggish, to the point of non-usability, so I restarted the MBP. After the chime, I got a dim grey screen with no Apple logo. NVRAM resets and SMC resets did not improve the situation.

I removed the Samsung SSD and replaced it with the old hard drive I had removed years ago, and the MBP booted as normal, ruling out other possible hardware issues. I installed the suspect Samsung SSD into another test 13” 2012 MBP, and it exhibited the same issue, although after about 5 minutes I got the blinking folder with question mark symbol.

I have also tried placing the SSD in an external USB enclosure, but in this configuration, the SSD is invisible to Finder, Disk Utility and Terminal.

Is this SSD toasted?

The OS on the suspect Samsung SSD is High Sierra, and the OS on the working 13” MBP is Mojave.

Update (01/03/2019)

Also, I got no prompts from any of the folowing OS's stating that the drive could not be read and needed to be initialized or formatted when connected as an external drive in a USB enclosure: Mac OS El Capitan, macOS Mojave, mac OS Sierra, Window 8, Windows 10 (yes, I tried it on 5 different machines). Not even a nudge to indicate that the computer recognized a device hooked up to USB.

Beantwoord! Bekijk het antwoord Dit probleem heb ik ook

Is dit een goede vraag?

Score 1

Commentaar:

Can you run a test on the SSD in question? It's likely that the SSD failing and computer dying at the same time is just a coincidence and not related at all.

door

Hey Alec, the SSD doesn't mount or show up in any software I've tried. macOS Finder doesn't see it, macOS Disk Utility doesn't see it, even Terminal doesn't see the drive when I execute "diskutil list". I even tried connecting it to a PC running Windows 10, and it didn't show up there either.

door

Voeg een opmerking toe

2 Antwoorden

Gekozen oplossing

I don’t think your drive is dead!

Both the 13” & 15” unibody systems have issues with the HD SATA cables. The first generations did not support SATA III (6.0 Gb/s) I/O. The original Apple drives where SATA II (3.0 Gb/s) so they never pushed the limits of the cable. Even some SATA III drives 5200 RPM drives still didn’t push the limits of the cable, but SSD’s do!

In addition, the thin foil wires within the cable can breakdown. This is when people over bend the cable trying to crease them instead of making even smooth arcs.

So the first thing is to replace the HD SATA cable with the newer version. For the 15” MacBook Pro 15" Unibody (Mid 2012) Hard Drive Cable and for the 13” MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable And yes! These are for the 2012 models and are fully workable in the 2011 models.

In addition to the new cable you’ll want to place a strip of electricians tape on the uppercase where the cable crosses over as the rough surface can also wear the cable. On the 15” models you need to make sure the plastic bottom lid mid plane clip near the drive is not broken as the pressure of the bottom case can cut into the cable where it crosses over the optical drive.

Once you have replace the cable we now have the second issue:

When you upgraded to High Sierra the OS installer updated the drive from HFS+ to APFS and the systems firmware was also updated. On your 13” system which you’ve already upgraded to Mojave it too would have upgraded the SSD to APFS but the 2nd version and as far as I’ve found the system won’t read High Sierra APFS SATA drives.

As for fixing things: I would put the drive back into your 15” and using the recovery partition run Disk Utility to see if you can at least get the drive running so you can recovery anything important. Once you’ve done that reformat the drive and re-install the OS. You might want to redo the full drive using an external bootable USB OS installer drive How to create a bootable macOS Sierra installer drive

Frankly, I don’t recommend running High Sierra or Mojave on SATA based systems as Apple has not addressed the queuing issues which could have been the root issue in your case.

MacBook Pro 15" Unibody (Mid 2012) Hard Drive Cable Afbeelding

Product

MacBook Pro 15" Unibody (Mid 2012) Hard Drive Cable

$19.99

MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable Afbeelding

Product

MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable

$34.99

Was dit antwoord nuttig?

Score 2

Commentaar:

One last point SSD's need free space to work effectively! You don't want to run your drive without having about 1/4 of it free. Even smaller drives need more space 1/3. This is do to how the drives do wear leveling so when the drive is overly full you tend to cause the drive to work much harder moving data around to even out the wear.

door

He plugged the device into different PC's (Mac and Windows) and reports that it isn't showing up in Disk Manager or Disk Utility. He also said his older device worked on his Mac Book Pro. Do you still think it's the hard drive cable?

door

Windows systems won't recognize either HFS+ or APFS drives all it will do is ask if you want to format it so Windows can use the drive. The only exception would be if you had the needed Windows driver to allow it to recognize HFS+ (APFS still is not workable).

Mac Systems which have not been updated to High Sierra won't have the newer firmware as such they too won't recognize the APFS drive!

I would still replace the drive cable then run Disk Utility either from the drive (OS Recovery) or a bootable High Sierra OS installer drive.

But as I said, I would make a full backup and then redo the drive back to HFS+ and Sierra. I've seen too many problems with Hight Sierra and Mojave on SATA based systems.

To be clear if you had a PCIe/AHCI or PCIe/NVMe SSD I would run the very latest OS without any issue!

door

That makes sense. I just hope his drive shows up in disk utility so he can back it up.

door

Dan and Alec, the drive does not show up when I boot from Internet Recovery. All that shows up is the disk image that the MBP is booting from (disk0). The drive is a 500GB Samsung 850 EVO and it had over 200GB of free space on it.

Dan, I should also point out that holding down the Option key at startup gives me no options to boot from, so booting from the recovery partition on the physical drive is impossible.

door

11 commentaren meer tonen

Voeg een opmerking toe

I have the same problem after a short cut the SSD wont boot, The SSD lights up as an external HD but wont boot in other macs or recovery mode. I think it also has something to do with Mojavo and the security mode. I read somewhere that sometimes Mojavo /macos can activate the disk as unreadable as a security measure when it is not proper ejected without a password etc. Dont have enough inside knowledge in this matter but since my SSD disk wont show up properly after one restart it seems more and more unlikely that it is a cable issue but more and more a Mojavo/Macos security precaution.

Was dit antwoord nuttig?

Score 0

Commentaar:

No magic within Mojave OS for security. You might have hit an issue with the newer file system intro'ed in High Sierra and also used in Mojave.

Let me explain... You have System A which you have Mojave installed and you plugged in an external SSD drive (USB, FirWire or Thunderbolt connected which you formatted with APFS. You properly shut down your system & drive. Now you take this drive to System B which has Sierra or older OS installed. You won't be able to access the drive as the older MacOS's have no clue how to read the new APFS file system (they are HFS+ based).

So how do I fix this the magic is within the systems firmware! You need to have run the OS installer directly on the system for the installer to upgrade your systems firmware! Of course that means you needed to have installed Mojave!

But my system doesn't support it! Now what! You'll need to reformat the drive to HFS+ to make it work on System B. Or... You could still install Mojave! Using this DosDude He had found a way to get it to install on the older Mac systems. But there are a few issues you really need 4 GB of RAM or more and a fair amount of free space on your boot drive for V-RAM use.

door

Voeg een opmerking toe

Voeg je antwoord toe

Ruben Reynoso zal eeuwig dankbaar zijn.
Weergavestatistieken:

Afgelopen 24 uren: 1

Afgelopen 7 dagen: 7

Afgelopen 30 dagen: 42

Altijd: 2,689