[linux-lvm] Severe problem: data lost while adding a partition

[linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Hello all,

I write to you with a rather grave problem. I have a small LVM setup at 
home, consisting of 4 partitions. These were created by the Mandrake 8.2 
  installation system. After deciding to upgrade the system to Mandrake 
9.0, I found out that I had another partition lying around which was 
also prepared for LVM use. I had meant for that disc to use later on in 
  a different scheme for my /usr partition but never got around to do it.
However, during installation I decided to add it to the LVM. The idea 
was that I would extend the FS later (of course, I was not going to 
involve this LVM setup in the rest of the installation, I would do all 
that manually.)

But as you probably guessed, something went horribly wrong during 
install time and my LVM setup is properly hosed. I wanted to re-create 
the setup, but alas: I forgot which was the disk that I added.

The name of the LV (there was only 1) was home, the disks involved were 
/dev/hda1, /dev/hda[4-6].

Output of pvscan:
----------------------------------------------------------------------
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
associated to an unknown VG (run vgscan)
pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]

-----------------------------------------------------------------------

output of vgscan:
-----------------------------------------------------------------------
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

-----------------------------------------------------------------------

output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
-----------------------------------------------------------------------
pvdisplay -- getting physical volume size
--- Physical volume ---
PV Name               /dev/ide/host0/bus0/target0/lun0/part1
VG Name               home
PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
PV#                   1
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              99
Free PE               0
Allocated PE          99
PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
-----------------------------------------------------------------------

If you need any further information, please let me know!
I do hope you can help me with this, since I stand to loose a lot of 
personal data, of which exists no backup (of course, you guys probably 
hear this all the time).

Best regards,

Sander Alberink

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Heinz J . Mauelshagen]

Sander,

can you tell what you mean with
'...something went horribly wron during install...' ?

Any particular messages which can help analyzing this ?

If you don't have any, take your most recent LVM metedata from the archive 
(/etc/lvconf/ ; you've got a backup, right ?), figure out disks used as PVs
with "vgcfgrestore -ll ..." and run "pvcreate -ff ..." and vgcfgrestore
on all of them. The archive you use shall _not_ include the recently added
disk.

Regards,
Heinz    -- The LVM Guy --


On Sun, Feb 02, 2003 at 01:14:28AM +0100, Sander Alberink wrote:
> Hello all,
> 
> I write to you with a rather grave problem. I have a small LVM setup at 
> home, consisting of 4 partitions. These were created by the Mandrake 8.2 
>   installation system. After deciding to upgrade the system to Mandrake 
> 9.0, I found out that I had another partition lying around which was 
> also prepared for LVM use. I had meant for that disc to use later on in 
>   a different scheme for my /usr partition but never got around to do it.
> However, during installation I decided to add it to the LVM. The idea 
> was that I would extend the FS later (of course, I was not going to 
> involve this LVM setup in the rest of the installation, I would do all 
> that manually.)
> 
> But as you probably guessed, something went horribly wrong during 
> install time and my LVM setup is properly hosed. I wanted to re-create 
> the setup, but alas: I forgot which was the disk that I added.
> 
> The name of the LV (there was only 1) was home, the disks involved were 
> /dev/hda1, /dev/hda[4-6].
> 
> Output of pvscan:
> ----------------------------------------------------------------------
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- walking through all physical volumes found
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]
> 
> -----------------------------------------------------------------------
> 
> output of vgscan:
> -----------------------------------------------------------------------
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> group
> 
> -----------------------------------------------------------------------
> 
> output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
> -----------------------------------------------------------------------
> pvdisplay -- getting physical volume size
> --- Physical volume ---
> PV Name               /dev/ide/host0/bus0/target0/lun0/part1
> VG Name               home
> PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
> PV#                   1
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              99
> Free PE               0
> Allocated PE          99
> PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
> -----------------------------------------------------------------------
> 
> If you need any further information, please let me know!
> I do hope you can help me with this, since I stand to loose a lot of 
> personal data, of which exists no backup (of course, you guys probably 
> hear this all the time).
> 
> Best regards,
> 
> Sander Alberink
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Heinz,

Thanks for your reply, but I have some more questions....

