I'd be surprised if tesla didn't have embedded systems engineering responsible for this thing, and indeed even flash memory experts on staff, who are intimately familiar with all of the design problems of flash memory write wear leveling. And they went ahead and send that design to production anyways?
There's an NHTSA investigation into the incident, but on the bright side, Tesla did remediate it in newer models...by using chips with twice as much eMMC memory to push the failures farther out.
That was a really stupid design decision of course for Tesla to use the emmc in that way. I love my car but that was a bad day when the problem hit me.
It's been a great car even with a few problems (had one of the door handles replaced). Mine will be 6 years old soon, I will probably wait till it's about 8 years old for replacing it.
On the other hand, I have a friend with an 8 year old model S and he had no extended warranty and he hasn't had that problem.
Some people who have intentionally done torture test writes on consumer grade SSDs have discovered the actual cumulative TB writes that a $50 to $100 SSD will take before ultimate failure. From back in 2015: https://techreport.com/review/27909/the-ssd-endurance-experi...
One drive failed at 700TB written. If you were to write 2GB per day in an industrial/embedded application nonstop for 20 years, that is considerably less data than 700TB.
With teslas that have a persistent LTE data connection for the car, you also have the option of doing something like 300KB of file upload per day to a remote server.
Specifically:
$ units
You have: 2GiB/day * 20yr
You want: TiB
* 14.267273
You have: 2GiB/day * 20yr
You want: 700TiB
/ 49.063334
14TB total, or about one fiftieth of your quota.Ironically, my system for downloading the logs writes them to an SD card on a raspberry pi.