(Undo revision 319622 by Le0villems (talk) this is incorrect, reverting to old content) |
(Undo revision 319619 by Le0villems (talk) This is wrong and removed valid documentation, reverting back to previous version) |
||
Line 57: | Line 57: | ||
== Preparing for the Upgrade == | == Preparing for the Upgrade == | ||
{{admon/important| | {{admon/important|Latest fedup|Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-01-08), that is fedup-0.7.2-1.fc17}} | ||
# Do a full system update and reboot to ensure that any kernel changes are running | # Do a full system update and reboot to ensure that any kernel changes are running | ||
# | # Install {{package|fedup}} | ||
#* Be sure to get the latest release, this may involve enabling updates-testing ('''<code>yum --enablerepo=updates-testing install fedup</code>''' in the command line) | |||
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc.). | |||
{{admon/important|Network upgrade is strongly recommended|It is strongly recommended to use the network upgrade instead of offline update modes (ISO, local device). Network upgrade will ensure you receive the latest packages from Fedora 18. If you use local media containing old Fedora 18 packages, you might end up with a mixture of Fedora 17 and Fedora 18 packages and the system might not work properly until you fully update it after reboot (if it boots at all).}} | |||
=== Network === | |||
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading. | |||
# Start the upgrade prep by executing following command | |||
#* {{command|sudo fedup-cli --network 18 --debuglog fedupdebug.log}} | |||
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}} | |||
=== ISO File === | |||
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-18.iso but you will need to replace all instances of that path with the actual path of the ISO. Updates will be pulled in if you have network access on the machine to be upgraded. | |||
# Download the Fedora {{FedoraVersion}} ISO appropriate for the arch that you are running | |||
#* For the sake of example, we will assume that the ISO exists at {{filename|/home/user/fedora-18.iso}} but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO. | |||
# Start the upgrade prep by executing the following command | |||
#* <nowiki>sudo fedup-cli --iso /home/user/fedora-18.iso --debuglog=fedupdebug.log</nowiki> | |||
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}} | |||
=== Other Device === | |||
Optical drives and other mountable storage can also be used as a package source for upgrade preparations. | |||
# Mount the source material | |||
#* For the sake of example, we will assume that this source is mounted at {{filename|/mnt/fedora}} but you can mount it anywhere as long as you replace {{filename|/mnt/fedora}} in the command below with the actual mounted location of the upgrade source. | |||
# Start the upgrade preparations by executing the following command | |||
#* <nowiki>sudo fedup-cli --device /mnt/fedora --debuglog=fedupdebug.log</nowiki> | |||
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}} | |||
== Executing the Upgrade == | == Executing the Upgrade == |
Revision as of 16:53, 19 January 2013
What is FedUp?
FedUp (FEDora UPgrader) is the name of a new system for upgrading Fedora installs in Fedora 18 and above releases. It replaces all of the currently recommended upgrade methods (PreUpgrade and DVD) that have been used in previous Fedora releases. Anaconda, the Fedora installer does have not any in-built upgrade functionality in Fedora 18 or above releases. It has been completely delegated to Fedup.
Currently, FedUp is capable of upgrading Fedora 17 installs to Fedora 18 using a networked repository, similar to how PreUpgrade worked. More methods for upgrade are currently planned and this page will be updated as those features are completed.
What Does FedUp do?
The FedUp system consistes of two parts - the client used to download packages and prepare for the upgrade and a pre-boot environment which does the actual upgrade using systemd and yum. More details are available in a blog post written by FedUp's primary author
The FedUp Client
The FedUp client runs on the system to be upgraded. It gathers the packages needed for upgrade in addition to downloading the required initramfs and kernel needed for the actual upgrade. At this time, only the fedup command-line interface is implemented but a GUI interface is expected before Fedora 18 is released.
The Upgrade
The actual upgrade takes place when the system has been rebooted after running the FedUp client. The filesystems are mounted during boot, the already downloaded packages are installed and some upgrade-related tasks are performed. During the upgrade process, a special plymouth theme is used which has a progress bar to indicate current upgrade progress.
Frequently Asked Questions
Can I upgrade a Fedora 16 system with FedUp?
No, this is not currently possible. The FedUp client does not currently build or run on Fedora 16 and you need to be running at least Fedora 17 in order to run the client. If you are upgrading from Fedora 16, use Preupgrade to upgrade to Fedora 17 first.
How do I report issues that I find with upgrades?
First see Common F18 bugs#Upgrade_issues whether the problem is not one of a very prominent issue we already know of. If it is not there, the component for reporting problems depends on the exact issue that you hit:
Issues with upgrade preparation
If you hit issues when using the FedUp client (fedup
) before reboot, search or file a bug against fedup using the version you are upgrading from.
Issues During Upgrade
If you hit issues after upgrade preparation and the initial reboot, search or file a bug against fedup-dracut
using the version you are upgrading to.
Issues After Upgrade
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.
How do I Debug Issues During Upgrade
A troubleshooting and debug guide will be written soon and linked to from here.
Does FedUp verify the software it runs or installs during upgrade?
This is a planned feature. See Bug 877623 for a status update.
Where can I ask Questions
For now, the best place to ask questions is probably #fedora-qa[?] on Freenode IRC or the test mailing list.
How Can I Upgrade My System with FedUp?
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.
Before you start doing anything, be sure to have a look at Common F18 bugs#Upgrade_issues and read about the most common bugs found.
Preparing for the Upgrade
- Do a full system update and reboot to ensure that any kernel changes are running
- Install
fedup
- Be sure to get the latest release, this may involve enabling updates-testing (
yum --enablerepo=updates-testing install fedup
in the command line)
- Be sure to get the latest release, this may involve enabling updates-testing (
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc.).
Network
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.
- Start the upgrade prep by executing following command
sudo fedup-cli --network 18 --debuglog fedupdebug.log
- Once the preparations have completed, check the
fedupdebug.log
file if any errors show up in the output fromfedup-cli
ISO File
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-18.iso but you will need to replace all instances of that path with the actual path of the ISO. Updates will be pulled in if you have network access on the machine to be upgraded.
- Download the Fedora 41 ISO appropriate for the arch that you are running
- For the sake of example, we will assume that the ISO exists at
/home/user/fedora-18.iso
but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO.
- For the sake of example, we will assume that the ISO exists at
- Start the upgrade prep by executing the following command
- sudo fedup-cli --iso /home/user/fedora-18.iso --debuglog=fedupdebug.log
- Once the preparations have completed, check the
fedupdebug.log
file if any errors show up in the output fromfedup-cli
Other Device
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.
- Mount the source material
- For the sake of example, we will assume that this source is mounted at
/mnt/fedora
but you can mount it anywhere as long as you replace/mnt/fedora
in the command below with the actual mounted location of the upgrade source.
- For the sake of example, we will assume that this source is mounted at
- Start the upgrade preparations by executing the following command
- sudo fedup-cli --device /mnt/fedora --debuglog=fedupdebug.log
- Once the preparations have completed, check the
fedupdebug.log
file if any errors show up in the output fromfedup-cli
Executing the Upgrade
- Open Terminal and run
su -c "fedup-cli --network 18 --debuglog fedupdebug.log""
. - Reboot your system.
- Once you Reboot, you'll see the option 'System Upgrade' on the GRUB prompt. Just press Enter.
- The system will boot into a special environment to perform the upgrade. The screen will show a graphical progress screen during upgrade.
GRUB Updates
Updating GRUB2 (BIOS systems)
- After upgrade, the grub2 you're booting from will still be the F17 version; upgrading must be done manually
- Follow the steps in this grub2 page to reinstall and update grub
Updating GRUB (UEFI systems)
Cleaning Up Post Upgrade
Docs TODO
- Write fedup troubleshooting and debug guide
- add details for secureboot/shim installation
- write commonbugs entries and link to them from this page
- add note about blob drivers if needed
- add notes about how to use other repos or link to discussion/instructions