>can you tell what you mean with
>'...something went horribly wron during install...' ?
>
>Any particular messages which can help analyzing this ?
>  
>
Well, actually no real error messages, just a GUI installer that didn't 
do what I expected it to do. However, the LVM was hosed already at the 
time I realized something was wrong

>If you don't have any, take your most recent LVM metedata from the archive 
>(/etc/lvconf/ ; you've got a backup, right ?), figure out disks used as PVs
>with "vgcfgrestore -ll ..." and run "pvcreate -ff ..." and vgcfgresto
>on all of them. The archive you use shall _not_ include the recently added
>disk.
>
Well, guess what? The LVM used in Mandrake doesn't make a backup copy. 
And of course I hadn't executed it myself.... So as such I cannot 
restore the exact configuration. Is pvcreate still the way to go then? 
Please advice!

Best regards,

Sander

>
>Regards,
>Heinz    -- The LVM Guy --
>
>
>On Sun, Feb 02, 2003 at 01:14:28AM +0100, Sander Alberink wrote:
>  
>
>>Hello all,
>>
>>I write to you with a rather grave problem. I have a small LVM setup at 
>>home, consisting of 4 partitions. These were created by the Mandrake 8.2 
>>  installation system. After deciding to upgrade the system to Mandrake 
>>9.0, I found out that I had another partition lying around which was 
>>also prepared for LVM use. I had meant for that disc to use later on in 
>>  a different scheme for my /usr partition but never got around to do it.
>>However, during installation I decided to add it to the LVM. The idea 
>>was that I would extend the FS later (of course, I was not going to 
>>involve this LVM setup in the rest of the installation, I would do all 
>>that manually.)
>>
>>But as you probably guessed, something went horribly wrong during 
>>install time and my LVM setup is properly hosed. I wanted to re-create 
>>the setup, but alas: I forgot which was the disk that I added.
>>
>>The name of the LV (there was only 1) was home, the disks involved were 
>>/dev/hda1, /dev/hda[4-6].
>>
>>Output of pvscan:
>>----------------------------------------------------------------------
>>pvscan -- reading all physical volumes (this may take a while...)
>>pvscan -- walking through all physical volumes found
>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
>>associated to an unknown VG (run vgscan)
>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
>>associated to an unknown VG (run vgscan)
>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
>>associated to an unknown VG (run vgscan)
>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
>>associated to an unknown VG (run vgscan)
>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
>>associated to an unknown VG (run vgscan)
>>pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]
>>
>>-----------------------------------------------------------------------
>>
>>output of vgscan:
>>-----------------------------------------------------------------------
>>vgscan -- reading all physical volumes (this may take a while...)
>>vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
>>vgscan -- WARNING: This program does not do a VGDA backup of your volume 
>>group
>>
>>-----------------------------------------------------------------------
>>
>>output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
>>-----------------------------------------------------------------------
>>pvdisplay -- getting physical volume size
>>--- Physical volume ---
>>PV Name               /dev/ide/host0/bus0/target0/lun0/part1
>>VG Name               home
>>PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
>>PV#                   1
>>PV Status             NOT available
>>Allocatable           yes (but full)
>>Cur LV                1
>>PE Size (KByte)       4096
>>Total PE              99
>>Free PE               0
>>Allocated PE          99
>>PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
>>-----------------------------------------------------------------------
>>
>>If you need any further information, please let me know!
>>I do hope you can help me with this, since I stand to loose a lot of 
>>personal data, of which exists no backup (of course, you guys probably 
>>hear this all the time).
>>
>>Best regards,
>>
>>Sander Alberink
>>
>>
>>_______________________________________________
>>linux-lvm mailing list
>>linux-lvm@sistina.com
>>http://lists.sistina.com/mailman/listinfo/linux-lvm
>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>    
>>
>
>*** Software bugs are stupid.
>    Nevertheless it needs not so stupid people to solve them ***
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>Heinz Mauelshagen                                 Sistina Software Inc.
>Senior Consultant/Developer                       Am Sonnenhang 11
>                                                  56242 Marienrachdorf
>                                                  Germany
>Mauelshagen@Sistina.com                           +49 2626 141200
>                                                       FAX 924446
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>  
>

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Heinz J . Mauelshagen]

