Zen

Source string Source string

64/10000 · 64

The string is read-only.

English Actions
link:++https://fedoraproject.org/wiki/++[Fedora Project Wiki] - the official wiki for Fedora Project
link:++https://unix.stackexchange.com/++[Stack Exchange] - an English language Q&A board, not specific to Fedora
The above list is by no means complete - you can find help in many other places as well. Additional information about available resources such as IRC channels and mailing lists is available at link:++https://fedoraproject.org/wiki/Communicating_and_getting_help++[].
Before you open a new discussion or ask anyone for help on IRC, you should always do some research on your own. If you are encountering an issue, there is usually a good chance that someone else ran into the same problem before you and published a solution somewhere. Opening a discussion about something already explained elsewhere, or asking a common question which has been answered many times before, is not likely to result in a friendly, constructive response.
When you ask for help troubleshooting problems related to the installation, you may be asked to provide log files generated by the installer. The sections below explain which files are generated, what their contents are, and how to transfer them from the installation system.
Log Files Generated During the Installation
For debugging purposes, [application]*Anaconda* logs installation actions into files in the `/tmp` directory. These files are listed in the following table.
Log Files and Their Contents
|Log file|Contents
|`/tmp/anaconda.log`|general [application]*Anaconda* messages
|`/tmp/program.log`|all external programs run during the installation
|`/tmp/storage.log`|extensive storage module information
|`/tmp/packaging.log`|[application]*dnf* and [application]*rpm* package installation messages
|`/tmp/syslog`|hardware-related system messages
If the installation fails, the messages from these files are consolidated into `/tmp/anaconda-tb-_identifier_pass:attributes[{blank}]`, where _identifier_ is a random string.
Transferring Log Files from the Installation System
All of the files described in xref:sect-troubleshooting-log-files[Log Files Generated During the Installation] reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using [command]#scp# on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure.
Transferring Log Files Onto a USB Drive
On the system you are installing, press kbd:[Ctrl + Alt + F2] to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system.
Connect a USB flash drive to the system and execute the [command]#dmesg# command. A log detailing all recent events will be displayed. At the bottom of this log, you will see a set of messages caused by the USB flash drive you just connected. It will look like a set of lines similar to the following:
`[ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk`
Note the name of the connected device - in the above example, it is `sdb`.
Go to the `/mnt` directory and once there, create new directory which will serve as the mount target for the USB drive. The name of the directory does not matter; this example uses the name `usb`.
# mkdir usb
Mount the USB flash drive onto the newly created directory. Note that in most cases, you do not want to mount the whole drive, but a partition on it. Therefore, do not use the name `sdb` - use the name of the partition you want to write the log files to. In this example, the name `sdb1` is used.
# mount /dev/sdb1 /mnt/usb
You can now verify that you mounted the correct device and partition by accessing it and listing its contents - the list should match what you expect to be on the drive.
# cd /mnt/usb
# ls
Copy the log files to the mounted device.
# cp /tmp/*log /mnt/usb
Unmount the USB flash drive. If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, `/`).
# umount /mnt/usb
The log files from the installation are now saved on the USB flash drive.
Transferring Log Files Over the Network
Switch to the `/tmp` directory where the log files are located:

Loading…

No matching activity found.
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:

Unchanged translation
Indonesian, Ukrainian, Portuguese (Brazil), Turkish, Spanish

Reset

Glossary

English English
No related strings found in the glossary.

7944809 String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/install/Troubleshooting.adoc:69
String age
3 years ago
Last updated
a year ago
Source string age
3 years ago
Translation file
pot/f34/pages/install/Troubleshooting.pot, string 22