Hi Harley, Is the LVM startup activated? I had a similar problem last week with an SLES11 SP3, after boot the boot.lvm wasn't activated in init.d so the LVM wasn’t found during boot. In systemd you need to active lvm2-activation.
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 Linker Harley - hlinke Sent: Monday, December 15, 2014 3:14 PM To: [email protected] Subject: Need help with LVM in SLES 12 on System z I am running SLES 12 (base install - no maintenance) as a guest under z/VM 6.3 non-SSI mainly to play with SLES 12 and identify the differences between it and SLES 11 SP3. Not that it matters, but this is a sandbox z/VM that has no access to the internet so I can't easily obtain and install maintenance. Almost immediately installing SLES 12 I created a LV using the btrfs filesystem on a single 3390-9 - the filesystem utilizes all of the space. After creating the LVM, I created the entry in /etc/fstab and mounted it using 'mount -a'. I worked on the system for a while and then decided to reboot. My system went into recovery mode as my new filesystem could not be found at boot time. Luckily, I has saved a copy of fstab and was able to save the exist fstab as fstab.new and copied the backup copy to fstab. When I rebooted I was able to bring up the full system and logged in with PuTTY. The output of the lvdisplay command shows the LV Status as 'NOT available'. I issued 'vgchange -ay' and the lvdisplay output showed the status as 'available'. If I reboot the system the LVM is again marked 'NOT available'. I never had this problem with earlier SLES versions, 'vgchange -ay' resolved the problem permanently. What do I need to do to force the LV to be available after every reboot in SLES 12? LV and fstab setup: I created the LV using the following commands (via PuTTY): pvcreate /dev/dasdd1 vgcreate sysg1 /dev/dasdd1 lvcreate -l 1760 -n system-lv1 sysg1 mkfs.btrfs /dev/sysg1/system-lv1 I obtained the 1760 in the lvcreate command from the 'Total PE' value as output from command 'vgdisplay sysg1' . I then updated /etc/fstab (after copying fstab to fstab.orig). I wanted to mount this new filesystem at /srv to eventually serve as a repository for the SLES 12 DVD1 iso file. I edited fstab to add: /dev/sysg1/system-lv1 /srv/ftp/repository btrfs defaults 0 0 Harley HARLEY LINKER JR. Sr. Systems Programmer (z/Linux, z/OS, z/VM) [Acxiom_IT_color] Acxiom Corporation EML [email protected]<mailto:[email protected]> TEL +1 630.944.5111 3333 Finley Road, 8th Floor - NW, Downers Grove, IL, 60515, USA www.acxiomit.com<http://www.acxiomit.com/> [Friend Us on Facebook]<http://www.facebook.com/acxiomcorp> [Link Us on LinkedIn] <http://www.linkedin.com/groupRegistration?gid=2901735> [Follow Us on Twitter] <http://twitter.com/acxiom> *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. **************************************************************************** ---------------------------------------------------------------------- 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.