Sander,

if you want to redo from scratch, "pvcreate -ff" the disks/partitions
you want to use with LVM. Partitions need to have type 0x8E (Linux LVM).


Regards,
Heinz    -- The LVM Guy --


On Thu, Feb 06, 2003 at 10:48:27PM +0100, Sander Alberink wrote:
> Heinz,
> 
> Thanks for your reply, but I have some more questions....
> 
> >can you tell what you mean with
> >'...something went horribly wron during install...' ?
> >
> >Any particular messages which can help analyzing this ?
> >  
> >
> Well, actually no real error messages, just a GUI installer that didn't 
> do what I expected it to do. However, the LVM was hosed already at the 
> time I realized something was wrong
> 
> >If you don't have any, take your most recent LVM metedata from the archive 
> >(/etc/lvconf/ ; you've got a backup, right ?), figure out disks used as PVs
> >with "vgcfgrestore -ll ..." and run "pvcreate -ff ..." and vgcfgresto
> >on all of them. The archive you use shall _not_ include the recently added
> >disk.
> >
> Well, guess what? The LVM used in Mandrake doesn't make a backup copy. 
> And of course I hadn't executed it myself.... So as such I cannot 
> restore the exact configuration. Is pvcreate still the way to go then? 
> Please advice!
> 
> Best regards,
> 
> Sander
> 
> >
> >Regards,
> >Heinz    -- The LVM Guy --
> >
> >
> >On Sun, Feb 02, 2003 at 01:14:28AM +0100, Sander Alberink wrote:
> >  
> >
> >>Hello all,
> >>
> >>I write to you with a rather grave problem. I have a small LVM setup at 
> >>home, consisting of 4 partitions. These were created by the Mandrake 8.2 
> >>  installation system. After deciding to upgrade the system to Mandrake 
> >>9.0, I found out that I had another partition lying around which was 
> >>also prepared for LVM use. I had meant for that disc to use later on in 
> >>  a different scheme for my /usr partition but never got around to do it.
> >>However, during installation I decided to add it to the LVM. The idea 
> >>was that I would extend the FS later (of course, I was not going to 
> >>involve this LVM setup in the rest of the installation, I would do all 
> >>that manually.)
> >>
> >>But as you probably guessed, something went horribly wrong during 
> >>install time and my LVM setup is properly hosed. I wanted to re-create 
> >>the setup, but alas: I forgot which was the disk that I added.
> >>
> >>The name of the LV (there was only 1) was home, the disks involved were 
> >>/dev/hda1, /dev/hda[4-6].
> >>
> >>Output of pvscan:
> >>----------------------------------------------------------------------
> >>pvscan -- reading all physical volumes (this may take a while...)
> >>pvscan -- walking through all physical volumes found
> >>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
> >>associated to an unknown VG (run vgscan)
> >>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
> >>associated to an unknown VG (run vgscan)
> >>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
> >>associated to an unknown VG (run vgscan)
> >>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
> >>associated to an unknown VG (run vgscan)
> >>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
> >>associated to an unknown VG (run vgscan)
> >>pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]
> >>
> >>-----------------------------------------------------------------------
> >>
> >>output of vgscan:
> >>-----------------------------------------------------------------------
> >>vgscan -- reading all physical volumes (this may take a while...)
> >>vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> >>vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> >>group
> >>
> >>-----------------------------------------------------------------------
> >>
> >>output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
> >>-----------------------------------------------------------------------
> >>pvdisplay -- getting physical volume size
> >>--- Physical volume ---
> >>PV Name               /dev/ide/host0/bus0/target0/lun0/part1
> >>VG Name               home
> >>PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
> >>PV#                   1
> >>PV Status             NOT available
> >>Allocatable           yes (but full)
> >>Cur LV                1
> >>PE Size (KByte)       4096
> >>Total PE              99
> >>Free PE               0
> >>Allocated PE          99
> >>PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
> >>-----------------------------------------------------------------------
> >>
> >>If you need any further information, please let me know!
> >>I do hope you can help me with this, since I stand to loose a lot of 
> >>personal data, of which exists no backup (of course, you guys probably 
> >>hear this all the time).
> >>
> >>Best regards,
> >>
> >>Sander Alberink
> >>
> >>
> >>_______________________________________________
> >>linux-lvm mailing list
> >>linux-lvm@sistina.com
> >>http://lists.sistina.com/mailman/listinfo/linux-lvm
> >>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>    
> >>
> >
> >*** Software bugs are stupid.
> >    Nevertheless it needs not so stupid people to solve them ***
> >
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >Heinz Mauelshagen                                 Sistina Software Inc.
> >Senior Consultant/Developer                       Am Sonnenhang 11
> >                                                  56242 Marienrachdorf
> >                                                  Germany
> >Mauelshagen@Sistina.com                           +49 2626 141200
> >                                                       FAX 924446
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >_______________________________________________
> >linux-lvm mailing list
> >linux-lvm@sistina.com
> >http://lists.sistina.com/mailman/listinfo/linux-lvm
> >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >  
> >
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Heinz, all,

