From Fedora Project Wiki

< User:Tflink
Revision as of 09:00, 8 January 2013 by Tflink (talk | contribs) (→‎Preparing for the Upgrade: added warning as reminder to look into more upgrade prep instructions)

Do not use this documentation before F18 is actually released
Some parts of fedup rely on variables which are not set until Fedora 18 is released. This is a draft document which will be put into place once Fedora 18 is released. If you follow these instructions verbatim before that time, you will not get the results promised here - you will get the beta version which has some known issues. If you really want to use the newest FedUp, follow the upgrade test case.
Security Considerations
FedUp does not yet ensure that only trusted software from Fedora is run on your system when you are doing upgrade over the network. Refer to Bugzilla: #877623 for more details. You can download the ISO release image and verify the authenticity independently before perfoming a upgrade with Fedup via media or ISO images methods to workaround this issue. Note that neither Anaconda not Preupgrade verified the authenticity of the source either and this is not a regression.

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.

Fedora 16 and Older
The FedUp client does not build or run on anything older than Fedora 17. If you want to upgrade an older Fedora installation, please upgrade to Fedora 17 before continuing. This limitation is planned to be fixed in a future release of Fedup

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?

The answer to this 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 for 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 for 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 Fedora Test list.

How Can I Upgrade My System with FedUp?

Upgrading to Pre-Release
These instructions are currently written for upgrading to Fedora 18 beta. If you want to try upgrading to the final pre-release, check out the upgrade test case. However, there may be bugs in the newer process if you use it before the release of Fedora 18 - if you try it, be aware that you may run into problems

As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.

Preparing for the Upgrade

Upgrade prep
It might be good to talk about removing orphan packages etc. before starting the upgrade process
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
  1. Do a full system update and reboot to ensure that any kernel changes are running
  2. Install fedup
    • Be sure to get the latest release, this may involve enabling updates-testing (put --enablerepo=updates-testing between yum and install on 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.).

Network

Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if 41 has a newer kernel version than 41.

  1. Start the upgrade prep by executing following command
    • sudo fedup --network 18 --debuglog fedupdebug.log
  2. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from 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.

  1. Download the 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.
  2. Start the upgrade prep by executing the following command
    • sudo fedup --iso /home/user/fedora-18.iso --debuglog=fedupdebug.log
  3. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup-cli

Other Device

Optical drives and other mountable storage can also be used as a package source for upgrade preparations.

  1. 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.
  2. Start the upgrade preparations by executing the following command
    • command|sudo fedup --device /mnt/fedora --debuglog=fedupdebug.log
  3. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup-cli

Executing the Upgrade

Out of Date
This section is out of date and needs to be rewritten
Monitoring Upgrade Progress
At this time, the FedUp progress during the actual upgrade is not shown automatically, but you can trigger it manually
  1. Reboot the system if fedup has completed without error.
  2. Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade.
  3. Select the System Upgrade option from the GRUB menu
    • If you want to be able to see progress during the upgrade, append plymouth.splash=fedup to the end of the kernel parameters (line starting with linux)
  4. The system should boot into the upgrade process and a plymouth boot screen should be displayed
    • If you press 'esc', a more detailed log of progress will be desplayed but if you switch back to the graphical progress indicator, it will remain at 0% for the remainder of the upgrade. See Need section reference here once it's written
  5. Once the upgrade process has completed, the system will reboot and an option to boot Fedora 42 will be on the grub menu

GRUB Updates

Somewhat Optional
While updating GRUB on your upgraded system isn't strictly required, it is recommended for BIOS systems and very strongly recommended for UEFI systems due to the transition from grub-efi to grub2-efi

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)

Mactel Machines
These instructions have been reported not to work for mactel machines and will need to be updated to cover those machines
Secure Boot
Secure Boot functionality was not completed in time for Fedora 18 beta and these instructions do not cover using shim or the signed kernel. Once Secure Boot functionality is available, these instructions will be updated.
Grub Theme
With the migration to grub2-efi in Fedora 18, you will see no grub splash after initial upgrade nor after upgrading to grub2-efi

Grub2 is not installed as part of the upgrade process, so you'll have to install it: 

sudo yum install grub2-efi

Once the grub2-efi package is installed, we need to add a new EFI boot entry. The easiest way to do this is to just modify the command used when Fedora was first installed. Note that you will not be using the exact same command when upgrading to grub2 as the location of some files has changed. The older reference command can be found in /var/log/anaconda/anaconda.program.log and should end with a command similar to: 

efibootmgr -c -w -L Fedora -d /dev/sdX -p Y -l \EFI\redhat\grub.efi

Find the current boot number for fedora using efibootmgr: 

efibootmgr -v

You are looking for a line similar to: 

Boot0004* Fedora  HD(1,800,34800,6733749f-b42a-4b8c-a0de-5a1d3505f8af)File(\EFI\redhat\grub.efi)

The boot number in this example is 0004.

Remove the old boot entry using the following command (<boot number>) is the boot number you found above: 

efibootmgr -b <boot number> -B
Using Quotes
Make sure you put quotes around '\EFI\fedora\grubx64.efi' or bash will interpret \E, \f and \g as control characters and your system will not boot properly

Once you have the command that was used and the boot number of the old boot entry, you can change it to use the new grub2-efi installation: 

sudo efibootmgr -c -w -L Fedora -d /dev/sdX -p Y -l '\EFI\fedora\grubx64.efi' -b <boot number>

In order to get a bootable UEFI system, you need to regenerate the grub configuration and symlink it to /etc/grub2-efi.cfg 

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Once the system reboots, you should be using grub2-efi instead of grub-efi

Cleaning Up Post Upgrade

Add more detail
There have been reports of problems stemming from following this guide completely. Either be more specific about the recommended steps or spell them out here

Some of the stuff from this post upgrade cleanup guide might be wise

Retrieved from "https://fedoraproject.org/w/index.php?title=User:Tflink/FedUp_Draft&oldid=316967"