/var and /home partitions can be empty. Tesla will re-create everything you need on first boot.I've never needed to look at files on the IC, but have heard that some things are different. /var may be close enough, Idk.
Only /var (mmcblk0p3) is likely to ever be damaged as that's what gets hammered by Tesla's (justified) logging. But /var holds some mighty crucial files. This is why you should always try and dump the chip before it fails... and rest assured cowboys, it will fail.
rsync -a will check CRC of source and destination files, and then overwrite the destination files which don't match with the source ones. I'll bet that there is a switch which will preserve existing destination files, although that would preserve also the damaged ones. My best idea is to just pick through the custom files one-by-one, and then search for any straggling VINs, names, birthdays, etc with:
# grep -r "{vinlastfive}" /dev/mmcblk0p3
{hehe} Hey, I'm a "Junior Member" here!Little do they know I'm 64.
I did it myself. Was not able to recover any data from my MCU, so I copied mmc from IC, then wiped /var and /home partitions, extended /home partition and tesla created everything on first boot.laurynas are you talking about just a generic Linux system or about the Tesla system specifically? Have you actually tried this or seen it done?
I did it myself. Was not able to recover any data from my MCU, so I copied mmc from IC, then wiped /var and /home partitions, extended /home partition and tesla created everything on first boot.
Edit:
almost everything.
I see this message in syslog:
2019-02-23T09:48:19.841473-08:00 cid QtCarNetManager[2451]: [SierraCellModem] INFO Cannot open /home/tesla/.Tesla/car/cell_apn
Anybody know the content of this file?
tesla01.com.attz
Thanks. I see no error message in the logs, but mobile internet does not work anyway. Probably cause of it US tesla in Europe. Have to replace sim card.cell_apn file contains this line
2019-02-24T15:03:14.236923-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:14.284608-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:21.884562-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:21.886510-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:44.729614-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:44.755770-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:45.787778-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:45.799184-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:46.012725-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:46.069373-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:49.894553-08:00 cid qtcar-tmserver: QtCarTMServer starting
2019-02-24T15:03:50.770327-08:00 cid qtcar-tmserver: QtCarTMServer has stopped
2019-02-24T15:04:29.979760-08:00 cid QtCarServer[1927]: [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:04:47.206514-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 1 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:05:47.206126-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 3 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:51:48.469502-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:51:48.469667-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Horizon at [] 192.168.90.100:4180 within 50 msecs
2019-02-24T15:51:48.470222-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServerIC at [ic] 192.168.90.101:4304 within 50 msecs
2019-02-24T15:51:48.470606-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to GpsDasDebug at [] 192.168.90.100:4162 within 50 msecs
2019-02-24T15:51:48.470980-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServer at [] 192.168.90.100:4104 within 50 msecs
2019-02-24T15:51:48.472474-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Media at [] 192.168.90.100:4145 within 50 msecs
2019-02-24T15:51:48.472951-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICSystemInfo at [ic] 192.168.90.101:0 within 50 msecs
2019-02-24T15:51:48.475396-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICNavServer at [ic] 192.168.90.101:4300 within 50 msecs
2019-02-24T15:51:48.475831-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICMapState at [ic] 192.168.90.101:4050 within 50 msecs
2019-02-24T15:51:48.476403-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to NavServer at [ic] 192.168.90.101:4200 within 50 msecs
2019-02-24T15:51:48.476903-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to VehicleVolatile at [] 192.168.90.100:0 within 50 msecs
2019-02-24T15:50:30.633320-08:00 cid QtCarAudiod[637]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25
2019-02-24T15:50:30.672629-08:00 cid QtCar[869]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25
Thanks. I see no error message in the logs, but mobile internet does not work anyway. Probably cause of it US tesla in Europe. Have to replace sim card.
I see some other errors in the logs. Apart from it, everything seems to work as expected. Don't know if I should worry about it.
Code:2019-02-24T15:03:14.236923-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high 2019-02-24T15:03:14.284608-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces) 2019-02-24T15:03:21.884562-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high 2019-02-24T15:03:21.886510-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces) 2019-02-24T15:03:44.729614-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high 2019-02-24T15:03:44.755770-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces) 2019-02-24T15:03:45.787778-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high 2019-02-24T15:03:45.799184-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces) 2019-02-24T15:03:46.012725-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high 2019-02-24T15:03:46.069373-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces) 2019-02-24T15:03:49.894553-08:00 cid qtcar-tmserver: QtCarTMServer starting 2019-02-24T15:03:50.770327-08:00 cid qtcar-tmserver: QtCarTMServer has stopped 2019-02-24T15:04:29.979760-08:00 cid QtCarServer[1927]: [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs 2019-02-24T15:04:47.206514-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 1 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs 2019-02-24T15:05:47.206126-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 3 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs 2019-02-24T15:51:48.469502-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs 2019-02-24T15:51:48.469667-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Horizon at [] 192.168.90.100:4180 within 50 msecs 2019-02-24T15:51:48.470222-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServerIC at [ic] 192.168.90.101:4304 within 50 msecs 2019-02-24T15:51:48.470606-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to GpsDasDebug at [] 192.168.90.100:4162 within 50 msecs 2019-02-24T15:51:48.470980-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServer at [] 192.168.90.100:4104 within 50 msecs 2019-02-24T15:51:48.472474-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Media at [] 192.168.90.100:4145 within 50 msecs 2019-02-24T15:51:48.472951-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICSystemInfo at [ic] 192.168.90.101:0 within 50 msecs 2019-02-24T15:51:48.475396-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICNavServer at [ic] 192.168.90.101:4300 within 50 msecs 2019-02-24T15:51:48.475831-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICMapState at [ic] 192.168.90.101:4050 within 50 msecs 2019-02-24T15:51:48.476403-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to NavServer at [ic] 192.168.90.101:4200 within 50 msecs 2019-02-24T15:51:48.476903-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to VehicleVolatile at [] 192.168.90.100:0 within 50 msecs
Code:2019-02-24T15:50:30.633320-08:00 cid QtCarAudiod[637]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25 2019-02-24T15:50:30.672629-08:00 cid QtCar[869]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25
Oh great work you actually did it?! How though? I don't understand. I thought keys, shadow, vpn, VIN, mileage and every other car specific crucial info was on p3 & p4. So if you take dump of IC and just keep p1&2 and delete the contents of p3&p4 on a blank new MCU eMMC where does it get the data from?I did it myself. Was not able to recover any data from my MCU, so I copied mmc from IC, then wiped /var and /home partitions, extended /home partition and tesla created everything on first boot.
Edit:
almost everything.
I see this message in syslog:
2019-02-23T09:48:19.841473-08:00 cid QtCarNetManager[2451]: [SierraCellModem] INFO Cannot open /home/tesla/.Tesla/car/cell_apn
Anybody know the content of this file?