keropgive.blogg.se - Macbook pro cable failure ssd upgrade

Macbook pro cable failure ssd upgrade mac os#
Macbook pro cable failure ssd upgrade install#
Macbook pro cable failure ssd upgrade update#

They may just offer a service program and underwrite the cost of the repair. Your next step is to contact Apple for a service estimate. Separating causality from correlation is super tricky outside a repair shop where you have access to known good parts, can reconnect cables, run advanced diagnostics and see trends due to hundreds of repairs a week. (This is also the time when minor storage corruptions turn into data loss.) This is precisely when you discover hardware isn’t up to snuff and pre-existing storage failures become critical. When you run an upgrade, you change the boot process substantially.Worse, it shakes our confidence when we confront how little we can do in the face of hardware failure.

It stinks when we get a failure, so no amount of experience lessens that disappointment.

Macbook pro cable failure ssd upgrade mac os#

The OS is hobbled by it no other than needing the next write to succeed, there’s no code in the OS that intentionally breaks storage.Īs it has been for two decades of Mac OS support, coincidence is more likely than cause, here. You may have a hardware failure, but it’s not the OS that’s causing it.

Macbook pro cable failure ssd upgrade update#

We have that update on several Macs identical to yours. I have 30+ years of Mac background, I've seen SSDs biting the dust, but this is nothing I've ever seen before.

Macbook pro cable failure ssd upgrade install#

Booting from a Windows 10 Installer USB Stick does show the SSD (however despite being able to format it somehow, I wasn't able to install Windows, which would have been an attempt to at least gain access again to the SSD A).

SSD A does not show up in Disk Utility (View All Devices) and does not show up when trying to installing a fresh Mac OS.ĭiskutil list shows multiple volumes of the 32 GB USB boot stick, but not the SSD A (remember: SSD A gets listed when starting with alt key pressed and boots halfway.

Booting from Catalina USB stick drive show the exact same behaviour:.

Booting from Big Sur USB stick drive or.

Booting with alt key pressed: SSD A is listed as valid startup volume.

Apple Hardware Test on MacBook A with misbehaving SSD A = Screen stays forever black, and ends in Globe with exclamation sign and error -2003D (which is a OS recovery http connection issue, nothing which matters in the context).Ĭonclusion up to this point: The MacBook A still is perfectly fine, it’s the SSD A which is f#ck3d up (thanks to the Big Sur update).Apple Hardware Test on MacBook A with SSD B = Runs flawlessly resulting in no problems.

Swapping SSDs between the two MacBooks swaps the problem from MacBook A to B (in other words: the faulty MacBook A boots fine with the SSD B running Catalina from MacBook B, but MacBook B has the exact same boot problem with SSD A).

Attempted to boot into Safe Mode with Shift key pressed (= same behavior: stalled progress bar).

Here’s what I've tried and observed so far: I waited as much as 10 hours, but it doesn't move a single pixel.įor cross reference/examination I have another 13" MBPR (Early 2015, 2.7 GHz i5) with 512 GB SSD running Catalina perfectly fine. Let’s call this SSD A.Īfter the update the MacBook doesn’t boot up properly anymore: Apple logo and progress bar appear, everything looks normal at first, but at 50% the progress bars stalls.

It has a 512 GB SSUBX Apple Samsung OEM SSD (Model MZ-JPV5120/0A4). I have the 13" MBPR (Early 2015, 2.9 GHz i5) of my 78 year old father here, which is kind of dead after he – if he recalls correctly – performed an update from Big Sur 11.x to Big Sur 11.y (he grabs every update he gets offered, so unfortunately he doesn't pay much attention to the details). I've heard quite a few stories of Big Sur bricking older MacBooks, but I'm not quite sure in which way precisely they get bricked (motherboard or just SSD), so question is whether the following story fits into those reports: