Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
Yes, my stuff gets the UUID out of everything and using by-path instead. You get different UUIDs on different minidisks. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dave Myers Sent: Tuesday, May 9, 2017 9:46 AM To: LINUX-390@VM.MARIST.EDU Subje

Re: SLES12 boot error after clone

2017-05-09 Thread Dave Myers
Thanks for the replies. We are going to try Marcy's script and see if that works. I'll report back. To clarify a few of my original comments: 1. The source volumes were flash-copied to the equivalent virtual device numbers. 200>200 201>201 2. 201 is the root (for both source/t

Re: SLES12 boot error after clone

2017-05-09 Thread Mark Post
>>> On 5/8/2017 at 07:57 PM, Dave Myers wrote: > A bootable SLES12 SP1 system was cloned using flashcopy. > All minidisks on the clone are the same virtual address. > > At boot on the clone we get: > > IPL 201 > Booting default (grub2) > dasd-eckd 42a207: 0.0.0200: The specified record was no

Re: SLES12 boot error after clone

2017-05-09 Thread Scott Rohling
I also think not swapping addresses around might help avoid errors and at least confusion...what is the point of cloning 200 > 201 and 201 > 200 ? Have you tried readdressing your disks to match the guest you cloned from? Scott Rohling On Tue, May 9, 2017 at 8:26 AM, Stefan Haberland wro

Re: SLES12 boot error after clone

2017-05-09 Thread Stefan Haberland
Hi, unfortunately I am not that deep into flashcopy, so please excuse if I assume something wrong. On 09.05.2017 01:57, Dave Myers wrote: A bootable SLES12 SP1 system was cloned using flashcopy. All minidisks on the clone are the same virtual address. Do the minidisks have exactly the same si

Re: SLES12 boot error after clone

2017-05-09 Thread Steffen Maier
On 05/09/2017 01:57 AM, Dave Myers wrote: A bootable SLES12 SP1 system was cloned using flashcopy. All minidisks on the clone are the same virtual address. At boot on the clone we get: IPL 201 Booting default (grub2) dasd-eckd 42a207: 0.0.0200: The specified record was not found. https://ww

Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
Oh wait, step 3 isn't necessary at some point in the dracut service stream. SUSE created a /etc/dracut.conf.d/10-s390x_persistent_device.conf file which includes the persistent_policy=by-path thing Not sure if you have that on - from rpm -q dracut --changelong * Fri Dec 23 2016 tr...@suse.de - Fi

Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
It's probably using UUID and not the 0200 address Here's the things I had to do to allow clones and allow it to run in other places after a flashcopy. 1. Added root=/dev/disk/by-path/ccw-0.0.0101-part1 to the kernel parms (under yast2, system, bootloader) (101 is our IPL address) 2. In /etc/