LVM2 recovery ?
Posted: 09 Jun 2012, 20:53
I pulled an old amd barton box out of storage a few weeks ago, it wouldnt boot.
So I tried to upgrade the Fedora 11 installed there, that fell over (some python exceptions iirc),
so I tried a fresh install.
while running installer, I foolishly chose to include all the LVM2 partitions in the upgrade,
rather than just one, without reading the fine print - so I fear Ive trashed the contents of
all those other partitions. I aborted the process (dont remember how - whether it was
orderly ^C or panic'd reset button). At that point I just stopped, figuring Id at least not
do any further harm..
So, I pulled a copy of RecoveryIsPossible, and ran TestDisk 6.14-WIP.
I plugged in USB drive, told testdisk to write the log there, prog ran for a while,
and wrote a 4gb image.dd file then paused/stopped) with:
No space left for the file image.
> [Ok]
Ive tried several times, USB drive has 86G free, so its not whats full...
the 4GB images (image.dd in 2 different directories) are both
4294967295 bytes long, which is exactly 4*2^30-1, which makes me
suspicious of the LARGE_FILES setting on the kernel or executable
(or maybe its the damn fat partition on the USB drive)
So, Im thinking that a FAT limitation is the problem, not the kernel or program.
But it does seem that TestDisk could recognize the limits imposed by the
destination filesystem..
Have I missed something ?
(partition is
So I tried to upgrade the Fedora 11 installed there, that fell over (some python exceptions iirc),
so I tried a fresh install.
while running installer, I foolishly chose to include all the LVM2 partitions in the upgrade,
rather than just one, without reading the fine print - so I fear Ive trashed the contents of
all those other partitions. I aborted the process (dont remember how - whether it was
orderly ^C or panic'd reset button). At that point I just stopped, figuring Id at least not
do any further harm..
So, I pulled a copy of RecoveryIsPossible, and ran TestDisk 6.14-WIP.
I plugged in USB drive, told testdisk to write the log there, prog ran for a while,
and wrote a 4gb image.dd file then paused/stopped) with:
No space left for the file image.
> [Ok]
Ive tried several times, USB drive has 86G free, so its not whats full...
the 4GB images (image.dd in 2 different directories) are both
4294967295 bytes long, which is exactly 4*2^30-1, which makes me
suspicious of the LARGE_FILES setting on the kernel or executable
(or maybe its the damn fat partition on the USB drive)
So, Im thinking that a FAT limitation is the problem, not the kernel or program.
But it does seem that TestDisk could recognize the limits imposed by the
destination filesystem..
Have I missed something ?
(partition is