Re: SUSE Issues udev name change

[Waite, Dick (External)]

For interest to good people migrating from SLES12 SP-1 to SP-2 I have looked at 
the Release Notes of SP-2 for key word "udev" and did not find any words. If 
you do not do one of the options below your migration runs grand until the new 
IPL and your boot disk is not there any more.

Grand work by a West Coast SUSE support chap.


OkI see what the problem is now.   In SP1 udev named the devices in 
/dev/disk/by-path like this:
fc15-zfcp-0x500507630413d46b:0x40eb4002-part1

In SP2 it's named like this:
ccw-0.0.fc15-fc-0x500507630413d46b-lun-0x40eb4002-part1

There are 2 ways to fix this on your existing SP1 servers:
1. Since you are using scsi devices and not DASD you could use the 
/dev/disk/by-id device in the /etc/fstab instead of the /dev/disk/by-id
So you would replace the 
/dev/disk/by-path/fc15-zfcp-0x500507630413d46b:0x40eb4002-part1with 
/dev/disk/by-id/scsi-36005076304ffd46beb02-part1

or

2. Before the update edit the /etc/fstab and change the name of the by-path 
device by replacing the ":" in the name with "-lun-"

__R

From: Waite, Dick (External)
Sent: 23 December 2016 12:18
To: Linux on 390 Port
Subject: RE: Goldimage Redhat 7.1

Good Morning,

I have SR 101040685023 with SUSE, open against issues with /dev not there 
after, in my case, an update/migration from SP-1... but I understand from 
support it can occur under other circumstance. Seem you have found one of the 
circumstances...

It's not just /dev/root this is missing, it's /dev

I was told by support yesterday morning then have repro'ed the issue and are 
working on it...

We have seen this with RHEL but not so often as with SUSE  With SUSE and a 
LVM environment with /usr as part of "/" it can happen each time you migrate a 
SP-1 to SP-2. In our case a new install does work Okay, only update/migration 
has this missing /dev

Have a grand day.

__R


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Kumar 
[kumarsyste...@gmail.com]
Sent: 23 December 2016 11:54
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Goldimage Redhat 7.1

I retried the installation and i didnt miss all messages this time

