None

Source string added
[[Copying the partition image to a new USB stick|fsck#copy]]
10/08/2024
None

Source string added
If the hardware of your USB stick is not failing, repairing the file system
from the Welcome Screen is likely the easiest technique.
10/08/2024
None

Source string added
[[Repairing the file system from the Welcome Screen|fsck#welcome]]
10/08/2024
None

Source string added
We are presenting here 3 recovery techniques that work in different cases. We recommend that you try the 3 techniques one after the other.
10/08/2024
None

Source string added
After [[creating a partition image|fsck#image]], you can safely try to recover data from your Persistent Storage without risking erasing more data.
10/08/2024
None

Source string added
<h1 id="recover">Recovering data from the Persistent Storage</h1>
10/08/2024
None

Source string added
You can now safely start [[recovering data from the Persistent
Storage|fsck#welcome]].
10/08/2024
None

Source string added
Shut down Tails.
10/08/2024
None

Source string added
If no bad areas were reported or if the same bad areas were reported after several executions of the `ddrescue` command, it means that all the data that could be rescued was copied to the partition image.
10/08/2024
None

Source string added
We recommend that you replace your USB stick and [[copy the partition image
to a new USB stick|fsck#copy]] after you execute `ddrescue` several times.
10/08/2024
None

Source string added
If bad areas were reported, try leaving your USB stick to rest for some minutes and executing the same `ddrescue` command again to copy more data.
10/08/2024
None

Source string added
After `ddrescue` finishes:
10/08/2024
None

Source string added
The section about **bad areas** refers to errors reading the data of your
Persistent Storage, most likely because of hardware failures.
10/08/2024
None

Source string added
The output of `ddrescue` looks like this:
10/08/2024
None

Source string added
The `ddrescue` utility tries to copy first the parts of the Persistent Storage that are not failing and skips over the parts that are failing. After that, you can run `ddrescue` again to try to copy the parts that failed the first time.
10/08/2024
None

Source string added
If creating a partition image using the *Disks* utility fails, you can try this second technique using `ddrescue`, which can be more resilient to hardware failures.
10/08/2024
None

Source string added
<h2 id="ddrescue">Creating a partition image using <span class="code">ddrescue</span> on the command line</h2>
10/08/2024
None

Source string added
If the creation failed, try the second technique described below to [[create a partition image using `ddrescue` on the command line|fsck#ddrescue]] instead.
10/08/2024
None

Source string added
You can now safely start [[recovering data from the Persistent
Storage|fsck#welcome]].
10/08/2024
None

Source string added
If the creation succeeded, shutdown Tails.
10/08/2024

Search