Re: LVM problem. Lost VG info
>>> On Tue, Jun 17, 2008 at 9:04 AM, in message <[EMAIL PROTECTED]>, RPN01 <[EMAIL PROTECTED]> wrote: -snip- > This is the last step in adding DASD, and the one that I've forgotten way > too many times. Given that it has to happen, my question is why YaST doesn't > perform the mkinitrd and zipl commands itself as part of the process. I know > that you can attach DASD temporarily, but it would seem simple enough to do > the commands again when you take DASD out of the configuration as well > It's just way too easy to forget to do. For some time now, it has done just that, providing you do indeed use YaST to add the new volumes. 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
Re: LVM problem. Lost VG info
I finally got it working again. My initial attempts to restore didn't work, but after going back to the second backup, it did restore and was able to find the VG. I really appreciate everyone's responses. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of CHAPLIN, JAMES (CTR) Sent: Tuesday, June 17, 2008 9:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Were you able to verify that the device is online? If lscss is unavailable, go to the dev directory: Determine the device number (say 204) either from an lsdasd or cat /proc/dasd/devices cd /sys/bus/ccw/drivers/dasd-eckd/0.0.0204 cat online . . . .if value zero (offline), then echo 1 > online James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc (703) 921-6220 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 9:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info This is on sles8, so I don't have the lscss command, but when I try the vgchange -ay it cant find any volume groups. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Szefler Jakub Sent: Tuesday, June 17, 2008 9:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Have you all disks online ? Issue command : lscss and check it. After then you can try: vgscan vgchange -ay Best regards, Jakub Szefler Administrator zOS/zVM -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 2:58 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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 -- 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 -- 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 problem. Lost VG info
Were you able to verify that the device is online? If lscss is unavailable, go to the dev directory: Determine the device number (say 204) either from an lsdasd or cat /proc/dasd/devices cd /sys/bus/ccw/drivers/dasd-eckd/0.0.0204 cat online . . . .if value zero (offline), then echo 1 > online James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc (703) 921-6220 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 9:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info This is on sles8, so I don't have the lscss command, but when I try the vgchange -ay it cant find any volume groups. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Szefler Jakub Sent: Tuesday, June 17, 2008 9:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Have you all disks online ? Issue command : lscss and check it. After then you can try: vgscan vgchange -ay Best regards, Jakub Szefler Administrator zOS/zVM -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 2:58 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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 -- 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 problem. Lost VG info
No problem. I have tried vgcfgrestore to the version before I added the dasd to no avail. I'm not sure what favorite tools to use to read that. Any suggestions? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Tuesday, June 17, 2008 9:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Also note that the information necessary to recreate the LVM environment should be stored in the first few blocks of any of the PV devices (I think there's actually about five copies there.) Use your favorite tool to read the physical device, and you should be able to extract the information you need to re-build the environment. Sorry if the other message was a false start, but you didn't say if you could actually see the physical devices, and it was the first thought that came to me -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 6/17/08 8:03 AM, "CHAPLIN, JAMES (CTR)" <[EMAIL PROTECTED]> wrote: > Did you try a vgscan? > > James Chaplin > Systems Programmer, MVS, zVM & zLinux > Base Technologies, Inc > (703) 921-6220 > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Walters, Gene P > Sent: Tuesday, June 17, 2008 8:58 AM > To: LINUX-390@VM.MARIST.EDU > Subject: LVM problem. Lost VG info > > I'm already having a bad day. I took one of our Linux Instances down to > add more disk space to it. Everything went fine. I used Yast2 to add > the new volumes to the VG. Now when I IPL, it cant find the volume > group. > > I ran a PVSCAN, and it shows all my physical volumes are associated to > an unknown VG. I've looked at several commands, but I guess I just > don't understand. Hopefully my data is not lost. Is there a way to > rebuild the VG? > > -- > 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 -- 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 problem. Lost VG info
This is on sles8, so I don't have the lscss command, but when I try the vgchange -ay it cant find any volume groups. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Szefler Jakub Sent: Tuesday, June 17, 2008 9:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Have you all disks online ? Issue command : lscss and check it. After then you can try: vgscan vgchange -ay Best regards, Jakub Szefler Administrator zOS/zVM -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 2:58 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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 -- 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 problem. Lost VG info
Have you all disks online ? Issue command : lscss and check it. After then you can try: vgscan vgchange -ay Best regards, Jakub Szefler Administrator zOS/zVM -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 2:58 PM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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 problem. Lost VG info
I actually did mkinitrd and zipl and ipl'd, formatted and then did yast. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Tuesday, June 17, 2008 9:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info After adding the new DASD, did you run mkinitrd and zipl, to fold them into the boot configuration? I think that on RedHat, you also have to add them to the parm line in the zipl.conf file This is the last step in adding DASD, and the one that I've forgotten way too many times. Given that it has to happen, my question is why YaST doesn't perform the mkinitrd and zipl commands itself as part of the process. I know that you can attach DASD temporarily, but it would seem simple enough to do the commands again when you take DASD out of the configuration as well It's just way too easy to forget to do. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 6/17/08 7:58 AM, "Walters, Gene P" <[EMAIL PROTECTED]> wrote: > I'm already having a bad day. I took one of our Linux Instances down to > add more disk space to it. Everything went fine. I used Yast2 to add > the new volumes to the VG. Now when I IPL, it cant find the volume > group. > > I ran a PVSCAN, and it shows all my physical volumes are associated to > an unknown VG. I've looked at several commands, but I guess I just > don't understand. Hopefully my data is not lost. Is there a way to > rebuild the VG? > > -- > 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 -- 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 problem. Lost VG info
Also note that the information necessary to recreate the LVM environment should be stored in the first few blocks of any of the PV devices (I think there's actually about five copies there.) Use your favorite tool to read the physical device, and you should be able to extract the information you need to re-build the environment. Sorry if the other message was a false start, but you didn't say if you could actually see the physical devices, and it was the first thought that came to me -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 6/17/08 8:03 AM, "CHAPLIN, JAMES (CTR)" <[EMAIL PROTECTED]> wrote: > Did you try a vgscan? > > James Chaplin > Systems Programmer, MVS, zVM & zLinux > Base Technologies, Inc > (703) 921-6220 > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Walters, Gene P > Sent: Tuesday, June 17, 2008 8:58 AM > To: LINUX-390@VM.MARIST.EDU > Subject: LVM problem. Lost VG info > > I'm already having a bad day. I took one of our Linux Instances down to > add more disk space to it. Everything went fine. I used Yast2 to add > the new volumes to the VG. Now when I IPL, it cant find the volume > group. > > I ran a PVSCAN, and it shows all my physical volumes are associated to > an unknown VG. I've looked at several commands, but I guess I just > don't understand. Hopefully my data is not lost. Is there a way to > rebuild the VG? > > -- > 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 -- 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 problem. Lost VG info
Yes, a VGscan tells me ERROR "vg_read_with_pv_and_lv()" cant get data of volume group "oraclevg" from physical volumes. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of CHAPLIN, JAMES (CTR) Sent: Tuesday, June 17, 2008 9:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM problem. Lost VG info Did you try a vgscan? James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc (703) 921-6220 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 8:58 AM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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 -- 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 problem. Lost VG info
After adding the new DASD, did you run mkinitrd and zipl, to fold them into the boot configuration? I think that on RedHat, you also have to add them to the parm line in the zipl.conf file This is the last step in adding DASD, and the one that I've forgotten way too many times. Given that it has to happen, my question is why YaST doesn't perform the mkinitrd and zipl commands itself as part of the process. I know that you can attach DASD temporarily, but it would seem simple enough to do the commands again when you take DASD out of the configuration as well It's just way too easy to forget to do. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 6/17/08 7:58 AM, "Walters, Gene P" <[EMAIL PROTECTED]> wrote: > I'm already having a bad day. I took one of our Linux Instances down to > add more disk space to it. Everything went fine. I used Yast2 to add > the new volumes to the VG. Now when I IPL, it cant find the volume > group. > > I ran a PVSCAN, and it shows all my physical volumes are associated to > an unknown VG. I've looked at several commands, but I guess I just > don't understand. Hopefully my data is not lost. Is there a way to > rebuild the VG? > > -- > 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 problem. Lost VG info
Did you try a vgscan? James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc (703) 921-6220 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Gene P Sent: Tuesday, June 17, 2008 8:58 AM To: LINUX-390@VM.MARIST.EDU Subject: LVM problem. Lost VG info I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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
LVM problem. Lost VG info
I'm already having a bad day. I took one of our Linux Instances down to add more disk space to it. Everything went fine. I used Yast2 to add the new volumes to the VG. Now when I IPL, it cant find the volume group. I ran a PVSCAN, and it shows all my physical volumes are associated to an unknown VG. I've looked at several commands, but I guess I just don't understand. Hopefully my data is not lost. Is there a way to rebuild the VG? -- 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
