Re: recommendations on how to recover a corrupted, LVM-based hard drive?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Feb 12, 2014, at 1:42 PM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:

> On Wed, 12 Feb 2014, murph wrote:
> 
>> Try the poorly-named "testdisk" to see if it can get any of the old
>> partition information.  I've had good luck with recovering
>> accidentally-partitioned disks.
> 
>  so here's the current output from that utility after it finished a
> lengthy scan of the (corrupted) drive:
> 
> Disk /dev/sdb - 750 GB / 698 GiB - CHS 91201 255 63
>     Partition               Start        End    Size in sectors
>> FAT16 >32M               0  32 33    12  93 17     196608 [boot]
>   Linux                    0  32 33 45105  20 35  724611072
>   Linux                   12  93 18   216 183 31    3282944 [rootfs]
> * Linux                48416 239 16 48612 191 27    3145728
> P Linux                70007  45 55 70008  50 58      16384
> P Linux                86771 149 35 86779 190  3     131072
> L Linux Swap           89115 185 31 91201  52 51   33503232

Huh. Is this a recent version of testdisk? Or has it been intentionally switched to CHS mode? I've only ever seen recent versions report in LBA, which is a lot easier to figure out about where the obliteration with dd occurred.

>  now, the "boot" and "rootfs" entries would correspond to the 2G
> bootable SD card image that was written over the beginning of the
> disk, and i would *guess* that the sizable "Linux" partition is the
> home partition/LV that is the object of recovery, but i have no idea
> what to do next or whether "testdisk" has the capability of
> recognizing logical volumes.

Without having looked at the code, if it doesn't find the PV metadata I don't think it's going to find the VG metadata either. I'm thinking it's finding a backup ext superblock from this:

>   Linux                    0  32 33 45105  20 35  724611072

What you'll do is have testdisk copy files out of this, onto separate storage. Some files will probably be hosed, and I can't say whether testdisk will inform you of their viability in advance.


> 
>  oh, crap, i hit "Quit" to back out of a menu and this utility just
> cleared all those results, so i have to do the scan again. grrrrr …

Make sure it's v6.14 before going to the trouble again.


Chris Murphy
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux