[linux-lvm] Adding a disk to a VG gone bad - need help

[linux-lvm] Adding a disk to a VG gone bad - need help

[Jeff Macdonald]

Hi,
I have one volume group and that is used as such:
[root@jeff ~]# /usr/sbin/lvscan
 ACTIVE            '/dev/VolGroup00/Root' [9.78 GB] inherit
 ACTIVE            '/dev/VolGroup00/Home' [231.31 GB] inherit
 ACTIVE            '/dev/VolGroup00/Swap' [320.00 MB] inherit

I added a whole disk to VolGroup00 like so:
[root@jeff ~]# dd if=/dev/zero of=/dev/hde bs=512 count=1
1+0 records in
1+0 records out

created the physical volume:
[root@jeff ~]# /usr/sbin/pvcreate /dev/hde

added it to the volume group:
[root@jeff ~]# /usr/sbin/vgextend VolGroup00 /dev/hde

added 100G from the 150G drive to Home:
[root@jeff ~]# /usr/sbin/lvextend -L+100G /dev/VolGroup00/Home
 Extending logical volume Home to 331.31 GB
 Logical volume Home successfully resized

At this point the docs suggest umounting the logical volume in order
to resize the file system. So I decided I was going to reboot the
computer and start it into single user mode. When doing that I'm
greated with:

lvm exited abnormally!
Couldn't find device with uuid <uuid>
Couldn't find all physical volumes for volume group VolGroup00

So it seems that it can't find the new physical volume that I just
added.  LVM is totally new to me, so any pointers would be great.
Booting from CD into rescue mode I wasn't unable to get very far. I
was able to run lvm and pvscan shows this interesting line:

PV /dev/hdf1 VG VolGroup00 lvm2 [ X GB / X GB free]
PV /dev/hdg2 VG VolGroup00 lvm2 [ Y GB / Y GB free]
PV unknown device VG VolGroup00 lvm2 [ Z GB / Z GB free]
Total: 3 [ X GB ] / in use 3

It seems to be that vgreduce is what I want in order to start over,
but running this in test mode with -t and --removemissing I see this
worrying line:
Removing LV Home from VG

and the line I want
Removing PV with UUID {correct UUID}

Am I on the right track?

TIA


-- 
Jeff Macdonald
Ayer, MA

Re: [linux-lvm] Adding a disk to a VG gone bad - need help

[M. Matt Colgin]

Weird, I'm not totally following how/what happened, but it sounds like
you VG went from 1 PV to 3 (but maybe you started off with two). 
Hopefully you don't have some super important data on it. If you do,
there are some people with more knowledge than me, repost your
question with some more/updated information.

