Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 970
    • Issues 970
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #10976
Closed
Open
Issue created Jan 19, 2016 by emmapeel@emmapeelDeveloper2 of 2 checklist items completed2/2 checklist items

persistence.conf lost, recoverable by reconfiguring

Originally created by @emmapeel on #10976 (Redmine)

Once in a while this happens since many Tails, maybe the persistence.conf file gets broken.

But since Tails 1.8.2 many of such reports have been made, most of the times only rebooting normally (no emergency shutdown, nothing)

The Persistence is easily recovered by reconfiguring it again, with same passphrase.

I guess I should add a note on known issues, and that is how I will resolve this ticket. But I wanted the devs to know that (I think) something on 1.8.2 made the persistence.conf a little bit more fragile.

Not sure what will happen with Tails 2.0, maybe this dissapears.

Feedback needed

If this problem happens to you, please send us:

  • the output of df -h;
  • the output of ls -l /live/persistence/*_unlocked/*.conf* (I’m interested in the mtime, not just in the size);
  • the output of ls -l /live/persistence/;
  • the output of getfacl /live/persistence/*_unlocked /live/persistence/*_unlocked/*.conf*;

After that, you can reconfigure your Persistent Volume and it will work normally after reboot:

https://tails.boum.org/support/known_issues/#persistence-disappears

Subtasks

  • #16461 (closed)
  • #16568 (closed)

Related issues

  • Related to #14544 (closed)
  • Related to #15598 (closed)
  • Related to #17112 (closed)
  • Related to #17116 (closed)
Edited Feb 01, 2021 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking