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

Bug#368029: installation-report: somewhat successful installation on Supermicro A+ AS1020P-T



On Wed, May 24, 2006 at 03:41:15PM +0200, Filip Van Raemdonck wrote:
On Fri, May 19, 2006 at 05:47:14PM +0200, David Härdeman wrote:
On Fri, May 19, 2006 at 02:02:16PM +0200, Filip Van Raemdonck wrote:
>vgdisplay -v
>   Finding all volume groups
> Incorrect metadata area header checksum
>   Finding volume group "alpha"
>...
>There's one more oddity, which is the "Incorrect metadata area header
>checksum" message lvdisplay/vgdisplay/pvdisplay are giving. Anyone know
>what that could be?

That is usually caused by a partition which has had a pv header (from using pvcreate) and then later used for a filesystem. The result is often that the pv header is only partially overwritten by the fs.

Right, I initially created a LVM partition at the beginning of the disk,
then went back to change the first into a small /boot partition and put
the LVM partition after that.
So it is sda1 which is recognized as a pv.

How can I fix it?

Normally you'd have to run pvremove on /dev/sda1, the problem is that it will wipe the beginning of the partition (first 2k I think), so if you're going to do that, you have to move the data off it, umount, pvremove, mkfs, mount, move data back, re-install grub or lilo into the partition header/MBR.

Alternatively you could use a hexeditor and look for the LVM signature "LVM2 001" on the partion and replace that with zero's...if you're feeling adventurous

Re,
David



Reply to: