Apple today released MacBook Air Flash Storage Firmware Update 1.0, an update for Mid-2012 MacBook Air models to address an issue with recovering from crashes.
This update is recommended for MacBook Air (mid 2012) models. This update addresses a storage firmware issue that, in rare cases, may cause a system to fail to recover from a crash.
/article-new/2013/05/macbook_air_2012_flash.jpg?lossy)
The update is 1.69 MB and requires OS X 10.7.5 or OS X 10.8.3.
Related Roundup: MacBook Air
Buyer's Guide: MacBook Air (Neutral)
Top Rated Comments
(View all)The MAS showed the update was available. I installed it, it rebooted, did it's thing, but it keeps showing up in MAS as an available update. Downloading the manual update now to see if that one will stick.
Manual update said it requires 10.7 (I'm on 10.8.3) and wouldn't install. So there's obviously something wrong with this update. I tried installing the update from the MAS again, but this time I manually shut down and let it install. Still showing up in the MAS. Oh well.
Same here on 2012 13" MBA with 10.8.3. It goes through the update and reboots instead of shutting down like the instructions explain. Tried both manually and through the app store.I wonder if having Filevault on is causing a problem. I'm decrypting FV2 now to test this theory. Do you have FV2 on by any chance.
Edit: Yep, that was it. I turned off FV2 and waited for it to unencrypt, then applied the update and it worked just fine. You can see the new SSD firmware version TPVABBF0 in sys info.
Mine is Samsung and I didn't get the update (yet?).
Because this is for Apple notebooks. :D:D
After the firwmare updated the computer completely shut off and didnt turn back on.
The installer states that this will happen in the dialog window that opens to confirm you want to install.
If i wasnt apple enthusiast and visited the forums there would have been no way to know that the drive needed to be decrypted first.
Edit* it also gave me a scare. After the firwmare updated the computer completely shut off and didnt turn back on. It was like 5 minutes before I tried to turn it back on because i was to scared to touch anything.
I have not seen any reports of a user able to apply this update with FV2 on, so I think it is necessary to turn it off.
Apple needs to get Core Storage implemented in the firmware. It'll solve so many problems... By that I mean removing the need to have PVs backed by GPT, and to allow decryption without needing a boot partition. They could even implement a GPT emulation layer, complete with a protective MBR for booting Windows.I believe what is happening is the updater writes itself to Macintosh HD for install upon reboot, but with FV2 on Macintosh HD is a virtual core storage (encrypted) volume that cannot be accessed at boot time, so the update fails.
I was on AC adaptor during my earlier failed attempts to install.
EDIT: Okay, now that I read this thread again it only seems to be one single guy here doing this, LOL - the others have the MAS notification of the update... Anyway, in other threads with firmware updates I stumbled upon people like described above.