We're trying to upgrade a SLES 11 SP4 system to SLES 12 SP3 using HTTP as the protocol for the network installation. The system boots fine and we're able to connect to the VNC display. The installer is able to grab files from the HTTP server as well but it fails when it comes to recognizing the existing system.
In the "Disk Activation" section we see our DASD disks and, after activating them (without formatting of course), we then proceed to the next section where we're supposed to select the "System or Partition to Update" but nothing shows up. This is our parameter file (notice we use "upgrade=1" to trigger upgrade): ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb hostip=192.168.10.24 netmask=255.255.255.0 gateway=192.168.10.1 nameserver=192.168.10.2 portname=none portno=0 instnetdev=osa osainterface=qdio osamedium=eth layer2=1 OSAHWaddr=02:78:C1:02:48:01 upgrade=1 readchannel=0.0.0360 writechannel=0.0.0361 datachannel=0.0.0362 usevnc=1 vncpassword=password hostname=pilotsrv install=http://192.168.10.40/SLES12/s390x/DVD1 Is there a way to make the installer recognize the existing SLES11 installation? Our / filesystem is /dev/dasda1 and the rest of filesystems are LVM-based. Regards, Victor Echavarry System Programmer Operating Systems ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