I really appreciate your help in this. However, I am rather reluctant to 
dive in and be hasty in my commands. I really don't want to destroy my 
data....
As I understand it, pvcreate -ff would re-initialize the physical 
volume. As I understand it, I will have to add them to a volume group 
again. But will the filesystem still be intact after that then?

Sorry if this sound like a beginner question to you. It very well might 
be, but I'd rather be careful....

Best regards,

Sander

>Sander,
>
>if you want to redo from scratch, "pvcreate -ff" the disks/partitions
>you want to use with LVM. Partitions need to have type 0x8E (Linux LVM).
>
>
>Regards,
>Heinz    -- The LVM Guy --
>
>
>On Thu, Feb 06, 2003 at 10:48:27PM +0100, Sander Alberink wrote:
>  
>
>>Heinz,
>>
>>Thanks for your reply, but I have some more questions....
>>
>>    
>>
>>>can you tell what you mean with
>>>'...something went horribly wron during install...' ?
>>>
>>>Any particular messages which can help analyzing this ?
>>> 
>>>
>>>      
>>>
>>Well, actually no real error messages, just a GUI installer that didn't 
>>do what I expected it to do. However, the LVM was hosed already at the 
>>time I realized something was wrong
>>
>>    
>>
>>>If you don't have any, take your most recent LVM metedata from the archive 
>>>(/etc/lvconf/ ; you've got a backup, right ?), figure out disks used as PVs
>>>with "vgcfgrestore -ll ..." and run "pvcreate -ff ..." and vgcfgresto
>>>on all of them. The archive you use shall _not_ include the recently added
>>>disk.
>>>
>>>      
>>>
>>Well, guess what? The LVM used in Mandrake doesn't make a backup copy. 
>>And of course I hadn't executed it myself.... So as such I cannot 
>>restore the exact configuration. Is pvcreate still the way to go then? 
>>Please advice!
>>
>>Best regards,
>>
>>Sander
>>
>>    
>>
>>>Regards,
>>>Heinz    -- The LVM Guy --
>>>
>>>
>>>On Sun, Feb 02, 2003 at 01:14:28AM +0100, Sander Alberink wrote:
>>> 
>>>
>>>      
>>>
>>>>Hello all,
>>>>
>>>>I write to you with a rather grave problem. I have a small LVM setup at 
>>>>home, consisting of 4 partitions. These were created by the Mandrake 8.2 
>>>> installation system. After deciding to upgrade the system to Mandrake 
>>>>9.0, I found out that I had another partition lying around which was 
>>>>also prepared for LVM use. I had meant for that disc to use later on in 
>>>> a different scheme for my /usr partition but never got around to do it.
>>>>However, during installation I decided to add it to the LVM. The idea 
>>>>was that I would extend the FS later (of course, I was not going to 
>>>>involve this LVM setup in the rest of the installation, I would do all 
>>>>that manually.)
>>>>
>>>>But as you probably guessed, something went horribly wrong during 
>>>>install time and my LVM setup is properly hosed. I wanted to re-create 
>>>>the setup, but alas: I forgot which was the disk that I added.
>>>>
>>>>The name of the LV (there was only 1) was home, the disks involved were 
>>>>/dev/hda1, /dev/hda[4-6].
>>>>
>>>>Output of pvscan:
>>>>----------------------------------------------------------------------
>>>>pvscan -- reading all physical volumes (this may take a while...)
>>>>pvscan -- walking through all physical volumes found
>>>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
>>>>associated to an unknown VG (run vgscan)
>>>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
>>>>associated to an unknown VG (run vgscan)
>>>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
>>>>associated to an unknown VG (run vgscan)
>>>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
>>>>associated to an unknown VG (run vgscan)
>>>>pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
>>>>associated to an unknown VG (run vgscan)
>>>>pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]
>>>>
>>>>-----------------------------------------------------------------------
>>>>
>>>>output of vgscan:
>>>>-----------------------------------------------------------------------
>>>>vgscan -- reading all physical volumes (this may take a while...)
>>>>vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
>>>>vgscan -- WARNING: This program does not do a VGDA backup of your volume 
>>>>group
>>>>
>>>>-----------------------------------------------------------------------
>>>>
>>>>output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
>>>>-----------------------------------------------------------------------
>>>>pvdisplay -- getting physical volume size
>>>>--- Physical volume ---
>>>>PV Name               /dev/ide/host0/bus0/target0/lun0/part1
>>>>VG Name               home
>>>>PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
>>>>PV#                   1
>>>>PV Status             NOT available
>>>>Allocatable           yes (but full)
>>>>Cur LV                1
>>>>PE Size (KByte)       4096
>>>>Total PE              99
>>>>Free PE               0
>>>>Allocated PE          99
>>>>PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
>>>>-----------------------------------------------------------------------
>>>>
>>>>If you need any further information, please let me know!
>>>>I do hope you can help me with this, since I stand to loose a lot of 
>>>>personal data, of which exists no backup (of course, you guys probably 
>>>>hear this all the time).
>>>>
>>>>Best regards,
>>>>
>>>>Sander Alberink
>>>>        
>>>>

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Steven Lembark]

