Conversation

Notices

1. Embed this notice
   niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 08:56:04 JST niconiconi

   Broken AWS macOS servers alert :woozy_aws: Many Intel Mac bare-metal servers (mac1.metal) are broken due to old incompatible firmware (AWS has a custom management system but firmware upgrade is broken right now). Apple Silicon Macs (mac2.metal) seem to work well. On Intel, use these supported versions only.
   
   This firmware problem has existed a month or more, but is still completely undocumented to my best knowledge. It's a Gacha game right now: "pay $20 to allocate a server that can run macOS 13, for at least 24 hours (macOS EULA, thanks Apple!). If it doesn't work, pay $20 again and try another one..." I'm now trying to get refunded.

   • Embed this notice
     niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 08:56:00 JST niconiconi

     in reply to

     AWS's macOS obsolete firmware problem just claimed yet another victim. :woozy_aws:

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 08:56:01 JST niconiconi

     in reply to

     Yet another victim of AWS's "macOS machine won't boot due to outdated firmware" problem has appeared... :woozy_aws: The problem has allegedly already existed for years, and it's also already 1.2 years since I documented it. But today it's still broken, and AWS apparently still hasn't acknowledged it in the knowledge base...

   • Embed this notice
     niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 08:56:02 JST niconiconi

     in reply to

     Yet another victim of AWS's "macOS machine won't boot due to outdated firmware" problem has reported it! :woozy_aws: They said they've lost "thousands of dollars and 2 weeks worth of man time" before figuring it out after seeing my posts. :woozypad: Unlike me who was having problems with Intel systems (mac1.metal), they were using Apple Silicon (mac2.metal) which I used before without problems - so they're not immune.
     
     But we finally have a workaround: just run the upgrade yourself... First, get the machine booting by selecting an older macOS image, run macOS upgrades manually all the way to the latest version. Destroy the instance, wait until it finishes scrubbing. Relaunch an instance on the same host - now you can select a new macOS image and boot it up. https://www.reddit.com/r/MacOS/comments/131y9nz/comment/ke3nv7z/ #AWS

   • Embed this notice
     niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 09:10:42 JST niconiconi

     in reply to

     • 🩷💜 PYNK 💜🩷

     @pynk AWS is using Apple's locked-down machines as is so there are real engineering problems. Just shows how nasty Apple is, even if you have trillion dollars in your bank account you still don't get any special offer like a server version or an escape from the Apple jail. The real problem is that AWS made zero acknowledgment in the knowledge base for years... :woozy_nikoni:

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     🩷💜 PYNK 💜🩷 (pynk@mk.absturztau.be)'s status on Tuesday, 15-Oct-2024 09:10:44 JST 🩷💜 PYNK 💜🩷

     in reply to

     @niconiconi
     please understand, it’s run by a mom-and-pop turboconglomerate with only a few trillion dollars to its name