Sentry & Saved has just 2 files

[cleanev]

Describe the problem

Till February 23, all Sentry & Saved filed were synced using rclone. 2/23 at the end of the day updated to latest version 2024.2.7 and now every single day there are just 2 files named event.json and thumb.png files are the only 2 that gets uploaded. What else should I look into. Will check another car where 2024.2.7 version got updated few days later.

Today (March3 ) updated teslausb using self update and still cannot get older saved and sentry files are uploaded.
Tried to check to best of my understanding and found sentry_found_files file in tmp folder that has below logged

SentryClips/2024-02-23_12-12-30/2024-02-23_12-01-03-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-01-03-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-01-03-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-02-04-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-02-04-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-02-04-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-02-04-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-03-04-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-03-04-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-03-04-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-03-04-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-04-05-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-04-05-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-04-05-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-04-05-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-05-05-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-05-05-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-05-05-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-05-05-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-06-06-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-06-06-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-06-06-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-06-06-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-07-06-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-07-06-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-07-06-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-07-06-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-08-07-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-08-07-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-08-07-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-08-07-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-09-07-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-09-07-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-09-07-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-09-07-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-11-08-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-11-08-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-11-08-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-11-08-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-12-09-back.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-12-09-front.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-12-09-left_repeater.mp4
SentryClips/2024-02-23_12-12-30/2024-02-23_12-12-09-right_repeater.mp4
SentryClips/2024-02-23_12-12-30/event.json
SentryClips/2024-02-23_12-12-30/thumb.png
SentryClips/2024-02-24_10-50-05/event.json
SentryClips/2024-02-24_10-50-05/thumb.png
SentryClips/2024-02-24_11-11-09/event.json
SentryClips/2024-02-24_11-11-09/thumb.png
SentryClips/2024-02-26_11-52-07/event.json
SentryClips/2024-02-26_11-52-07/thumb.png
SentryClips/2024-02-26_18-36-41/event.json
SentryClips/2024-02-26_18-36-41/thumb.png
SentryClips/2024-02-26_19-13-32/event.json
SentryClips/2024-02-26_19-13-32/thumb.png
SentryClips/2024-02-28_13-24-50/event.json
SentryClips/2024-02-28_13-24-50/thumb.png
SentryClips/2024-02-28_15-11-59/event.json
SentryClips/2024-02-28_15-11-59/thumb.png
SentryClips/2024-02-28_18-00-21/event.json
SentryClips/2024-02-28_18-00-21/thumb.png
SentryClips/2024-02-28_19-18-50/event.json
SentryClips/2024-02-28_19-18-50/thumb.png
SentryClips/2024-03-02_19-35-31/event.json
SentryClips/2024-03-02_19-35-31/thumb.png
SentryClips/2024-03-02_20-09-48/event.json
SentryClips/2024-03-02_20-09-48/thumb.png

Below is what shows up in archiveloop.log right after rebooting

