#Tesla usb drive format full#
#Tesla usb drive format Pc#
#Tesla usb drive format windows#

I do not know why the Tesla couldn't format this drive or why it refused to like the Windows-formatted exFAT volume, but I honestly don't care anymore.

#Tesla usb drive format full#

Waaaaaa!ДЇinally, I took the drive to a linux box, repartitioned the drive to use the full size, formatted it in ex4 format, added TeslaCam folder and lo and behold, my Tesla gobbled it up just fine and the sentry mode and dashcam functions were back up and running. EXCEPT that Tesla checks the volume size and if its not bigger than 32GB it will refuse to use it for the TeslaCam. So just to see if it was the drive itself or the filesystem, I made a 32GB partition, formatted it, added the folder and it worked fine.

#Tesla usb drive format windows#

This was an issue because Windows does not like to format anything over 32GB in FAT32 to the point where it won't let you. The Tesla was having none if it, and when plugged into the car, it would corrupt the volume immediately and start throwing errors.

#Tesla usb drive format Pc#

So I formatted it on my PC in exFAT format and put the requisite 'TeslaCam' folder on it manually. This particular SSD apparently does not like being formatted by the Tesla. So I replaced my 64GB flash drive with an inexpensive JOIOT SSD drive. (the larger the flash drive, the less frequent the same part of the memory gets overwritten). This is why SSD's or even very large flash drives are preferable. Flash drives are simply not designed for that much constant writing to them. Also, I think there may be a wave of people beginning to experience this as more people's flash drives get bricked from the excessive writing from the dashcam. I am sharing this because it was a frustrating issue that I could not find a solution for via Googling the error. I concluded that what must have happened is that when the USB drive bricked, the MCU must have been holding on to data that needed to be committed or purged, but couldn't do so without a new valid thumb drive being made available to the car, despite the reboots. I rebooted the car one more time and the error never came back. Then while we were on the phone I decided to take a new USB drive, format it, and then plug it into the car. I let them know that my thumb drive was indeed fried (it couldn't even be recognized by my PC) but it has been disconnected for several days, I did sever reboots but the error persisted. I made an appointment w/ Tesla mobile service and they reached out and the technician wasn't sure what to do but was willing to swap out the USB hub for me. I then rebooted the car and the error disappeared for maybe 10 minutes and then returned. I removed the thumb drive from the USB port but the error didn't go away. I recently got an error message on my Model 3 about a 'USB Device Malfunction' and my sentry mode and dashcam stopped working.