FedUp/it

In other languages: English (en) español (es) italiano (it) 中文（中国大陆） (zh-cn) Ελληνικά (el) [edit]

Nota
Questa pagina non è ancora completamente tradotta.
This page is not completely translated yet.

Considerazioni per la sicurezza
FedUp non assicura ancora che venga avviato solo software sicuro da Fedora sul proprio sistema quando si effettua un upgrade da rete. Far riferimento al Bug: #877623 per maggiori dettagli. E' possibile scaricare le immagini ISO e verificarne l'autenticità indipendentemente prima dell'upgrade con Fedup tramite media o tramite immagini per risolvere questi problemi; comunque l'upgrade da rete è ancora l'opzione raccomandata visto che permette una migliore gestione dei pacchetti. Si noti che ne Anaconda ne il PreUpgrade verificano l'autenticità della fonte.

Cos'é FedUp ?

FedUp (FEDora UPgrader) è il nome del nuovo sistema d'aggiornamento (upgrade) delle installazioni Fedora a partire da Fedora 18 Spherical Cow. Rimpiazza tutti gli attuali metodi raccomandati di upgrade (PreUpgrade e DVD) che sono stati usati nei rilasci precedenti a Fedora 18. Anaconda, l'installer di Fedora non ha alcuna funzionalità d'aggiornamento integrata fino a Fedora 18, tale funzionalità è stata delegata completamente a Fedup.

Ad oggi, FedUp è in grado di aggiornare installazioni di Fedora 17 Beefy Miracle a Fedora 18 Spherical Cow usando un repository di rete con un funzionamento simile a PreUpgrade. Molti metodi d'aggiornamento sono attualmente in pianificazione e, a tal proposito, questa pagina verrà aggiornata seguendone gli sviluppi.

Fedora 16 e precedenti
Il client FedUp non costruisce od avvia nulla di più vecchio di Fedora 17. Se si vuole aggiornare partendo da un rilascio più vecchio di Fedora 17, si prega di seguire le istruzioni per l'upgrade a Fedora 17 prima di continuare.

Cosa fa FedUp ?

FedUp consiste in due parti: il client usato per scaricare i pacchetti e per la preparazione all'upgrade ed un ambiente di pre-avvio che effettua l'attuale aggiornamento usando systemd e yum. Maggiori dettagli sono disponibili in un articolo sul blog del principale autore di FedUp

Il Client FedUp

Il Client di FedUp parte nel sistema che deve essere aggiornato. Raccoglie i pacchetti necessari per l'aggiornamento oltre a scaricare gli initramfs del kernel richiesti e necessari per l'aggiornamento vero e proprio. In questo momento è implementata la sola interfaccia a riga di comando di fedup ma ci si aspetta un'interfaccia GUI prima del rilascio di Fedora 18.

L'Upgrade

L'aggiornamento attuale ha luogo quando il sistema viene riavviato dopo l'esecuzione del client fedup. I filesystem sono montati durante l'avvio, i pacchetti già scaricati vengono installati ed alcune attività relative all'aggiornamento vengono eseguite. Durante il processo di aggiornamento, un tema speciale plymouth è utilizzato per visualizzare una barra di avanzamento per indicare i progressi in corso.

Domande frequenti

Posso aggiornare un sistema Fedora 16 con FedUp ?

No, non è attualmente possibile. Il client FedUp non parte su Fedora 16 ma bisogna avviarlo necessariamente almeno in Fedora 17. Se si sta aggiornando da Fedora 16, usare Preupgrade.

Come posso riportare eventuali problemi trovati durante gli aggiornamenti ?

Innanzitutto leggere Common F18 bugs#Upgrade_issues per sapere se il problema è tra quelli conosciuti. Se non lo è, il componente principale del problema dipende dall'esatta questione che s'incontra:

Questioni nella preparazione all'aggiornamento

Per problemi del genere con il client FedUp (fedup) prima del riavvio, ricercare o riportare un bug in rapporto a fedup usando la versione di partenza dalla quale si aggiorna.

Questioni durante l'upgrade

Per i problemi incontrati dopo la preparazione ed al riavvio iniziale, ricercare o riportare un bug in rapporto a fedup-dracut usando la versione alla quale si sta aggiornando.

Questioni dopo l'upgrade

Per problemi con un pacchetto specifico, riportare un bug in rapporto al pacchetto stesso.