==============================================
Sun  3 Mar 21:20:02 EST 2024: Starting archiveloop at 43.21 seconds uptime...
Sun  3 Mar 21:20:03 EST 2024: Running fsck on /backingfiles/cam_disk.bin...
Sun  3 Mar 21:20:04 EST 2024: | fsck from util-linux 2.33.1
Sun  3 Mar 21:20:08 EST 2024: | fsck.fat 4.1 (2017-01-24)
Sun  3 Mar 21:20:08 EST 2024: | Long filename fragment "2023-10-20_20" found outside a LFN sequence.
Sun  3 Mar 21:20:08 EST 2024: |   (Maybe the start bit is missing on the last fragment)
Sun  3 Mar 21:20:08 EST 2024: |   Not auto-correcting this.
Sun  3 Mar 21:20:08 EST 2024: | Long filename fragment "2023-05-31_16" found outside a LFN sequence.
Sun  3 Mar 21:20:08 EST 2024: |   (Maybe the start bit is missing on the last fragment)
Sun  3 Mar 21:20:08 EST 2024: |   Not auto-correcting this.
Sun  3 Mar 21:20:08 EST 2024: | Long filename fragment "2023-04-16_14" found outside a LFN sequence.
Sun  3 Mar 21:20:08 EST 2024: |   (Maybe the start bit is missing on the last fragment)
Sun  3 Mar 21:20:08 EST 2024: |   Not auto-correcting this.
Sun  3 Mar 21:20:08 EST 2024: | Long filename fragment "2023-04-09_18" found outside a LFN sequence.
Sun  3 Mar 21:20:08 EST 2024: |   (Maybe the start bit is missing on the last fragment)
Sun  3 Mar 21:20:08 EST 2024: |   Not auto-correcting this.
Sun  3 Mar 21:20:08 EST 2024: | Wrong checksum for long file name "2024-02-23_15-12-44-back.mp4".
Sun  3 Mar 21:20:08 EST 2024: |   (Short name 209B50~1.MP4 may have changed without updating the long name)
Sun  3 Mar 21:20:08 EST 2024: |   Not auto-correcting this.
Sun  3 Mar 21:20:08 EST 2024: | /dev/loop0p1: 423 files, 742871/1965055 clusters
Sun  3 Mar 21:20:08 EST 2024: Finished fsck on /backingfiles/cam_disk.bin.
Sun  3 Mar 21:20:08 EST 2024: taking snapshot of cam disk in /backingfiles/snapshots/snap-003216
Sun  3 Mar 21:20:09 EST 2024: waiting for autofs to be active
Sun  3 Mar 21:20:10 EST 2024: waiting for autofs to be active
Sun  3 Mar 21:20:12 EST 2024: waiting for autofs to be active
Sun  3 Mar 21:20:13 EST 2024: waiting for autofs to be active
Sun  3 Mar 21:20:14 EST 2024: waiting for autofs to be active
Sun  3 Mar 21:20:16 EST 2024: took snapshot
Sun  3 Mar 21:20:19 EST 2024: comparing new snapshot with /backingfiles/snapshots/snap-003215/snap.bin
Sun  3 Mar 21:20:19 EST 2024: new snapshot is identical to previous one, discarding
Sun  3 Mar 21:20:31 EST 2024: Trying to set time...
Sun  3 Mar 21:21:21 EST 2024: Time adjusted by 50.088968 seconds after 0.190000 seconds
Sun  3 Mar 21:21:21 EST 2024: Not keeping car awake.
Sun  3 Mar 21:21:21 EST 2024: Archiving...
Sun  3 Mar 21:21:22 EST 2024: Checking saved folder count...
Sun  3 Mar 21:21:22 EST 2024: There are 0 event folder(s) with 0 file(s) and 0 track mode file(s) to move.  0 short recording(s) will be skipped.
Sun  3 Mar 21:21:23 EST 2024: Ensuring cam file is mounted...
Sun  3 Mar 21:21:23 EST 2024: Disconnecting usb from host...
Sun  3 Mar 21:21:23 EST 2024: Disconnected usb from host.
Sun  3 Mar 21:21:23 EST 2024: Mounting /mnt/cam...
Sun  3 Mar 21:21:23 EST 2024: Mounted /mnt/cam.
Sun  3 Mar 21:21:23 EST 2024: Ensured cam file is mounted.
Sun  3 Mar 21:21:23 EST 2024: cleaning cam mount
Sun  3 Mar 21:21:24 EST 2024: done cleaning cam mount
Sun  3 Mar 21:21:25 EST 2024: Trimming free space in /mnt/cam, which has 1682 extents
Sun  3 Mar 21:21:25 EST 2024: Trim complete, image now has 1682 extents
Sun  3 Mar 21:21:25 EST 2024: Unmounting /mnt/cam...
Sun  3 Mar 21:21:25 EST 2024: Unmounted /mnt/cam.
Sun  3 Mar 21:21:25 EST 2024: Finished archiving.
Sun  3 Mar 21:21:25 EST 2024: Music archive not configured or unreachable
Sun  3 Mar 21:21:25 EST 2024: Connecting usb to host...
Sun  3 Mar 21:21:26 EST 2024: Connected usb to host.
Sun  3 Mar 21:21:31 EST 2024: Waiting for archive to be unreachable...


### Device

Raspberry Pi Zero W

### OS Image

Prebuilt TeslaUSB image

### Car Model

Model Y

### USB connection

Center console

### Logs

_No response_

### Additional information

_No response_

[marcone]

I have seen this issue too, as have others. Since it only started happening recently I suspect it's due to a Tesla software update, but it's unclear what exactly the trigger is. If I clear out the "cam" drive, it starts working properly again.

[cleanev]

Thanks for confirming @marcone. I checked 2018 Model 3 and that does exactly the same.
When you say clearing out “cam” drive is it the Teslacam folder on SD card? I will definitely give that a try once you confirm to see if it works again like you observed.

[marcone]

Connecting the Pi to a PC and deleting the content of the TeslaCam folder in the "CAM" drive is what I did. Don't delete the TeslaCam folder itself.
Or if you want to do it without taking the Pi out of the car:

