[linux-lvm] Volume groups not found

Wolfe, Gordon W gordon.w.wolfe at boeing.com
Fri Mar 1 14:25:02 UTC 2002

This is crossposted to both the Linux-390 list and the Linux-LVM list.
Sorry for the duplicates, but I'm desparate.

I've been running more than a dozen Linux guests under z/VM running SuSE
Linux/390 with the 2.2.16 kernel.  This was supplied with LVM 0.8-157.

We are in the process of upgrading to SuSE Linux/390 with the 2.4.7 kernel,
supplied with LVM 0.9.1-beta-32.

One server is running as a Samba print and file server for a department.
The /home directory is an ext2 logical volume consisting of ten real 3390-3
volumes.  This arrangement has been working fine for about six months.

In doing the upgrade from 2.2.16 to 2.4.7, we essentially replace everything
but /home and a few files in /etc.  I booted from the 2.4.7 reader ramdisk,
insmod dasd for all dasd devices, mounted the root dasd as /mnt, did a
chroot to /mnt and mounted the /usr dasd.  To recover /home, I did the usual

vgscan;vgchange -ay

This should have found all ten volumes of the volume group and logical
volumes and rebuilt the information to remount the /home logical volume.
Instead I get the messages that a) it's scanning all disk devices and b) no
logical volumes were found.

Needless to say, this is a real show-stopper.   Can anyone help me find the
solution to this problem?

"Never trust any computer you can lift."
Gordon Wolfe, Ph.D. (425)865-5940
VM Technical Services, The Boeing Company

More information about the linux-lvm mailing list