Yeah, bought mine in June. Picked it up late June and was a custom config. Doesn't make sense it's an Early 2015 though.
Apple Releases Flash Storage Firmware Update for 2015 MacBook Pros
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yeah, bought mine in June. Picked it up late June and was a custom config. Doesn't make sense it's an Early 2015 though.
jezbd1997
macrumors 6502a
That's weird that their site says
I think I'm on the same page, I bought my 13" force touch in June and the update hasn't come up for me in software update.. Probably just the more recent models
jbachandouris
macrumors 603
I have an early 2015 13" rMBP. Apparently not affected.
BTW, this story is showing on my iPhone, but not on my rMBP. Weird.
BTW, this story is showing on my iPhone, but not on my rMBP. Weird.
z31fanatic
macrumors 6502a
Is it your first Macbook ever?
Even though yours was built in June, it's still an early 2015 model because that's when your model was released.
My 15" rMBP was built in March 7, 2015 but it's still a mid 2014 model.
Do you understand it better now?
Thanks, I've updated the article to clarify the firmware is for the 15-inch "mid-2015" models and not the 13-inch 2015 "early-2015" models.
jezbd1997
macrumors 6502a
Restart and make sure you're connected to the Internet, it checks the serial with the Internet connection to display the year
jezbd1997
macrumors 6502a
Lol it is slow with Yosemite
MacTech68
macrumors 68020
It's also limited to certain date codes of flash storage, with certain revisions of firmware and the flash storage must have a valid serial number.
jezbd1997
macrumors 6502a
Why would we need to check? If our laptop requires the update, it'll appear in software update...
noxtos
macrumors member
My board id is Mac-06F11FD93F0323C5, but the installer says I don't need the update. I only bought my MBP yesterday, maybe it already had the new firmware installed.
virginblue4
macrumors 68020
The "Early 2015" part refers to when your model was released, it has nothing to do with when you actually purchased it.
dannys1
macrumors 68040
Ah yeah, interesting, mine shipped with this already then - so it looks like it only applies to models shipped prior to last week or so from release date...a fairly smallish window.
I purchased my Mid 2015 MacBookPro about a month ago. And I think I did face the problem.
I started having very strange and occasional/random delays when I moved some files around. For instance, when I moved a document from Folder A to Folder B the moved file facing the problem would appear in Folder B after a 1-2 sec. delay, AFTER the file had been removed from Folder A and regardless of the size of the file. Sometimes the files would just vanish in the process.
For example, I had to move a few PDFs from one folder to another. The files were wiped out from the source folder but only some of them ended up in the destination folder, albeit intact. A bunch of them simply vanished. I actually resolved this problem by pulling them back from my TM backup. But that incident did bother me and made me believe that something was wrong with my drive. I even ran a simple HD check on my drive to make sure it was ok but that did not reveal anything.
This file destruction happened to me only a few times. And most of the time the problem arose when I was moving the files to/from a 256bit encrypted disk image, rather than during the normal manipulation of the files. I have not faced any system failures yet and I am not sure if any other file got messed up or not. The delay problem was more frequent but it did not always corrupt/destroyed the data.
These problems disappeared after the update. I now wonder, however, if I need to go through a clean install or not...
Last edited:
How can I tell if my data is ok? I still have the TM backup from my previous laptop and it is not too late to go through a clean install and recovery (i.e. pull back most of my data from the TM backup made with my old laptop and manually combine that with the recent files). Is it worth the trouble?
tombiscuit
macrumors member
I encountered one of these "rare" data errors and blogged about it at http://mackungfu.org.
Luckily I had a Time Machine backup and was able to restore.
You might know if you're affected because a permissions check in Disk Utility* will show input/output errors. The first whiff I got that something was wrong was when Activity Monitor wouldn't start because it was "corrupted". Scary stuff, and the first time I've seen something like this in over a decade of using Macs.
* Note that Apple appears to have removed permissions checking from El Capitan. Great!
Luckily I had a Time Machine backup and was able to restore.
You might know if you're affected because a permissions check in Disk Utility* will show input/output errors. The first whiff I got that something was wrong was when Activity Monitor wouldn't start because it was "corrupted". Scary stuff, and the first time I've seen something like this in over a decade of using Macs.
* Note that Apple appears to have removed permissions checking from El Capitan. Great!
Not my first but yes, I get it now. For some reason I was confusing build date with release date. Apple goes by the release of that build. Any subsequent changes results in a new release date.
I have revision number BXW1PA0Q and still I don't have this update.
This is veeeery weird.
tombiscuit
macrumors member
Just download it from the link and see if it'll run. If it's not for your Mac then it won't.
It doesn't work when I download it, but it obviously is for my rMBP. That's why I have no clue what is going on