Come posso risolvere un problema durante l'upgrade ?

Una guida per la risoluzione ed il debug verrà presto redatta e collegata alla presente pagina wiki.

FedUp verifica il software che avvia od installa durante l'upgrade ?

Questa è una funzionalità in pianificazione. Vedere il Bug 877623 per aggiornamenti sul suo stato.

Dove posso chiedere ?

Per adesso, il posto migliore per fare domande è probabilmente il canale #fedora-qa^[?] su Freenode IRC o la mailing list test.

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

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 (yum --enablerepo=updates-testing install fedup 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.).

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.

1. Start the upgrade prep by executing following command
   • sudo fedup-cli --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 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.
2. Start the upgrade prep by executing the following command
   • sudo fedup-cli --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
   • sudo fedup-cli --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

Needs Reference
This section still needs a reference to the 'esc kills plymouth' bug once a suitable summary has been written

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.
   • If you add rd.upgrade.debugshell boot argument, you will get a login shell on VT2, allowing you to tinker with the system in case something goes wrong
3. Select the System Upgrade option from the GRUB menu
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 but that does not mean the upgrade has stopped. 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 41 will be on the grub menu

GRUB Updates

Needs update
This part of the documentation is updating.

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)

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

sudo yum install grub2-efi

Migrating Grub Configuration

Unfortunately, most boot settings are not migrated to grub2 without manual intervention. To migrate these settings, you will need to look the existing grub configuration to migrate settings. Open the /boot/efi/EFI/redhat/grub.conf and find the most recent boot entry. The version numbers don't need to exactly match the example, just find the most recent one.

title Fedora (3.6.11-1.fc17.x86_64)
        root (hd0,2)
        kernel /vmlinuz-3.6.11-1.fc17.x86_64 rd.luks.uuid=luks-f664c3a9-e939-410e-8478-891f48b80f12
                rd.md=0 rd.dm=0  KEYTABLE=us SYSFONT=True rd.lvm.lv=vg_test/lv_root
                root=/dev/mapper/vg_test-lv_root ro rd.lvm.lv=vg_test/lv_swap
                LANG=en_US.UTF-8 rhgb quiet
        initrd /initramfs-3.6.11-1.fc17.x86_64.img

We are not interested in all of the arguments following kernel, mostly arguments which start with rd. and a few other specific arguments. In the example listed above, we're interested in:

rd.luks.uuid=luks-f664c3a9-e939-410e-8478-891f48b80f12
rd.md=0
rd.dm=0
rd.lvm.lv=vg_test/lv_root
root=/dev/mapper/vg_test-lv_root
ro
rd.lvm.lv=vg_test/lv_swap
rhgb
quiet

To migrate the configuration, open /etc/default/grub with sudo or as root and paste the following template in:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_RECOVERY="true"
GRUB_THEME="/boot/grub2/themes/system/theme.txt"

non-us keymaps and languages
Need to write docs on how to figure out the vconsole lang and keymap args

Take the kernel args that we extracted before and insert them inside the quotes following GRUB_CMDLINE_LINUX. In this example, it would look like the following. Note that formatting has been slightly altered for the wiki - there should be no newlines in the text following GRUB_CMDLINE_LINUX.

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-f664c3a9-e939-410e-8478-891f48b80f12
rd.md=0 rd.dm=0 rd.lvm.lv=vg_test/lv_root root=/dev/mapper/vg_test-lv_root
ro rd.lvm.lv=vg_test/lv_swap rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_THEME="/boot/grub2/themes/system/theme.txt"

Now that we've migrated the required grub settings, we can wrap up by generating a new grub configuration using these new settings and symlinking this new configuration to /etc/grub2-efi.cfg.

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

Updating the EFI boot entry

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, note that <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>

Now your system should have a working grub2-efi bootloader and it should be loaded when you reboot.

Cleaning Up Post Upgrade

Pending
This part of the documentation is still being written

Relevant Bugs: Bug 888085

There are a collection of post-upgrade things to do. Some of which are fixed by doing a distro sync:

yum distribution-synchronization --disablepresto

If you are using google-chrome from the google repository, you must re-install google-chrome due to a packing bug on the Google side of things. Make sure to adjust the command to the build type you would like to install:

yum remove google-chrome-\* && yum install google-chrome-[beta,stable,unstable]

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