Hi What do you mean it still mounts a gold LUN? You boot from from a NEW Lun but root filesystem ends up beeing mounted from GOLD Lun? First of I all I would make sure that GOLD lun after clonning is not accesible in virtual machine anymore. Just to make it simple.
I can't remember how it is done in SLES but in RHEL there is a bunch of stuff that refers to a specific LUN with a specific scsi_id For example multipath (/etc/multipath.conf) configuration. In there you usually you bond scsi_id (wwid) of Lun with friendly name (mpathX for example). That multipath configuration is also saved in initrd. So if you boot from clone, it will end up mounting wrong volume. Are you using LVM? 2017-09-07 9:08 GMT-04:00 Greg Preddy <gpre...@cox.net>: > All, > > We're doing SLES 12 on 100% LUN, with gold copy on a single 60GB LUN. > This is a new cloning approach for us so we're not sure how to make this > work. Our Linux SA got the storage admin to replicate the LUN, but when > we change the server to boot the copy, it still mounts the gold LUN. > 99% sure we got the LOADDEV parms right. Does anyone have steps to > clone a LUN-only SLES 12 system? > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
