None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
If the hardware of your USB stick is failing, you might still be able to
repair the file system of your Persistent Storage after copying the
partition image to a new USB stick.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
[[Copying the partition image to a new USB stick|fsck#copy]]
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
If the hardware of your USB stick is not failing, repairing the file system
from the Welcome Screen is likely the easiest technique.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
[[Repairing the file system from the Welcome Screen|fsck#welcome]]
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
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 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
After [[creating a partition image|fsck#image]], you can safely try to recover data from your Persistent Storage without risking erasing more data.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
<h1 id="recover">Recovering data from the Persistent Storage</h1>
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
You can now safely start [[recovering data from the Persistent
Storage|fsck#welcome]].
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
Shut down Tails.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
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 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
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 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
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 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
After `ddrescue` finishes:
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
The section about **bad areas** refers to errors reading the data of your
Persistent Storage, most likely because of hardware failures.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
GNU ddrescue 1.27
Press Ctrl-C to interrupt
ipos: 749404 kB, non-trimmed: 0 B, current rate: 34996 kB/s
ipos: 1446 MB, non-trimmed: 0 B, current rate: 24772 kB/s
opos: 1446 MB, non-scraped: 0 B, average rate: 33629 kB/s
non-tried: 9290 MB, bad-sector: 0 B, error rate: 0 B/s
rescued: 1446 MB, bad areas: 0, run time: 43s
pct rescued: 13.46%, read errors: 0, remaining time: 1m 31s
time since last successful read: 0s
Copying non-tried blocks... Pass 1 (forwards)
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
The output of `ddrescue` looks like this:
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
<p class="command-template">ddrescue <span class="command-placeholder">/dev/mapper/luks-xyz</span> persistent-storage.img ddrescue.log</p>
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
In the terminal, execute the following command. Replace <span class="command-placeholder">/dev/mapper/luks-xyz</span> with the device name found when [[identifying your *Persistent Storage* in the *Disks* utility|fsck#identify]].
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
Doing so opens a terminal that is configured to operate in this folder.
 
10 days ago
None

String updated in the repository

  1. Tails
  2. wiki/src/doc/persistent_storage/fsck.*.po
  3. Bulgarian
Right-click in the empty space of the right pane and choose **Open in Terminal** in the shortcut menu.
 
10 days ago

Search