-- Sander Alberink <alberink@stamppot.demon.nl>

> Heinz, all,
>
> I really appreciate your help in this. However, I am rather reluctant to
> dive in and be hasty in my commands. I really don't want to destroy my
> data.... As I understand it, pvcreate -ff would re-initialize the
> physical volume. As I understand it, I will have to add them to a volume
> group again. But will the filesystem still be intact after that then?
>
> Sorry if this sound like a beginner question to you. It very well might
> be, but I'd rather be careful....

Thing to understand is that LVM commands update a small
header on the phyiscal volume. You can munge the LVM
portion without touching your data at all. In this case
the data has no way of knowing that anything happend to
the LVM portion of life: they live in entirely different
parts of the disk drive.


--
Steven Lembark                               2930 W. Palmer
Workhorse Computing                       Chicago, IL 60647
                                            +1 773 252 1080

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Hi all,

Thanks for the reply. At the moment I have re-initialized the PV's via 
pvcreate -ff. However, trying to reconstruct a new volume group yields 
me the following output:

# vgcreate -v home /dev/hda[1,4,6,7]
vgcreate -- checking volume group name
vgcreate -- checking volume group directory existence
vgcreate -- locking logical volume manager
vgcreate -- checking volume group "home" existence
vgcreate -- counting all existing volume groups
vgcreate -- reading all physical volume data from disks
vgcreate -- checking if all given physical volumes in command line are new
vgcreate -- checking physical volumes name "/dev/hda1"
vgcreate -- checking physical volumes name "/dev/hda4"
vgcreate -- checking physical volumes name "/dev/hda6"
vgcreate -- checking physical volumes name "/dev/hda7"
vgcreate -- no valid physical volumes in command line
#

So apparently something is not OK. But what can that be? Any pointers 
would be appreciated!

>> I really appreciate your help in this. However, I am rather reluctant to
>> dive in and be hasty in my commands. I really don't want to destroy my
>> data.... As I understand it, pvcreate -ff would re-initialize the
>> physical volume. As I understand it, I will have to add them to a volume
>> group again. But will the filesystem still be intact after that then?
>>
>> Sorry if this sound like a beginner question to you. It very well might
>> be, but I'd rather be careful....
>
>
> Thing to understand is that LVM commands update a small
> header on the phyiscal volume. You can munge the LVM
> portion without touching your data at all. In this case
> the data has no way of knowing that anything happend to
> the LVM portion of life: they live in entirely different
> parts of the disk drive. 


