Re: LVM does not see 2nd LVM on reboot
Were you able to complete the installation having defined two volume groups during the initial YaST conversation? If so, could you describe the VG's as to number of volumes and the logical volumes that were defined on them? >From your original description of your problem, it sounded more like you were >adding an additional volume group after the installation completed. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - "In theory, theory and practice are the same, but in practice, theory and practice are different." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Libutti Sent: Friday, September 02, 2005 2:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM does not see 2nd LVM on reboot It was two vgs during install. mkinitrd and zipl fixed the problem. Thanks all. >>> [EMAIL PROTECTED] 9/2/2005 2:50:33 PM >>> Did you create two Volume Groups, or just two Logical Volumes from one Volume Group?Robert Nix had a problem where he created two VGs during the install of a SLES9 SP2 system, and when the system tried to boot, the LVs weren't available. Removing one of the two VGs "fixed" the problem. -- 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
Re: LVM does not see 2nd LVM on reboot
It was two vgs during install. mkinitrd and zipl fixed the problem. Thanks all. >>> [EMAIL PROTECTED] 9/2/2005 2:50:33 PM >>> Did you create two Volume Groups, or just two Logical Volumes from one Volume Group?Robert Nix had a problem where he created two VGs during the install of a SLES9 SP2 system, and when the system tried to boot, the LVs weren't available. Removing one of the two VGs "fixed" the problem. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Libutti Sent: Friday, September 02, 2005 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM does not see 2nd LVM on reboot This is a SLES9 sp2 on z/vm. We have created two lvm groups and then our required mount points. We then successfully mount the new slices. When we reboot the second LVM is not seen nor mounted. This is all done through yast. -- 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 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
Re: LVM does not see 2nd LVM on reboot
Did you create two Volume Groups, or just two Logical Volumes from one Volume Group?Robert Nix had a problem where he created two VGs during the install of a SLES9 SP2 system, and when the system tried to boot, the LVs weren't available. Removing one of the two VGs "fixed" the problem. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Libutti Sent: Friday, September 02, 2005 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM does not see 2nd LVM on reboot This is a SLES9 sp2 on z/vm. We have created two lvm groups and then our required mount points. We then successfully mount the new slices. When we reboot the second LVM is not seen nor mounted. This is all done through yast. -- 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
Re: LVM does not see 2nd LVM on reboot
> This is a SLES9 sp2 on z/vm. We have created two lvm groups > and then our required mount points. We then successfully > mount the new slices. > When we reboot the second LVM is not seen nor mounted. This > is all done through yast. You forgot to mkinitrd and zipl following the new volume definitions. YaST doesn't do this for 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
Re: LVM does not see 2nd LVM on reboot
Did you run mkinitrd and zipl afterwards? Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Libutti Sent: Friday, September 02, 2005 1:11 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM does not see 2nd LVM on reboot This is a SLES9 sp2 on z/vm. We have created two lvm groups and then our required mount points. We then successfully mount the new slices. When we reboot the second LVM is not seen nor mounted. This is all done through yast. -- 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 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
Re: LVM does not see 2nd LVM on reboot
Did you run mkinitrd? If not, you may want to manually scan and mount your new stuff and then run mkinitrd when everything looks good. You really should report this to SuSE as yast should at least give you a warning or an opportunity to run mkinitrd following a change/addition to LVM. This is perhaps THE most common error people encounter when it comes to LVM. -Original Message- This is a SLES9 sp2 on z/vm. We have created two lvm groups and then our required mount points. We then successfully mount the new slices. When we reboot the second LVM is not seen nor mounted. This is all done through yast. -- 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
