Corrupt LVM metadata header after kernel update
3
I'm running Debian Wheezy (Linux wheezy3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux) as an encrypted LVM with hardware raid 1 (Adaptec 6405E) on a supermicro server.
I was encounting the following errors during the the kernel update:
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
done
Here is the output for pvdisplay, vgdisplay, lvdisplay, df, pvs, lvs, vgs:
root@wheezy:~# pvdisplay -v
Scanning for physical volume names
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Physical volume ---
PV Name /dev/dm-0
VG Name wheezy
PV Size 111.37 GiB / not usable 2.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 28510
Free PE 0
Allocated PE 28510
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
root@wheezy:~# vgdisplay -v
Finding all volume groups
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
Finding volume group "wheezy"
--- Volume group ---
VG Name wheezy
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 10
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 111.37 GiB
PE Size 4.00 MiB
Total PE 28510
Alloc PE / Size 28510 / 111.37 GiB
Free PE / Size 0 / 0
VG UUID nq8fye-SpVe-cHrd-AM99-YWdA-7SPp-L3S2Hm
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
--- Physical volumes ---
PV Name /dev/dm-0
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
PV Status allocatable
Total PE / Free PE 28510 / 0
root@wheezy:~# lvdisplay -v
Finding all logical volumes
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
root@wheezy:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 92G 25G 63G 28% /
udev 10M 0 10M 0% /dev
tmpfs 3.2G 1.3M 3.2G 1% /run
/dev/mapper/wheezy-base 92G 25G 63G 28% /
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 6.3G 0 6.3G 0% /run/shm
/dev/sda1 228M 30M 187M 14% /boot
/dev/mapper/wheezy-TMP 11G 172M 10G 2% /tmp
root@wheezy:~# pvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
PV VG Fmt Attr PSize PFree
/dev/dm-0 wheezy lvm2 a-- 111.37g 0
/dev/sda1 lvm2 a-- 243.00m 243.00m
root@wheezy:~# vgs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
VG #PV #LV #SN Attr VSize VFree
wheezy 1 3 0 wz--n- 111.37g 0
root@wheezy:~# lvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
SWAP wheezy -wi-ao-- 7.45g
TMP wheezy -wi-ao-- 10.79g
base wheezy -wi-ao-- 93.13g
What would be the best workaround to fix the corrupted metadata header?
I have an identical machine (same hardware, same partitions, same wheezy installation, same apt sources) running without any problems.
The second machine doesn't have this output in the pvdislay-command:
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
debian linux-kernel lvm
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
add a comment |
3
I'm running Debian Wheezy (Linux wheezy3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux) as an encrypted LVM with hardware raid 1 (Adaptec 6405E) on a supermicro server.
I was encounting the following errors during the the kernel update:
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
done
Here is the output for pvdisplay, vgdisplay, lvdisplay, df, pvs, lvs, vgs:
root@wheezy:~# pvdisplay -v
Scanning for physical volume names
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Physical volume ---
PV Name /dev/dm-0
VG Name wheezy
PV Size 111.37 GiB / not usable 2.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 28510
Free PE 0
Allocated PE 28510
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
root@wheezy:~# vgdisplay -v
Finding all volume groups
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
Finding volume group "wheezy"
--- Volume group ---
VG Name wheezy
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 10
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 111.37 GiB
PE Size 4.00 MiB
Total PE 28510
Alloc PE / Size 28510 / 111.37 GiB
Free PE / Size 0 / 0
VG UUID nq8fye-SpVe-cHrd-AM99-YWdA-7SPp-L3S2Hm
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
--- Physical volumes ---
PV Name /dev/dm-0
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
PV Status allocatable
Total PE / Free PE 28510 / 0
root@wheezy:~# lvdisplay -v
Finding all logical volumes
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
root@wheezy:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 92G 25G 63G 28% /
udev 10M 0 10M 0% /dev
tmpfs 3.2G 1.3M 3.2G 1% /run
/dev/mapper/wheezy-base 92G 25G 63G 28% /
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 6.3G 0 6.3G 0% /run/shm
/dev/sda1 228M 30M 187M 14% /boot
/dev/mapper/wheezy-TMP 11G 172M 10G 2% /tmp
root@wheezy:~# pvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
PV VG Fmt Attr PSize PFree
/dev/dm-0 wheezy lvm2 a-- 111.37g 0
/dev/sda1 lvm2 a-- 243.00m 243.00m
root@wheezy:~# vgs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
VG #PV #LV #SN Attr VSize VFree
wheezy 1 3 0 wz--n- 111.37g 0
root@wheezy:~# lvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
SWAP wheezy -wi-ao-- 7.45g
TMP wheezy -wi-ao-- 10.79g
base wheezy -wi-ao-- 93.13g
What would be the best workaround to fix the corrupted metadata header?
I have an identical machine (same hardware, same partitions, same wheezy installation, same apt sources) running without any problems.
The second machine doesn't have this output in the pvdislay-command:
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
debian linux-kernel lvm
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see thepvdislayreturns a physical drive only
– Athafoud
Apr 8 '15 at 15:04
add a comment |
3
3
3
1
I'm running Debian Wheezy (Linux wheezy3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux) as an encrypted LVM with hardware raid 1 (Adaptec 6405E) on a supermicro server.
I was encounting the following errors during the the kernel update:
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
done
Here is the output for pvdisplay, vgdisplay, lvdisplay, df, pvs, lvs, vgs:
root@wheezy:~# pvdisplay -v
Scanning for physical volume names
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Physical volume ---
PV Name /dev/dm-0
VG Name wheezy
PV Size 111.37 GiB / not usable 2.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 28510
Free PE 0
Allocated PE 28510
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
root@wheezy:~# vgdisplay -v
Finding all volume groups
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
Finding volume group "wheezy"
--- Volume group ---
VG Name wheezy
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 10
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 111.37 GiB
PE Size 4.00 MiB
Total PE 28510
Alloc PE / Size 28510 / 111.37 GiB
Free PE / Size 0 / 0
VG UUID nq8fye-SpVe-cHrd-AM99-YWdA-7SPp-L3S2Hm
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
--- Physical volumes ---
PV Name /dev/dm-0
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
PV Status allocatable
Total PE / Free PE 28510 / 0
root@wheezy:~# lvdisplay -v
Finding all logical volumes
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
root@wheezy:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 92G 25G 63G 28% /
udev 10M 0 10M 0% /dev
tmpfs 3.2G 1.3M 3.2G 1% /run
/dev/mapper/wheezy-base 92G 25G 63G 28% /
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 6.3G 0 6.3G 0% /run/shm
/dev/sda1 228M 30M 187M 14% /boot
/dev/mapper/wheezy-TMP 11G 172M 10G 2% /tmp
root@wheezy:~# pvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
PV VG Fmt Attr PSize PFree
/dev/dm-0 wheezy lvm2 a-- 111.37g 0
/dev/sda1 lvm2 a-- 243.00m 243.00m
root@wheezy:~# vgs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
VG #PV #LV #SN Attr VSize VFree
wheezy 1 3 0 wz--n- 111.37g 0
root@wheezy:~# lvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
SWAP wheezy -wi-ao-- 7.45g
TMP wheezy -wi-ao-- 10.79g
base wheezy -wi-ao-- 93.13g
What would be the best workaround to fix the corrupted metadata header?
I have an identical machine (same hardware, same partitions, same wheezy installation, same apt sources) running without any problems.
The second machine doesn't have this output in the pvdislay-command:
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
debian linux-kernel lvm
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
I'm running Debian Wheezy (Linux wheezy3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux) as an encrypted LVM with hardware raid 1 (Adaptec 6405E) on a supermicro server.
I was encounting the following errors during the the kernel update:
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
error: unknown LVM metadata header.
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
done
Here is the output for pvdisplay, vgdisplay, lvdisplay, df, pvs, lvs, vgs:
root@wheezy:~# pvdisplay -v
Scanning for physical volume names
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Physical volume ---
PV Name /dev/dm-0
VG Name wheezy
PV Size 111.37 GiB / not usable 2.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 28510
Free PE 0
Allocated PE 28510
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
root@wheezy:~# vgdisplay -v
Finding all volume groups
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
Finding volume group "wheezy"
--- Volume group ---
VG Name wheezy
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 10
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 111.37 GiB
PE Size 4.00 MiB
Total PE 28510
Alloc PE / Size 28510 / 111.37 GiB
Free PE / Size 0 / 0
VG UUID nq8fye-SpVe-cHrd-AM99-YWdA-7SPp-L3S2Hm
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
--- Physical volumes ---
PV Name /dev/dm-0
PV UUID 8DEe3m-NaQC-mRia-cMfv-OO2O-Foog-XXTLeU
PV Status allocatable
Total PE / Free PE 28510 / 0
root@wheezy:~# lvdisplay -v
Finding all logical volumes
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
--- Logical volume ---
LV Path /dev/wheezy/SWAP
LV Name SWAP
VG Name wheezy
LV UUID VbC1TX-2Ppz-1003-VFqU-0o0X-otwu-qy5Xam
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:36:55 +0000
LV Status available
# open 2
LV Size 7.45 GiB
Current LE 1907
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/wheezy/TMP
LV Name TMP
VG Name wheezy
LV UUID btQknc-WeBv-q2xA-dhz0-GsqR-G2hn-gKwCh0
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:05 +0000
LV Status available
# open 1
LV Size 10.79 GiB
Current LE 2761
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/wheezy/base
LV Name base
VG Name wheezy
LV UUID dWD7ro-ACQ6-04O2-rKd2-iMCe-HddW-kX1mt6
LV Write Access read/write
LV Creation host, time wheezy, 2014-11-24 16:37:13 +0000
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
root@wheezy:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 92G 25G 63G 28% /
udev 10M 0 10M 0% /dev
tmpfs 3.2G 1.3M 3.2G 1% /run
/dev/mapper/wheezy-base 92G 25G 63G 28% /
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 6.3G 0 6.3G 0% /run/shm
/dev/sda1 228M 30M 187M 14% /boot
/dev/mapper/wheezy-TMP 11G 172M 10G 2% /tmp
root@wheezy:~# pvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
PV VG Fmt Attr PSize PFree
/dev/dm-0 wheezy lvm2 a-- 111.37g 0
/dev/sda1 lvm2 a-- 243.00m 243.00m
root@wheezy:~# vgs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
VG #PV #LV #SN Attr VSize VFree
wheezy 1 3 0 wz--n- 111.37g 0
root@wheezy:~# lvs
Incorrect metadata area header checksum on /dev/sda1 at offset 4096
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
SWAP wheezy -wi-ao-- 7.45g
TMP wheezy -wi-ao-- 10.79g
base wheezy -wi-ao-- 93.13g
What would be the best workaround to fix the corrupted metadata header?
I have an identical machine (same hardware, same partitions, same wheezy installation, same apt sources) running without any problems.
The second machine doesn't have this output in the pvdislay-command:
"/dev/sda1" is a new physical volume of "243.00 MiB"
--- NEW Physical volume ---
PV Name /dev/sda1
VG Name
PV Size 243.00 MiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID fnKsgr-KC2h-inYi-jhli-YFil-edTh-RsRTzK
debian linux-kernel lvm
debian linux-kernel lvm
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
edited Jul 14 '15 at 1:28
Jodka Lemon
2,463534
2,463534
asked Feb 24 '15 at 9:17
heuriheuri
53117
asked Feb 24 '15 at 9:17
heuriheuri
53117
asked Feb 24 '15 at 9:17
heuriheuri
53117
53117
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see thepvdislayreturns a physical drive only
– Athafoud
Apr 8 '15 at 15:04
add a comment |
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see thepvdislayreturns a physical drive only
– Athafoud
Apr 8 '15 at 15:04
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see the
pvdislay returns a physical drive only– Athafoud
Apr 8 '15 at 15:04
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see the
pvdislay returns a physical drive only– Athafoud
Apr 8 '15 at 15:04
add a comment |
1 Answer
1
active
oldest
votes
0
You may have leftover metadata from earlier partitioning. Like a boot partition that is used without LVM but which has LVM metadata because an installer prepared it to be used via LVM.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350
(German) https://debianforum.de/forum/viewtopic.php?f=33&t=154131
Yes this is not a full-blown solution, but progress.
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186536%2fcorrupt-lvm-metadata-header-after-kernel-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
You may have leftover metadata from earlier partitioning. Like a boot partition that is used without LVM but which has LVM metadata because an installer prepared it to be used via LVM.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350
(German) https://debianforum.de/forum/viewtopic.php?f=33&t=154131
Yes this is not a full-blown solution, but progress.
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
add a comment |
0
You may have leftover metadata from earlier partitioning. Like a boot partition that is used without LVM but which has LVM metadata because an installer prepared it to be used via LVM.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350
(German) https://debianforum.de/forum/viewtopic.php?f=33&t=154131
Yes this is not a full-blown solution, but progress.
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
add a comment |
0
0
0
You may have leftover metadata from earlier partitioning. Like a boot partition that is used without LVM but which has LVM metadata because an installer prepared it to be used via LVM.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350
(German) https://debianforum.de/forum/viewtopic.php?f=33&t=154131
Yes this is not a full-blown solution, but progress.
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
You may have leftover metadata from earlier partitioning. Like a boot partition that is used without LVM but which has LVM metadata because an installer prepared it to be used via LVM.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/452350
(German) https://debianforum.de/forum/viewtopic.php?f=33&t=154131
Yes this is not a full-blown solution, but progress.
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
answered May 11 '16 at 9:19
klaus thornklaus thorn
1
1
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186536%2fcorrupt-lvm-metadata-header-after-kernel-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the exact same problem as your first machine. As I understand this metadata is some leftovers from the installation part, when you are configuring partitions and LVMs. I still do not have a solution. Regarding your second machine, you do not have this problem cause you did not configure any LVMs. As you can see the
pvdislayreturns a physical drive only– Athafoud
Apr 8 '15 at 15:04