Can't perform offline update from SLES 11 SP2 to SP3

I am trying to update a virtual server using physical media (SLES 11 SP3 ISO) to upgrade offline but can’t get past the stage of Specifying the Partition to Update.
I receive the error: “No installed system that can be upgraded with this product was found on the selected partition”

Here is a screen shot of the error:

Attempted fixes:
I’ve set the /boot and / partition mount point to use device paths.
The server has been fully patched with YOU and rebooted a number of times.
Searched the Knowledgebase and the update readme file.

Info about the server

Novell Open Enterprise Server 11 (x86_64)
VERSION = 11.1

SUSE Linux Enterprise Server 11 (x86_64)


dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0-part2 swap swap defaults 0 0
/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0-part3 / btrfs defaults 1 1
/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:0:0-part1 /boot ext3 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0


Disk /dev/sda: 26.8 GB, 26843545600 bytes
255 heads, 63 sectors/track, 3263 cylinders, total 52428800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000e92f

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 321535 159744 83 Linux
/dev/sda2 321536 4530175 2104320 82 Linux swap / Solaris
/dev/sda3 4530176 41943039 18706432 83 Linux


Filesystem Size Used Avail Use% Mounted on
/dev/sda3 18G 13G 3.3G 80% /
udev 940M 88K 940M 1% /dev
tmpfs 940M 148K 940M 1% /dev/shm
/dev/sda1 152M 47M 98M 33% /boot

I hope someone has a good idea to get past this issue.


In your case (since it’s OES) you are better off to ask your question
over here;

Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

I have an SR open and am finally making progress.

In the end we’ve removed all existing repos, re-registered sles (and oes) with suse_register, then run the online upgrade with yast2 wagon. All is progressing well at this stage.

So in this case the root cause of why the offline upgrade failed has not been determined, but the end result of a patch upgrade should be achieved in the next 20-30 min. I have normally avoided online upgrades due to being burnt once, but as this is a VM we have the safety of a snapshot.