Hi Mark,

Thanks for your test. Indeed I can open up an SR at IBM. Good to know it 
shouldn't be normal behavior.

Let me list some more details on the installation process.

/* Not actual mdisk password:-) just to show where the disks go */
USER SLES12
MDISK 0100 3390 1 3338 LXG1A4 MR    root
MDISK 0102 3390 3339 300 LXG1A4 MR  swap
MDISK 0104 3390 3639 6378 LXG1A4 MR rootvg
MDISK 0105 3390 1 10016 LXG1A3 MR  rootvg
MDISK 0106 3390 1 10016 LXG1A2 MR  rootvg
MDISK 0107 3390 1 10016 LXG1A1 MR  rootvg

During install I reworked the partitions:

/dev/dasda1                    2299908  253036   1910328  12% /
/dev/mapper/rootvg-usrlv       5029504 1849864   2901112  39% /usr
/dev/mapper/rootvg-optlv       3030800  415828   2441304  15% /opt
/dev/mapper/rootvg-varlv       5029504  102524   4648452   3% /var
/dev/mapper/rootvg-servicelv   5029504   10232   4740744   1% /service
/dev/mapper/rootvg-homelv      1998672 1233496    643936  66% /home
/dev/mapper/rootvg-tmplv       2064208    3096   1956256   1% /tmp

I have removed "Gnome Desktop" and "X window System" from the software list 
(patterns). Install is executed with an ssh terminal.

During reboot after in initial install I already see some messages regarding 
/usr but I have to investigate further to see when this issue actually happens. 
After initial install I have updated grub and Dracut to make sure disks are 
referred to as by-path. (refer to a discussion regarding UUID some time ago.) 
It might be it only appears only after I had updated grub/Dracut.


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


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post
Sent: Wednesday, December 14, 2016 7:52 PM
To: [email protected]
Subject: Re: systemd Failed unmounting /usr

>>> On 12/14/2016 at 10:31 AM, "van Sleeuwen, Berry"
>>> <[email protected]>
wrote:
> Hi All,
>
> I have installed a new SLES12 SP2 guest. The root partition is on one
> partition (/dev/dasda1). The remaining system directories are stored
> within an lvm, rootvg. This lvm contains logical volumes for /usr,
> /opt, /home, /tmp and /var.
>
> During boot, when systemd is started it tries to umount /usr. After a
> couple of tries umount ends. But I did have one occasion where the
> umount apparently succeeded as the guest came up in emergency mode, without 
> /usr mounted.

I just did an install to try to replicate this, and I see nothing like that 
happening.  The only messages I see regarding /usr are these:
Dec 14 13:00:22 linux dracut-initqueue[307]: inactive '/dev/system/usr' [3.00 
GiB] inherit Dec 14 13:00:22 linux systemd[1]: Mounting /sysroot/usr...
Dec 14 13:00:22 linux systemd[1]: Mounted /sysroot/usr.

Clearly there's something quite different about my install versus yours.  I 
think you're going to need to open a service request with your service provider.


Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] 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.

Reply via email to