We have been experiencing strange LVM behaviour on multiple machines. The situation: - Debian 3.1 (Sarge) - 2.6.8.1 Kernel - LVM2 - 3 IDE disks (2x80GB, 1x120GB) (All Maxtors) Creating physical volumes is no problem for two disks, but with the third disk (it is actually on hdb and already a different disk then the one originally used) problems begin. pvcreate does not give any errors, but with pvdisplay the disk is not shown while pvscan gives "Couldn't find device with uuid 'xAMOJ3-xIGd-AJQK-HN5Q-Q9Yg-Mu2D-UYxn0Y'" It is possible to create volume groups and logical volumes, but pvscan, vgscan and lvscan keeping failing with the above error. Neither of the 3 disks has a partition when starting. When on hdb a partition is created and then hdb1 is used as physical volume everything works fine. Why does the partition need to be created on that disk for LVM to work (and not on the other two)? Is this a problem with LVM2, the 2.6 kernel? Or could it be hardware not functioning as it should, e.g. disk or controller? I would like to know why the creation of a partition is necessary. Has anyone experienced the same problem/behaviour with LVM? If so, is there a solution so no partition is needed? Thanks in advance for the help. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
