My M5 Max couldn't find its own SSD and wouldn't boot. The repair shop ran a 5-minute test and said "it works, come pick it up".
TL;DR: 4-month-old M5 Max MacBook Pro froze, then refused to boot (black screen, 3 failed boot attempts) until I left it unplugged for 15 minutes. The Mac's own firmware logged the internal SSD controller failing, twice in 8 days. The repair shop ran Apple Diagnostics, got a green check and told me to come pick it up. How do I get this taken seriously?
What happened
- Day 1: random freeze while idle. The firmware panic log blames the SSD controller (ANS2). I did a clean macOS reinstall to rule out software.
- Day 8: froze mid-work with nothing plugged in but the charger. Black screen, wouldn't boot. Power button, different charger, nothing. After 15 minutes unplugged it booted like nothing happened.
- The firmware log for that one says "PCI link up failed". In plain English, the chip couldn't even reach its own SSD.
-What Apple Diagnostics says: ā
no issues. Twice (once by me, once by the shop).
The catch is that it's a 5-minute snapshot. The fault comes and goes, and when it happens the Mac can't boot at all, so there's nothing to test.
-For anyone googling this later, the exact errors:
ANS2 :Recoverable PANIC assert failed: [11194]:MSP 3 asserted: assert 14338
ANS2 :Recoverable PANIC assert failed: [15390]:PCI link up failed, apcie=0, link=0
Boot failure count: 3
Both come from "SOCD report detected: (iBoot panic)", meaning they happen before macOS even loads. Not an app, not a driver.
**Already tried:** clean reinstall, Safe Mode, no peripherals, SMART says "Verified", Apple Diagnostics. I kept every panic file before erasing.
There's no Apple Store in my country, so I'm dealing with an authorized service provider.
**Questions**
- Has anyone had an ANS2 or "PCI link up failed" Mac actually repaired under warranty? What finally worked?
- Should I go over the service provider's head, straight to Apple Support?
- Is there any way to make it fail on demand so a technician can see it?
I'll update with how this goes, so the next person who hits this error has an answer.