sudo -i
bin/disable_gadget.sh
mount /mnt/cam
rm -rf /mnt/cam/TeslaCam/*
umount /mnt/cam
bin/enable_gadget.sh

This probably isn't a permanent fix, but it made it work again for me for now.

[brswattt]

Connecting the Pi to a PC and deleting the content of the TeslaCam folder in the "CAM" drive is what I did. Don't delete the TeslaCam folder itself. Or if you want to do it without taking the Pi out of the car:

sudo -i
bin/disable_gadget.sh
mount /mnt/cam
rm -rf /mnt/cam/TeslaCam/*
umount /mnt/cam
bin/enable_gadget.sh

This probably isn't a permanent fix, but it made it work again for me for now.

I believe this fixed it for me, will verify when I get home from work.

[Gizmotoy]

Having the same issue here. I gave the above series of "in-vehicle" commands a shot. There is one modification needed. I got an error that I couldn't rm on a read-only file. The correct sequence, I think, is:

sudo -i
bin/disable_gadget.sh
mount -o rw /mnt/cam
rm -rf /mnt/cam/TeslaCam/*
umount /mnt/cam
bin/enable_gadget.sh

I'll monitor and report back if this fixes it.

[marcone]

you shouldn't need to add that -o rw to the mount command. It should be mounted read-write by default. If it's not, there's probably some kind of filesystem corruption.

[cleanev]

Connecting the Pi to a PC and deleting the content of the TeslaCam folder in the "CAM" drive is what I did. Don't delete the TeslaCam folder itself. Or if you want to do it without taking the Pi out of the car:

sudo -i
bin/disable_gadget.sh
mount /mnt/cam
rm -rf /mnt/cam/TeslaCam/*
umount /mnt/cam
bin/enable_gadget.sh

This probably isn't a permanent fix, but it made it work again for me for now.

Thanks @marcone - it works for now on 2 separate instances.

[coolham123]

I'm having a similar issue. TeslaUSB was only backing up 2 files. I ran the commands @marcone suggested. I am using TeslaFi to keep the car awake, and the archive log never gets past "Starting background task to keep car awake.". I verified through the TeslaFi API page, the call is going through and is received by the vehicle. I re-rolled the API token for good measure and updated the config, restarted, aswell as ran the update script to make sure I was on the latest TeslaUSB version. The Diagnostics page (attached) does not immediately jump out at me.

teslausb_diagnostics.txt

[Gizmotoy]

This worked for me for a few days and now it’s exhibiting the behavior again. Notably on one new vehicle (2024) which got a new and freshly-provisioned Pi Zero W teslausb installation. Now I’m also seeing the same on an existing installation on a 2020 vehicle where teslausb had been working flawlessly for years.

Seems related to a recent vehicle SW update, I guess? Both are running v11.1 ⁦(2024.2.7 d522c44937f7)⁩.

If it's not, there's probably some kind of filesystem corruption.

What’s the recommended way to check for/repair this for these mounts?

[cleanev]

Broke after few days again on 2 cars. Just 2 files.
@Gizmotoy - this seems to be Tesla firmware update, both vehicles are on 2024.2.7 - 2018 RWD 3 and 2020 Y.
Maybe wait till next Tesla update.

[Gizmotoy]

Mine are also again broken.

this seems to be Tesla firmware update

That's the big concern, I think. It doesn't seem super likely to me that Tesla will make fixes for this use case (or even notice they've broken it).

@marcone , is there anything we could do to help provide some insight into what is actually going on here? Run a diagnostic build? Capture logs? Happy to help investigate.

[brswattt]

Same here, broke after a while. Going back to manual USB until this is resolved, if it can be. I'll format it and see if theres any obvious directory changes. I'll be happy to help as well. What exactly has changed? How the video files are saved? Naming?

[marcone]

@marcone , is there anything we could do to help provide some insight into what is actually going on here? Run a diagnostic build? Capture logs? Happy to help investigate.

I don't think there is anything that can be done on the TeslaUSB side. I think this is just a bug on Tesla's side, since it started recently with no notable TeslaUSB changes, and I'm seeing problems even with a regular USB drive.

[brswattt]

@marcone , is there anything we could do to help provide some insight into what is actually going on here? Run a diagnostic build? Capture logs? Happy to help investigate.

I don't think there is anything that can be done on the TeslaUSB side. I think this is just a bug on Tesla's side, since it started recently with no notable TeslaUSB changes, and I'm seeing problems even with a regular USB drive.

So you think this problem is widespread to all Tesla dashcam users regardless if they are using teslausb or not? What problems do you see with the regular usb drive?

[Gizmotoy]

I was wondering the same. I flipped my 2024 back to a USB drive and it seems to be working fine so far, while the 2020 continues to fail after clearing the TeslaCam folder every few days. I can't say I see any complaints of this on the various Tesla forums despite scouring pretty hard, but it doesn't mean it's not happening.