Unable to upgrade SLES12 SP5 to SLES 15 SP1

0

In SLES 12 SP5, when we reboot the Server after installing below package to migrate the system to SLES 15 SP1

zypper in SLES15-Migration suse-migration-sle15-activation

its failing to migrate to SLES 15 SP1 with below mentioned error logs:

Device path /dev/disk/by-uuid/"b7bbd4b5-81ee-4cf9-b80f-048dd3eb6085" not found and skipped
Device path /dev/disk/by-uuid/"242dbaba-e687-48ea-99fb-3b5f905123da" not found and skipped
Device path /dev/disk/by-uuid/"03eefbc1-b95f-4125-a7bc-83034bff48ae" not found and skipped
Device path /dev/disk/by-uuid/"b9459393-776b-473c-bc7a-7d17de295a6d" not found and skipped
Device path /dev/disk/by-uuid/"f7cf5298-1a20-4a79-8b22-546b0c44176b" not found and skipped
Device path /dev/disk/by-uuid/"aef286fb-4fb0-4e47-a2cd-f2bc31af7d03" not found and skipped
Device path /dev/disk/by-uuid/"19456e98-c7da-4591-b295-e0fc297179f4" not found and skipped
Device path /dev/disk/by-uuid/"04db4e56-3f5a-4f77-86c1-5c3932f8ca58" not found and skipped
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Device path /dev/disk/by-uuid/"b7bbd4b5-81ee-4cf9-b80f-048dd3eb6085" not found and skipped
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']
Running suse-migration-pre-checks with options: fix: False
Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT']

This happening after 25th Aug 2022. Before that we could migrate successfully. Please check and help us to fix this error.

posta 2 anni fa750 visualizzazioni
1 Risposta
0

Upgrade from SUSE 12 SP4 or SP5 to SUSE 15 SP1, please follow the steps below:

Step 1: - Edit the /etc/fstab file and replace the root volume entry with the UUID of the new root volume. Save the changes.

Step 2: - Modify the /etc/default/grub file with the following changes:

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=1
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 multipath=off net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 8250.nr_uarts=4 dis_ucode_ldr"
GRUB_CMDLINE_LINUX=""
GRUB_DISTRIBUTOR="SLES 12 SP5 EC2"
GRUB_GFXMODE=800x600
GRUB_TERMINAL="gfxterm"
GRUB_USE_INITRDEFI=true
GRUB_USE_LINUXEFI=true

Save the changes.

Step 3: - Regenerate the GRUB configuration by running the following command:

grub2-mkconfig -o /boot/grub2/grub.cfg

Step 4: - Install the latest package updates for the VM by running the following commands:

zypper clean --all zipper refresh zipper update

Once the updates are installed, restart the VM to apply the changes.

Step 5: - After the restart, verify the kernel and OS version to ensure that it is now SUSE 12 SP4 or SUSE 12 SP5:

uname -a cat /etc/os-release

Step 6: - Install the suse-migration-sle15-activation package, which will automatically install the SLES15-Migration package as a dependency:

zipper install suse-migration-sle15-activation
zipper in suse-migration-sle15-activation

Step 7: - Update the /etc/zypper/zypper.conf file and add the following line to the [main] section:

solver.onlyRequires = true

Add the following line in the [main] section to disable the installation of recommended packages:

installRecommends=false

Step 8: - Reboot the system to apply the changes.

By following these steps, you should be able to perform a successful upgrade from SUSE 12 SP4 or SP5 to SUSE 15 SP1.

Please note that it is always recommended to take proper backups and test the upgrade in a non-production environment before performing it on live systems.

con risposta 10 mesi fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande