Tails

wiki/src/doc/persistent_storage/check.*.po

English

Translate

Zen

	English	Actions
	[[!meta title="Checking the file system of the Persistent Storage"]]
	In rare occasions, you might have to perform a file system check to repair a broken Persistent Storage.
	Unlock the Persistent Storage
	When starting Tails, [[set up an administration password\|doc/first_steps/welcome_screen/administration_password]].
	Choose Applications ▸ Utilities ▸ Disks to open the Disks utility.
	In the left pane, click on the device corresponding to your Tails USB stick.
	In the right pane, click on the partition labeled as <span class="guilabel">TailsData LUKS</span>.
	Click on [[!img lib/network-wireless-encrypted.png alt="Unlock" class="symbolic" link="no"]]</span> to unlock the Persistent Storage. Enter the passphrase of the Persistent Storage and click Unlock again.
	In the confirmation dialog, enter your administration password and click <span class="guilabel">Authenticate</span>.
	Click on the <span class="guilabel">TailsData Ext4</span> partition that appears below the <span class="guilabel">TailsData LUKS</span> partition.
	Identify the device name of your Persistent Storage. The device name appears below the list of volumes. It should look like `/dev/mapper/luks-xxxxxxxx`.
	Triple-click to select it and press Ctrl+C to copy it to the clipboard.
	Check the file system using the terminal
	1. Choose <span class="menuchoice"> <span class="guimenu">Applications</span> ▸ <span class="guisubmenu">System Tools</span> ▸ <span class="guimenuitem">Root Terminal</span></span> and enter your administration password to open a root terminal.
	In the terminal, execute the following command. Replace <span class="command-placeholder">device</span> with the device name found in step 8:
	<p class="command-template">fsck -y <span class="command-placeholder">device</span></p>
	To do so, you can type <code>fsck -y </code> and press Shift+Ctrl+V to paste the device name from the clipboard.
	If the file system is free of errors, the last line from the output of `fsck` starts with `TailsData: clean`.
	If the file system has errors, `fsck` tries to fix them automatically. After it finishes, you can try executing the same command again to check if all errors are solved.

Loading…

None

Source string added

3 months ago

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
XML markup: German, Spanish, French, Italian, Portuguese, Russian

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

type: Bullet: '1. '

Flags

read-only

String age

3 months ago

Last updated

3 months ago

Source string age

3 months ago

Translation file

string 15