Differences

This shows you the differences between two versions of the page.

--- unix:lvm_recovery [2013/05/27 13:56]
robm [... 2 weeks later]
+++ unix:lvm_recovery [2013/08/20 22:54] (current)
@@ Line 505: / Line 505: @@
 Success!
-**Update**: I ended up writing a Python script, [[https://github.com/meermanr/ext3_recovery|find_ext3.py]], to help me locate ''ext3'' superblocks, and automatically check their validity using ''dumpe2fs''.
+**Update**: I ended up writing a Python script, [[https://github.com/meermanr/ext3_recovery|find_ext3.py]], to help me locate ''ext3'' superblocks, and automatically check their validity using ''dumpe2fs''. This showed that the most common file-system origin is actually _before_ the start of the LVM logical volume:
+<code>
+root@skuld:/home/meermanr/projects/find_ext3# cut -d' ' -f9- store_vg-store_lv.find_ext3.log | sort | uniq
+ -c | sort -rn | head
+origin -134282240
+origin -134514176
+origin 8382976
+origin 8268288
+origin 8256000
+origin 8215040
+origin 8145408
+origin 8133120
+origin 8043008
+origin 8030720
+</code>
+From this I conclude that my original (working) installation was not actually using the Logical Volume! This may explain why updating Ubuntu to a version which has LVM support by default made my system unable to find the file-system.
+So from this point on I'll ignore the Logical Volumes in my disk image (''store_vg/store_lv''), and instead look for a file-system in the raw image.
 ====== Getting my data back ======

RobMeerman.co.uk