Live data from Hacker News

macOS Sonoma Boot Failures

github.com

21–30 of 290 posts

Re: macOS Sonoma Boot Failures

#22
post #16

Abstraction Layers. We've gotten to point with the huge number of abstraction layers (and now AI as well) that troubleshooting what causes system to do what it did, has become so unwieldily difficult to diagnosis.

This doesn’t seem to be the problem here? It’s an issue of having a combinatorial number of versions to test when upgrading software and firmware.

Re: macOS Sonoma Boot Failures

#23

Interestingly I ran into this exact problem with my work MacBook Pro M1 upgrading to Ventura 13.6 and assumed it was a totally isolated incident. I don't have a dual-boot setup either, just a single macOS install. The computer was connected to a Thunderbolt Display during the update which I assume had the same effect of changing the refresh rate to something other-than-ProMotion that the linked article mentions. I ha…

> I also wasted far too much time trying to get the DFU restore to work before discovering that you cannot use a Thunderbolt cable — it has to be done using a plain USB-C cable, otherwise the Apple Configurator simply won't detect the other Mac. I would have expected a Thunderbolt cable to be required, if either was. This is quite surprising to me. Usually, the more capable (higher bandwidth) cable works if one isn’t…

I am currently restoring an MBP using Configurator and a thunderbolt cable. You definitely can use one, perhaps your TB cable is buggered ?

Re: macOS Sonoma Boot Failures

#24

Not sure if related, but my 2020 M1 macbook air bricked a week or so after upgrading to Sonoma. I was suspicious if this was related to the update. Luckily the logic board was replaced for free under warranty laws here, though it put me off switching to iphone which I was a day away from doing.

Seems like a weird rationale. Any manufacturer is going to have its share of software and hardware issues.

Re: macOS Sonoma Boot Failures

#26
post #11

> Do not let them charge you any money for it. This is a problem Apple caused, and purely a software issue. If the technicians claim there is hardware damage, they are wrong. Good luck with that.

The Apple Store is usually great with this stuff.

If there's a documented problem that affects your hardware model and the given software versions, they're extremely unlikely to try to charge you for anything.

Re: macOS Sonoma Boot Failures

#27

Not sure if related, but my 2020 M1 macbook air bricked a week or so after upgrading to Sonoma. I was suspicious if this was related to the update. Luckily the logic board was replaced for free under warranty laws here, though it put me off switching to iphone which I was a day away from doing.

The logic Board failed in my 2020 M1 Air as well. Opened the lid one day, and it wouldn't power on. I have AppleCare on it, otherwise it would have been a $500 repair.

About two weeks ago I'm sitting in a hotel room with the air on bed with the lid open. I grab it by the screen to slide it closer to me and the screen shatters from the light pressure of my finger.

There are instances of both these things happening to the Air all over the internet. At first I really liked the M1 Air, but it has now proven too unreliable for me.

Re: macOS Sonoma Boot Failures

#29

Interestingly I ran into this exact problem with my work MacBook Pro M1 upgrading to Ventura 13.6 and assumed it was a totally isolated incident. I don't have a dual-boot setup either, just a single macOS install. The computer was connected to a Thunderbolt Display during the update which I assume had the same effect of changing the refresh rate to something other-than-ProMotion that the linked article mentions. I ha…

> I also wasted far too much time trying to get the DFU restore to work before discovering that you cannot use a Thunderbolt cable — it has to be done using a plain USB-C cable, otherwise the Apple Configurator simply won't detect the other Mac. I would have expected a Thunderbolt cable to be required, if either was. This is quite surprising to me. Usually, the more capable (higher bandwidth) cable works if one isn’t…

It's done over USB 2.0 largely because that's simpler than involving newer and faster specs, and partly because that's how the original iPhone did it.

My understanding is that all complaint USB USB-C cables should work for USB 2.0, even USB4/TB4 cables, but active TB3 cables might not hook up the USB 2.0 pins.

Re: macOS Sonoma Boot Failures

#30
post #13

Not sure if related, but my 2020 M1 macbook air bricked a week or so after upgrading to Sonoma. I was suspicious if this was related to the update. Luckily the logic board was replaced for free under warranty laws here, though it put me off switching to iphone which I was a day away from doing.

Upgrades bricking hardware seems to be a common failure mode for macOS. For example Big Sur bricked a bunch of 2013 and 2014 MBPs: https://www.macrumors.com/2020/11/15/macos-big-sur-update-br... I was affected by this and like many users the problem was fixed after replacing the I/O board. In my case, I did it myself using a $10 part from Ebay since the machine was well out of warranty at that point.

From comments #736 and #747 attached to the forum post you kindly shared, it sounds like simply disconnecting and reconnecting the I/O board may be sufficient (found those comments linked in #831):

https://forums.macrumors.com/threads/macos-big-sur-update-br...

https://forums.macrumors.com/threads/macos-big-sur-update-br...

https://forums.macrumors.com/threads/macos-big-sur-update-br...

Post reply on HN