Corrupted LVM partition - hard disk seems too small error?

Using TestDisk to undelete files
Post Reply
Message
Author
avggeek
Posts: 3
Joined: 15 Sep 2013, 04:04

Corrupted LVM partition - hard disk seems too small error?

#1 Post by avggeek » 15 Sep 2013, 04:15

Hi,

I had a LVM partition that became corrupted and fell out of the LVM array. The files on it are no longer visible when I use ls or any file manager - so I have not added it back to the LVM array.

I have tried scanning it using TestDisk but get the following messages:

Code: Select all

Disk /dev/sdf1 - 2000 GB / 1863 GiB - CHS 243202 255 63

The harddisk (2000 GB / 1863 GiB) seems too small! (< 2010 GB / 1872 GiB)
Check the harddisk size: HD jumpers settings, BIOS detection...

No file found, filesystem may be damaged.
I am able to view the first level folders after Deep Search, but trying to view the contents does not work. I have cross checked against Gparted and it seems to confirm the Cylinder/Head/Sector information:

Code: Select all

Gparted output:
file system: lvm2
partition table: msdos
heads: 255
sector: 63
cylinders: 243201
This is using TestDisk 6.13 on Ubuntu 12.04 LTS. Can anyone suggest how to proceed further?

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 3403
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Corrupted LVM partition - hard disk seems too small erro

#2 Post by cgrenier » 27 Sep 2013, 12:39

Can you run pvck on this partition ?
What is the result of "pvdisplay-a" ?

avggeek
Posts: 3
Joined: 15 Sep 2013, 04:04

Re: Corrupted LVM partition - hard disk seems too small erro

#3 Post by avggeek » 28 Sep 2013, 03:19

Output of pvdisplay:

Code: Select all

  --- Physical volume ---
  PV Name               /dev/sdf1
  VG Name               LCARS
  PV Size               1.82 TiB / not usable 16.00 MiB
  Allocatable           yes 
  PE Size               16.00 MiB
  Total PE              119232
  Free PE               119232
  Allocated PE          0
  PV UUID               tELEcU-VREJ-HKdg-C6DZ-rtCv-GmvI-uK7vI5
Output of pvck -d -v:

Code: Select all

    Scanning /dev/sdf1
  Found label on /dev/sdf1, sector 1, type=LVM2 001
  Found text metadata area: offset=4096, size=192512
    Found LVM2 metadata record at offset=6656, size=2048, offset2=0 size2=0

User avatar
cgrenier
Site Admin
Posts: 3403
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Corrupted LVM partition - hard disk seems too small erro

#4 Post by cgrenier » 16 Oct 2013, 19:57

It looks good, continue with

Code: Select all

vgscan -v
vgck -v
lvscan -v

avggeek
Posts: 3
Joined: 15 Sep 2013, 04:04

Re: Corrupted LVM partition - hard disk seems too small erro

#5 Post by avggeek » 25 Oct 2013, 02:34

cgrenier wrote:It looks good, continue with

Code: Select all

vgscan -v
vgck -v
lvscan -v
Output from the three commands:

Code: Select all

 sudo vgscan -v
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
  Reading all physical volumes.  This may take a while...
    Finding all volume groups
    Finding volume group "LCARS"
  Found volume group "LCARS" using metadata type lvm2

Code: Select all

 sudo vgck -v                                                                                                                                 
    Finding all volume groups
    Finding volume group "LCARS"

Code: Select all

% sudo lvscan -v                                                                                                                                
    Finding all logical volumes
  ACTIVE            '/dev/LCARS/music' [200.00 GiB] inherit
  ACTIVE            '/dev/LCARS/movies' [1.10 TiB] inherit
  ACTIVE            '/dev/LCARS/amanda-holding' [200.00 GiB] inherit
Any suggestions on what I should be doing next?

User avatar
cgrenier
Site Admin
Posts: 3403
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Corrupted LVM partition - hard disk seems too small erro

#6 Post by cgrenier » 27 Oct 2013, 17:29

Run as root the fsck command against each device. You should be able to access this 3 volumes, try to mount them.

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests