10.11.6 Destroyed My Fusion Drive

ZipZap

macrumors 603
Original poster
Dec 14, 2007
5,426
856
Just a heads up I tried to install 10.11.6 on Saturday. My iMac 2015 died during install. Hours and hours on the phone with Apple. Took it to store today, SSD and HDD were unfused. Good thing I had a backup.

Stay away from that update.
 

chrfr

macrumors G3
Jul 11, 2009
8,183
2,514
10.11.6 has been out for 3 months and this isn't a widespread problem. It's much more likely that this was a coincidental glitch specific to your computer.
 

ZipZap

macrumors 603
Original poster
Dec 14, 2007
5,426
856
My iMac ran fine. No issues. This update goes in an bang its dead. Plenty of other people online have reported this or similar issues.

Its just a warning for those who may not have updated to skip it.
 

simonsi

macrumors 601
Jan 3, 2014
4,849
716
Auckland
Doesn't remotely seem a common problem. So everyone is supposed to avoid the update because someone somewhere has a problem??? There are millions of Macs now, some activities will encounter problems, some problems will occur coincidentally to all kinds of activities every day...hardly a reason to claim the sky is falling.
 
  • Like
Reactions: arefbe

flyinmac

macrumors 68040
Sep 2, 2006
3,582
2,408
United States
I've read lots of posts reporting the SSD and HDD of fusion drives becoming separated / unlinked. This is a symptom of design, not limited to particular updates.

Various situations can arise and cause this to happen. It is likely that something else coincidentally took place around the time of your update. Not likely caused by the 10.11.6 update itself.
 

ZipZap

macrumors 603
Original poster
Dec 14, 2007
5,426
856
I've read lots of posts reporting the SSD and HDD of fusion drives becoming separated / unlinked. This is a symptom of design, not limited to particular updates.

Various situations can arise and cause this to happen. It is likely that something else coincidentally took place around the time of your update. Not likely caused by the 10.11.6 update itself.
Not around the time. But exactly at the time. The update failed and took my system with it.
[doublepost=1476831443][/doublepost]
Doesn't remotely seem a common problem. So everyone is supposed to avoid the update because someone somewhere has a problem??? There are millions of Macs now, some activities will encounter problems, some problems will occur coincidentally to all kinds of activities every day...hardly a reason to claim the sky is falling.
Did not say it was. I generally skip all updates until months have gone by because they are unpredictable. This is the first one to fail. Significant from my perspective.