How to use PreUpgrade
(→Method 1: Free up space)
(→Method 1: Free up space)
|Line 53:||Line 53:|
chmod a+x kernel-prune.py
chmod a+x kernel-prune.py
Revision as of 20:37, 19 November 2009
PreUpgrade is an application users run on an existing Fedora 8 or above installation, that resolves and downloads packages required to upgrade Fedora. While PreUpgrade downloads the necessary packages, users are free to continue using their systems. This gives an experience similar to a live upgrade. For additional information, please refer to the PreUpgrade feature page.
Prepare the system
While preupgrade provides a generally hassle free upgrade experience. The following steps are recommended before proceeding.
- Backup - Before performing any system maintenance, it is recommended that you back up all important data before proceeding.
- Update - Apply available updates Fedora updates before proceeding. As the root user, issue the following command.
- Install - As of Fedora 10, the preupgrade utility is included in a default Fedora install. However, the package can be installed manually using the
yum install preupgrade
Perform the upgrade
- As the root user, run the command
preupgradeto start the Preupgrade application. If you prefer a command line application, the command
- On the Choose desired release screen, select the Fedora release you want to upgrade to , and click the Apply button.
- When all of the packages have downloaded, reboot your system to start the Fedora installer and upgrade to the next release.
Common post-upgrade tasks
After the upgrade is complete, additional steps are recommended to complete the process.
Removing unsupported packagesSome packages may no longer be supported by the new release. You may wish to remove these packages because they will no longer get security updates, and they may cause later conflicts with supported packages. These can be identified with the following command:
After completing the upgrade process, you may notice file names ending with
.rpmnew. Don't be alarmed. The upgrade process will always preserve any locally modified configuration files. The file names ending with
.rpmsave contain your local configuration changes. While the file names ending with
.rpmnew represent the configuration file originally packages with the software.
You should examine all
.rpmnew files created by the upgrade. Depending on the differences, you may need to manually merge configuration files. You can locate all matching files using the
find / -print | egrep "rpmnew$|rpmsave$"
Not enough space in /boot
/boot filesystem size of 200MB hits a bug in preupgrade when upgrading to Fedora 12. In many cases, the diskspace that is likely free is just enough for preupgrade to find enough space to download the installer to but not quite enough for us to run the installer and install the new kernel after reboot. This section outlines several tips that have been known to work. As always when performing administrative tasks, be sure to back-up any data before proceeding.
There are two basic methods to make preupgrade work in this situation. In the first method, you need to free up sufficient space for the installer to install the new kernel packages. In the second method, you need to temporarily fill up enough of the space on
/boot to force preupgrade to download the installer after rebooting.
Method 1: Free up space
First, try to remove any kernel packages not currently in use on your system. The kernel-prune.py script can be used to identify kernels that may be safely removed. If you choose to remove additional kernels, be prepared with installation media should you be unable to return to your previously installed system.
To identify kernels that may be safely removed, run the following from a command line:
curl -O 'http://skvidal.fedorapeople.org/misc/kernel-prune.py' chmod a+x kernel-prune.py ./kernel-prune.py
The installer will need approximately 26M of free space in /boot. Use the following command to determine the amount of free space in the /boot partition:
df -h /boot
Next, adjust the number of reserved filesystem blocks using the command
tune2fs. You'll first need to identify the block device for your
/boot file system. In the example below,
/dev/sda1 is the block device for the
# mount | grep "/boot" /dev/sda3 on /boot type ext4 (rw)
Now, adjust the number of reserved blocks for the
/boot filesystem using the command
tune2fs. Normally, a small amount of space on ext filesystem formatted partitions is 'reserved' and can only be used by the system administrator; this is to prevent an entirely full partition from rendering a system unbootable, and allow the administrator some space in which to work in order to clean up 'full' partitions. However, neither of this cases really applies to the
/boot filesystem, so removing this reserved space is safe.
# tune2fs -r 0 /dev/sda3
Last, try removing unnecessary files from the
/boot filesystem. This will largely depend on how your system is set up. Removing the incorrect files may result in a unbootable system. Some candidates for removal include
Method 2: Trick preupgrade into downloading the installer
This method requires you to have a wired connection to the internet during the install. If you are on wireless and cannot connect via an ethernet cable you will have to use Method 1 instead.
First, find out how much space is available on the
df is the command you want for this:
$ df /boot Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 198337 30543 157554 17% /boot
Second, create a file that takes up enough space that preupgrade decides it cannot install stage2 now. Preupgrade needs approximately 120MB for the installer image so we'll make sure we have a bit less than 100MB. For the example filesystem, that means we need to fill up 60MB. Here's how to do that as root:
# dd if=/dev/zero of=/boot/preupgrade_filler bs=1024 count=61440 # df /boot Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 198337 92224 95873 50% /boot
Third, run preupgrade as normal. In the early stages, before downloading packages, preupgrade should tell you that there wasn't enough room to download part of the installer but it can download it after reboot if you have a wired connection to the network. You can click continue for that. When preupgrade is done don't reboot immediately. Instead, remove the
/boot/preupgrade_filler file and make sure your computer is connected to the network via an ethernet cable. Then you can reboot.
# rm /boot/preupgrade_filler
Fourth, the computer should boot into the installer, connect to the internet via the ethernet cable and start downloading the stage2 installer image. Then it should continue upgrading as normal.