Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] LVM Incorrect metadata area header checksum
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
kevintshaver
n00b
n00b


Joined: 14 Feb 2006
Posts: 49

PostPosted: Sun Mar 29, 2009 4:54 pm    Post subject: [solved] LVM Incorrect metadata area header checksum Reply with quote

I need some help on this new LVM error I've been getting. Normally, I log in and run
Code:
vgscan
and
Code:
vgchange -a y
to make /dev/vg0 available. This morning I did the same thing and got some errors.

Code:
server ~ # vgscan
  Reading all physical volumes.  This may take a while...
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Volume group "vg0" inconsistent
  Incorrect metadata area header checksum
  WARNING: Inconsistent metadata found for VG vg0 - updating to use version 7
  Incorrect metadata area header checksum
  Automatic metadata correction failed


Some other things that might help:

Code:
server ~ # vgcfgrestore vg0
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Restore failed.


Code:
server ~ # vgdisplay
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  WARNING: Volume group "vg0" inconsistent
  --- Volume group ---
  VG Name               vg0
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  7
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               2.73 TB
  PE Size               4.00 MB
  Total PE              715400
  Alloc PE / Size       486400 / 1.86 TB
  Free  PE / Size       229000 / 894.53 GB
  VG UUID               HwLcZs-65mL-uRSz-B55c-zjb8-FlH4-9qR5bl


Code:
server ~ # pvdisplay
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  WARNING: Volume Group vg0 is not consistent
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  --- Physical volume ---
  PV Name               /dev/dm-0
  VG Name               vg0
  PV Size               2.73 TB / not usable 4.00 KB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              715400
  Free PE               229000
  Allocated PE          486400
  PV UUID               TncGxJ-53Cj-FEqT-WVwd-pv96-5zRO-30AH0e


Code:
server ~ # fdisk -l

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x904d904e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           9       72261   83  Linux
/dev/sda2              10         265     2056320   82  Linux swap / Solaris
/dev/sda3             266       24321   193229820   83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x605ca212

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x7bc1e74a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3c145983

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1      121601   976760001   fd  Linux raid autodetect


Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x88d53d18

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/md0: 3000.6 GB, 3000606523392 bytes
2 heads, 4 sectors/track, 732569952 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x08040000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/dm-0: 3000.6 GB, 3000605470720 bytes
255 heads, 63 sectors/track, 364802 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table


Could it have something to do with the /dev/md0 and /dev/dm-0 devices? What's the difference between these two?

Previously, the lvm.conf was working fine, but I modified the filter because I see this error can sometimes be caused by scanning non-LVM devices. My new filter line is:

Code:
filter = [ "a|^/dev/mapper/vault$|", "r/.*/" ]


I'm stuck. Thanks in advance.


Last edited by kevintshaver on Thu Apr 02, 2009 1:58 am; edited 1 time in total
Back to top
View user's profile Send private message
kevintshaver
n00b
n00b


Joined: 14 Feb 2006
Posts: 49

PostPosted: Wed Apr 01, 2009 6:15 pm    Post subject: Reply with quote

I also noticed these lines in lvdisplay if it helps.

Code:
server ~ # lvdisplay
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Volume group "vg0" inconsistent
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  WARNING: Inconsistent metadata found for VG vg0 - updating to use version 7
  Incorrect metadata area header checksum
  Automatic metadata correction failed
  Internal error: Volume Group vg0 was not unlocked
  Device '/dev/dm-0' has been left open.
  Device '/dev/dm-0' has been left open.
  Device '/dev/dm-0' has been left open.
Back to top
View user's profile Send private message
kevintshaver
n00b
n00b


Joined: 14 Feb 2006
Posts: 49

PostPosted: Thu Apr 02, 2009 2:01 am    Post subject: Reply with quote

Here's the fix. It seems a bit risky but I didn't end up with any lost data.

Code:
pvcreate -ff -u TncGxJ-53Cj-FEqT-WVwd-pv96-5zRO-30AH0e --restorefile /etc/lvm/backup/vg0 /dev/mapper/vault
vgcfgrestore vg0


change the uuid after -u to the pv0 uuid in /etc/lvm/backup/vg0 and change vg0 to your volume group name
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum