Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
Subject: Re: [LINUX-390] SLES12 boot error after clone 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>

Re: SLES12 boot error after clone

2017-05-09 Thread Dave Myers
ot use UUID and use by-path ?? From: Dave Myers Sent: Monday, May 08, 2017 5:57 PM To: 'LINUX-390@VM.MARIST.EDU' <LINUX-390@VM.MARIST.EDU> Subject: SLES12 boot error after clone A bootable SLES12 SP1 system was cloned using flashcopy. All minidisks on the clone are the same virtual addre

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:

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

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.

Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
ers Sent: Monday, May 8, 2017 4:57 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES12 boot error after clone 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)

Re: SLES12 boot error after clone

2017-05-09 Thread Marcy Cortes
t: Monday, May 8, 2017 4:57 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES12 boot error after clone 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 4

SLES12 boot error after clone

2017-05-08 Thread Dave Myers
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. 1. What's the most likely cause for this error?