Best regards,

Sander Alberink

Re: [linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Hello all,

Sorry to reply to myself, but I really am stuck on this one. Any 
pointers would be much appreciated...

I have gotten the vgcreate to work (this was caused by me now using 
devfs (so I need to supply DevFS filenames). I also executed an lvcreate 
-l 399 (which was the maximum number of PE's available) on the resulting 
volume group. However, I cannot mount the resulting logical volume.
It used to contain a reiserfs filesystem, a reiserfsck --check yields no 
errors, but I am unable to mount the filesystem.
I am getting rather lost now.....

Hope someone can help!

Best regards,

Sander

Sander Alberink wrote:

> Hi all,
>
> Thanks for the reply. At the moment I have re-initialized the PV's via 
> pvcreate -ff. However, trying to reconstruct a new volume group yields 
> me the following output:
>
> # vgcreate -v home /dev/hda[1,4,6,7]
> vgcreate -- checking volume group name
> vgcreate -- checking volume group directory existence
> vgcreate -- locking logical volume manager
> vgcreate -- checking volume group "home" existence
> vgcreate -- counting all existing volume groups
> vgcreate -- reading all physical volume data from disks
> vgcreate -- checking if all given physical volumes in command line are 
> new
> vgcreate -- checking physical volumes name "/dev/hda1"
> vgcreate -- checking physical volumes name "/dev/hda4"
> vgcreate -- checking physical volumes name "/dev/hda6"
> vgcreate -- checking physical volumes name "/dev/hda7"
> vgcreate -- no valid physical volumes in command line
> #
>
> So apparently something is not OK. But what can that be? Any pointers 
> would be appreciated!
>
>>> I really appreciate your help in this. However, I am rather 
>>> reluctant to
>>> dive in and be hasty in my commands. I really don't want to destroy my
>>> data.... As I understand it, pvcreate -ff would re-initialize the
>>> physical volume. As I understand it, I will have to add them to a 
>>> volume
>>> group again. But will the filesystem still be intact after that then?
>>>
>>> Sorry if this sound like a beginner question to you. It very well might
>>> be, but I'd rather be careful....
>>
>>
>>
>> Thing to understand is that LVM commands update a small
>> header on the phyiscal volume. You can munge the LVM
>> portion without touching your data at all. In this case
>> the data has no way of knowing that anything happend to
>> the LVM portion of life: they live in entirely different
>> parts of the disk drive. 
>

[linux-lvm] Severe problem: data lost while adding a partition

[Sander Alberink]

Hello all,

I write to you with a rather grave problem. I have a small LVM setup at 
home, consisting of 4 partitions. These were created by the Mandrake 8.2 
  installation system. After deciding to upgrade the system to Mandrake 
9.0, I found out that I had another partition lying around which was 
also prepared for LVM use. I had meant for that disc to use later on in 
  a different scheme for my /usr partition but never got around to do it.
However, during installation I decided to add it to the LVM. The idea 
was that I would extend the FS later (of course, I was not going to 
involve this LVM setup in the rest of the installation, I would do all 
that manually.)

But as you probably guessed, something went horribly wrong during 
install time and my LVM setup is properly hosed. I wanted to re-create 
the setup, but alas: I forgot which was the disk that I added.

The name of the LV (there was only 1) was home, the disks involved were 
/dev/hda1, /dev/hda[4-6].

Output of pvscan:
----------------------------------------------------------------------
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
associated to an unknown VG (run vgscan)
pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]

-----------------------------------------------------------------------

output of vgscan:
-----------------------------------------------------------------------
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

-----------------------------------------------------------------------

output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
-----------------------------------------------------------------------
pvdisplay -- getting physical volume size
--- Physical volume ---
PV Name               /dev/ide/host0/bus0/target0/lun0/part1
VG Name               home
PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
PV#                   1
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              99
Free PE               0
Allocated PE          99
PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
-----------------------------------------------------------------------

If you need any further information, please let me know!
I do hope you can help me with this, since I stand to loose a lot of 
personal data, of which exists no backup (of course, you guys probably 
hear this all the time).

Best regards,

Sander Alberink