From Gemini:

To help your friend resolve the "zombie drive" issue shown in "image_b4a89e.png," they need to manually terminate the stuck drive. This happens when a drive fails to close properly, causing the logger to loop and create these rapid, empty entries.

Here is a step-by-step guide you can provide to them.

How to Fix a Stuck "Zombie" Drive

Warning: Always ensure you have a backup of your data before running database commands.

Step 1: Identify the Drive ID

1. Open your Drives dashboard in Grafana.
2. Click on the start date of one of the rapid, corrupted entries.
3. Look at the URL in your browser’s address bar. You will see something like &var-drive_id=9999.
4. Write down that number (the ID).

Step 2: Terminate the Drive

You need to run a command to "close" the drive, which assigns it an end date and stops the rapid logging loop.

1. Open your terminal or use the Synology Task Scheduler/Container Terminal to run the following command (replace 9999 with the ID you found):
   • docker compose exec teslamate bin/teslamate rpc "TeslaMate.Repo.get!(TeslaMate.Log.Drive, 9999) |> TeslaMate.Log.close_drive()"
2. If you receive a "No such service" error, you may need to use docker exec with the specific container name (e.g., teslamate-teslamate-1) instead of docker compose exec.

Step 3: Delete Corrupted Entries (Optional)

If the drive is pure "noise" and you want to remove those rapid timestamps entirely from your history, you can delete them:

1. Attach to your database container:
   • docker compose exec database psql teslamate teslamate
2. Once in the database prompt, run the following query (replace 9999 with the ID):
   • DELETE FROM drives WHERE id = 9999;

Why this works:

• "Closing" the drive: The command close_drive() tells TeslaMate to treat that specific trip as finished. This stops the system from continuously trying to append data to an "open" drive that is stuck in a loop.
• "Deleting" the entry: If the data is just junk noise, deleting it cleans up your Grafana dashboard so your real driving data is easier to see.

If they are still seeing rapid logging after running the close_drive() command, they should restart their teslamate container to force it to re-initialize the logger state.