*[ [32m  OK   [0m] Started Show Plymouth Boot Screen.
  *
*[ [32m  OK   [0m] Reached target Paths.
   *
*[ [32m  OK   [0m] Reached target Basic System.
 *
* Starting Dracut Emergency Shell...
 *
*dracut-initqueue[680]: Warning: Could not boot.
 *
*dracut-initqueue[680]: Warning: /dev/root does not exist
*
*Warning: /dev/root does not exist
 *


*Generating "/run/initramfs/rdsosreport.txt"
 *




*Entering emergency mode. Exit the shell to continue.
*
*Type "journalctl" to view system logs.
*
*You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or
/boot*
*after mounting them and attach it to a bug report.
*




*dracut:/#   *
*dracut:/# journalctl
  *
*journalctl
  *
* [?1h = -- Logs begin at Fri 2016-12-23 10:39:14 UTC, end at Fri
2016-12-23 10:42:41 UTC [m  *
*Dec 23 10:39:14 localhost systemd-journal[63]: Runtime journal is using
6.1M (ma [m  *
*Dec 23 10:39:14 localhost systemd-journal[63]: Runtime journal is using
6.1M (ma [m  *
*Dec 23 10:39:14 localhost kernel: Initializing cgroup subsys cpuset [m
  *
*Dec 23 10:39:14 localhost kernel: Initializing cgroup subsys cpu [m
*
*Dec 23 10:39:14 localhost kernel: Initializing cgroup subsys cpuacct [m
*
*Dec 23 10:39:14 localhost kernel:  [1;39mLinux version
3.10.0-229.el7.s390x (mockbuild@ [m*
*Dec 23 10:39:14 localhost kernel: setup: Linux is running as a z/VM guest
operat [m   *
*Dec 23 10:39:14 localhost kernel:  [1;39mZone ranges: [0m [m
   *
*Dec 23 10:39:14 localhost kernel:  [1;39m  DMA  [mem
0x-0x7fff] [0m [m*
*Dec 23 10:39:14 localhost kernel:  [1;39m  Normal   empty [0m [m
   *
*Dec 23 10:39:14 localhost kernel:  [1;39mMovable zone start for each node
[0m [m  *
*Dec 23 10:39:14 localhost kernel:  [1;39mEarly memory node ranges [0m [m
   *
*Dec 23 10:39:14 localhost kernel:  [1;39m  node   0: [mem
0x-0x3fff] [0m [m   *
*Dec 23 10:39:14 localhost kernel: On node 0 totalpages: 262144 [m
*
*Dec 23 10:39:14 localhost kernel:   DMA zone: 4096 pages used for memmap
[m   *
*Dec 23 10:39:14 localhost kernel:   DMA zone: 0 pages reserved [m
*
*Dec 23 10:39:14 localhost kernel:   DMA zone: 262144 pages, LIFO batch:31
[m  *

Re: *LOGREC on zLinux

[Neale Ferguson]

I created an IUCV character device driver that should work. I use it to
connect to *MSG/*MSGALL. It also supports ioctls() to set/get various
things including enabling 2way comms.

There are rpms for various kernels and the source for the same at:

http://download.sinenomine.net/OSS/

On 12/29/16, 5:38 AM, "Linux on 390 Port on behalf of joão paulo limberger
(shoo)"  wrote:

>Hi!
>
>Is there a way to receive IUCV data from *LOGREC on zLinux machine?

--
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/

Re: new subnet for cloned zlinux guest

[Kumar]

Hi Mike and Fred,

Thank you for the replies.

I checked again with the Network folks and found that the Switch was not
configured to make the subnet usable, they will do the changes next week
and hopefully i will be able to use the IPs then.

Regards,
Kumar

On Wed, Dec 28, 2016 at 8:56 PM, Mike Riggs  wrote:

> If the new subnet is in a new VLAN, have the necessary grants been issued?
>
> Mike
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Kumar
> Sent: Wednesday, December 28, 2016 10:10 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: new subnet for cloned zlinux guest
>
> Hi,
>
> We have been successfully able to clone Suse gold images to guests but off
> late we ran out of IPs from a particular subnet.
>
> So Network team assigned new set of subnet, have assigned the new IP to a
> new zlinux Suse 12 guest and also new default gateway using eth0 down and
> up  commands but still we cannot SSH to it.
>
> Previously we just had to update the IP assigned and default gateway using
> the eth0 down and up commands we were able to ssh to it.
>
> Please advise
>
> Regards,
> Kumar
>
> --
> 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/

Re: systemd Failed unmounting /usr

[van Sleeuwen, Berry]

Today I have installed the 1013989 PTF's. After reboot I do not see any "Failed 
unmounting" messages anymore. So it looks like this fix indeed has solved the 
issue.

Thank you for pointing to this fix number.

Regards, Berry.

Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Wednesday, December 21, 2016 1:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: systemd Failed unmounting /usr

>>> On 12/20/2016 at 03:00 PM, Marcy Cortes  
>>> wrote:

> Do you have a bug number I can reference when I open an SR to get a
> test fix from SUSE?

1013989


Mark Post

--
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/
This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, Atos’ liability cannot be triggered for the message 
content. Although the sender endeavours to maintain a computer virus-free 
network, the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. On all 
offers and agreements under which Atos Nederland B.V. supplies goods and/or 
services of whatever nature, the Terms of Delivery from Atos Nederland B.V. 
exclusively apply. The Terms of Delivery shall be promptly submitted to you on 
your request.

*LOGREC on zLinux

[shoo]

Hi!

Is there a way to receive IUCV data from *LOGREC on zLinux machine?

Thanks,
jp

--
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/