Each LVM command will write a "changelog" to the /etc/lvm/archive/*
directory with the state of the VG before/after the command was
issued. The best bet to undo the extend would be to issue a
vgcfgrestore with the file, before your vgextend.

It might be worth checking into the physical connections for your new
drive. The UUID is basically a uniq signature that is written to the
front of the drive/partition. If this UUID can not be found, then it's
possible the drive went bad or (most likely) the computer doesn't see
the drive anymore. Look at the cables, replace a cable, check out the
BIOS (make sure it's being detected), etc. Fixing a failed connection
is better than messing around with the LVM VG with a missing drive. If
you can get the drive to show up, then it would be a simple matter of
vgreduce.


On Fri, 25 Feb 2005 23:22:59 -0500, Jeff Macdonald
<macfisherman@gmail.com> wrote:
> Hi,
> I have one volume group and that is used as such:
> [root@jeff ~]# /usr/sbin/lvscan
>  ACTIVE            '/dev/VolGroup00/Root' [9.78 GB] inherit
>  ACTIVE            '/dev/VolGroup00/Home' [231.31 GB] inherit
>  ACTIVE            '/dev/VolGroup00/Swap' [320.00 MB] inherit
> 
> I added a whole disk to VolGroup00 like so:
> [root@jeff ~]# dd if=/dev/zero of=/dev/hde bs=512 count=1
> 1+0 records in
> 1+0 records out
> 
> created the physical volume:
> [root@jeff ~]# /usr/sbin/pvcreate /dev/hde
> 
> added it to the volume group:
> [root@jeff ~]# /usr/sbin/vgextend VolGroup00 /dev/hde
> 
> added 100G from the 150G drive to Home:
> [root@jeff ~]# /usr/sbin/lvextend -L+100G /dev/VolGroup00/Home
>  Extending logical volume Home to 331.31 GB
>  Logical volume Home successfully resized
> 
> At this point the docs suggest umounting the logical volume in order
> to resize the file system. So I decided I was going to reboot the
> computer and start it into single user mode. When doing that I'm
> greated with:
> 
> lvm exited abnormally!
> Couldn't find device with uuid <uuid>
> Couldn't find all physical volumes for volume group VolGroup00
> 
> So it seems that it can't find the new physical volume that I just
> added.  LVM is totally new to me, so any pointers would be great.
> Booting from CD into rescue mode I wasn't unable to get very far. I
> was able to run lvm and pvscan shows this interesting line:
> 
> PV /dev/hdf1 VG VolGroup00 lvm2 [ X GB / X GB free]
> PV /dev/hdg2 VG VolGroup00 lvm2 [ Y GB / Y GB free]
> PV unknown device VG VolGroup00 lvm2 [ Z GB / Z GB free]
> Total: 3 [ X GB ] / in use 3
> 
> It seems to be that vgreduce is what I want in order to start over,
> but running this in test mode with -t and --removemissing I see this
> worrying line:
> Removing LV Home from VG
> 
> and the line I want
> Removing PV with UUID {correct UUID}
> 
> Am I on the right track?
> 
> TIA
> 
> --
> Jeff Macdonald
> Ayer, MA
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

Re: [linux-lvm] Adding a disk to a VG gone bad - need help

[Jeff Macdonald]

On Mon, 28 Feb 2005 10:19:46 -0800, M. Matt Colgin <mcolgin@gmail.com> wrote:
> Weird, I'm not totally following how/what happened, but it sounds like
> you VG went from 1 PV to 3 (but maybe you started off with two).

Yes, I started with 2.

> Hopefully you don't have some super important data on it. If you do,
> there are some people with more knowledge than me, repost your
> question with some more/updated information.
>

Just all my digial media! :(
 
> Each LVM command will write a "changelog" to the /etc/lvm/archive/*
> directory with the state of the VG before/after the command was
> issued. The best bet to undo the extend would be to issue a
> vgcfgrestore with the file, before your vgextend.

Well, with Fedora Core 3, this isn't possible, because that data was
stored on a LV. They should make it a symlink to /boot like grub is.

<snip stuff about cables>
This was a disk that was being used as a normal non LVM disk. So it
was properly working while copying data from it to a LV. After all the
data was transferred, I wanted to add it to the existing VG. See
procedures I followed from the previous mail below.

As I outlined before, it seems that doing:

vgreduce --removemissing VolGroup00

may do the trick, but in test mode I see this troubling line:

Removing LV Home from VG

Which is definately not what I want. However, perhaps rerunning
pvcreate -u with the UUID it claims it doesn't have a device for is a
viable alternative?

> On Fri, 25 Feb 2005 23:22:59 -0500, Jeff Macdonald
> <macfisherman@gmail.com> wrote:
> > Hi,
> > I have one volume group and that is used as such:
> > [root@jeff ~]# /usr/sbin/lvscan
> >  ACTIVE            '/dev/VolGroup00/Root' [9.78 GB] inherit
> >  ACTIVE            '/dev/VolGroup00/Home' [231.31 GB] inherit
> >  ACTIVE            '/dev/VolGroup00/Swap' [320.00 MB] inherit
> >
> > I added a whole disk to VolGroup00 like so:
> > [root@jeff ~]# dd if=/dev/zero of=/dev/hde bs=512 count=1
> > 1+0 records in
> > 1+0 records out
> >
> > created the physical volume:
> > [root@jeff ~]# /usr/sbin/pvcreate /dev/hde
> >
> > added it to the volume group:
> > [root@jeff ~]# /usr/sbin/vgextend VolGroup00 /dev/hde
> >
> > added 100G from the 150G drive to Home:
> > [root@jeff ~]# /usr/sbin/lvextend -L+100G /dev/VolGroup00/Home
> >  Extending logical volume Home to 331.31 GB
> >  Logical volume Home successfully resized
> >
> > At this point the docs suggest umounting the logical volume in order
> > to resize the file system. So I decided I was going to reboot the
> > computer and start it into single user mode. When doing that I'm
> > greated with:
> >
> > lvm exited abnormally!
> > Couldn't find device with uuid <uuid>
> > Couldn't find all physical volumes for volume group VolGroup00
> >
> > So it seems that it can't find the new physical volume that I just
> > added.  LVM is totally new to me, so any pointers would be great.
> > Booting from CD into rescue mode I wasn't unable to get very far. I
> > was able to run lvm and pvscan shows this interesting line:
> >
> > PV /dev/hdf1 VG VolGroup00 lvm2 [ X GB / X GB free]
> > PV /dev/hdg2 VG VolGroup00 lvm2 [ Y GB / Y GB free]
> > PV unknown device VG VolGroup00 lvm2 [ Z GB / Z GB free]
> > Total: 3 [ X GB ] / in use 3
> >
> > It seems to be that vgreduce is what I want in order to start over,
> > but running this in test mode with -t and --removemissing I see this
> > worrying line:
> > Removing LV Home from VG
> >
> > and the line I want
> > Removing PV with UUID {correct UUID}
> >
> > Am I on the right track?
> >
> > TIA
-- 
Jeff Macdonald
Ayer, MA