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 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>200 201>201 2. 201 is the root (for both source/target) 3. In /etc/default/grub....we have statements referencing 200 (not 201). So I'm guessing Marcy is correct that the boot process is ignoring those incorrect device numbers and using UUID. So after FC the targets have incorrect UUID ? So, her script changes boot process to not 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 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? 2. What script/files do we need to tweak to fix it ? Note: On the golden copy, 200 is the root, 201 is a swap file. Thanks, Dave This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. This message may be viewed by parties at Sirius Computer Solutions other than those named in the message header. This message does not contain an official representation of Sirius Computer Solutions. If you have received this communication in error, notify Sirius Computer Solutions immediately and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. Sirius Computer Solutions<http://www.siriuscom.com> ---------------------------------------------------------------------- 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/