> Wiping the front of the new disks may help. Ok, so, I did that and, the errors with vgchange are still there. Now, that's without the node being in the cluster yet either. I removed lvm2 and lvm2-cluster ignoring deps. // Uninstalling packages lvm2 lvm2-cluster .. Uninstallation failed : warning: /etc/lvm/lvm.conf saved as /etc/lvm/lvm.conf.rpmsave error reading information on service lvm2-monitor: No such file or directory error: %postun(lvm2-2.02.21-5.el4.XOS.1.i386) scriptlet failed, exit status 1 \\ I turned the cluster services back on and rebooted. Comes up fine in the cluster; # cman_tool nodes Node Votes Exp Sts Name 40 1 5 M cweb40.companions.com 58 1 4 M compdev.companions.com 62 1 5 M img62.companions.com 92 1 5 M cweb92.companions.com Do an fdisk -l; # fdisk -l - Looks fine, needs partition. Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 4767 38290896 83 Linux /dev/hda2 4768 4865 787185 82 Linux swap Disk /dev/sda: 774.2 GB, 774207700992 bytes 255 heads, 63 sectors/track, 94125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sda doesn't contain a valid partition table Create new GFS drive; # gfs_mkfs -p lock_dlm -t compweb:web -j 8 /dev/sda This will destroy any data on /dev/sda. Are you sure you want to proceed? [y/n] y Device: /dev/sda Blocksize: 4096 Filesystem Size: 188738976 Journals: 8 Resource Groups: 2882 Locking Protocol: lock_dlm Lock Table: compweb:web Syncing... All Done Go DANG!!!! I screwed it up by adding VG information, compweb:web. Now what? I have to fix this then re-do it, how? Mike -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
