Start again after a damaged folder list
Use this guide when Tressyl does not start and its window says Tressyl did not start: the list of your synced folders is damaged.
Tressyl keeps the list of the folders this computer syncs in its private folder. If that file is damaged (a disk error, a crash while it was being saved), Tressyl stops instead of guessing, and leaves the file as it is.
Before you start
- If you have a backup of Tressyl’s private folder from before the damage, restoring it brings everything back as it was: do that instead, while Tressyl is closed.
- Otherwise, write down which folders this computer synced and where they are, if you remember: the next steps put some of them in a new place.
Start without the damaged list
- In the Tressyl window, click Start without this list.
- Read what the page says, then click Start without this list again.
The damaged file is moved aside in Tressyl’s private folder, never deleted. Tressyl starts with no folder. Your files are not touched.
What comes back by itself
Folders that your other devices share with this computer come back within a few moments, in your Tressyl folder (usually ~/Tressyl), and their files come from your other devices. Nothing is deleted on your other devices.
A folder that was somewhere else on this computer (for example in ~/Documents) comes back in your Tressyl folder too. Its old copy stays where it was, no longer synced: once the new copy is complete, you can delete the old one yourself.
What to add again
Folders that were only on this computer, shared with no other device, are not listed anywhere else. Add them again: see Add a folder.
If a step fails
| The window says | What to do |
|---|---|
| Tressyl is already running for this user. | Close the other Tressyl window, or stop tressyl-cli run, then try again. |
| Another message with an error code | Look the code up in the error reference. |
On a computer without the window (backup node), stop Tressyl, then run tressyl-cli folder set-aside --yes and start it again.