Adrian Chadd <[email protected]> writes:
> You won't be able to. If you configured them up as a stripe (ie, no
> mirroring) with interleaving every x megabytes on each disk, you'll
> basically end up with a virtual hard disk with "holes" evenly spread out
> across 1/3rd of the image. I don't know of any (easy) tools to recover from
> that.
LVM, by default, is a boring old linear mapping, so he probably has two disks
worth of data ... starting a third (or whatever) of the way through the file
system. So, no superblock on whatever.
> I can think of what I'd write to try and recover -something- but it'd
> involve writing a whole lot of rather hairy looking filesystem-scraping
> code. I'm sure there are tools to do this kind of partial data recovery
> but they're bound to be -very- expensive.
The 'testdisk' package available in Debian, and fully OSS, can do quite a lot
of data recovery without a file system. It just block-scrapes the device.
[...]
> On Wed, Jun 16, 2010, Gerald C.Catling wrote:
>
>> Many thanks to all that responded to try to solve this LVM problem.
>> I could not recover any data from the crashed system. I could not find any
>> method of mounting drive 2 or 3 as individual drives and the system would
>> not create a volume group without the now non-existant first drive. Once
>> again, many thanks. I will have to try RAID 1.
I strongly suggest that using some sort of RAID is absolutely worth the money.
I would also encourage you to try the testdisk tools to recover some of the
content of your device: you will probably get back more than nothing back, and
that might be worth the hassle.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
