Re: Lost LVM data - lost logical volume

[Anton Bizzarri <anton.bizzari@drgit.ca>]

Hi David. I see what you mean. 

So just to confirm, there is no way to recover the logical volume.

FWIW.. I am trying the following 

I recreated the LV with lvcreate. 

Luckily the old LV spanned the 100% the old LVM.

I can now see the LV.

I then ran ext3.fsck to repair /dev/mapper/data

latest errors i get are:

Oct 26 13:07:38 arbor kernel: [349276.552056] EXT3-fs error (device dm-0): ext3_check_descriptors: Block bitmap for group 384 not in group (block 0)!

Oct 26 13:07:38 arbor kernel: [349276.559433] EXT3-fs (dm-0): error: group descriptors corrupted

Then I am running ext3.fsck /dev/dm-0 

and just waiting for it to finish.

FWIW. There are a multitude of reasons why there is no backup in place. In this particular case, there is no SLA to cover the regular backup of 3TB of data. So there is no money available to invest in hardware or services to backup the data. The agreement is try "best effort" to recover data if it goes down.

On Sun, Oct 25, 2015 at 6:44 PM, David Christensen <dpchrist@holgerdanske.com> wrote:

On 10/23/2015 03:56 AM, Anton Bizzarri wrote:

On Thu, Oct 22, 2015 at 9:55 PM, David Christensen <
dpchrist@holgerdanske.com> wrote:

You *do* have a back up of your data, right?

No. There is no backup. Is the data lost because it was a striped volume.?
Its not my server and I never worked on it before. I was not aware it was a
stripe.

Please "reply to list".


RAID0 and no backups?  The owner already decided to lose his data.


If the owner has changed his mind and wants his data back, then I'd take two images of every drive in the server, store one set off-site, and have the owner send the server to a data recovery consultant or shop. In the mean time, now might be an opportune moment to implement a backup system.


David