On a RHEL5.3 VMWare guest, after removing 2 LVM physical volumes from a volume group without doing a vgreduce first, the volume group won't activate after reboot

Solution Verified - Updated -

Issue

System originally had 3 drives in VolGroup01, two 50GB drives and one 100GB drive. A 4th drive (120GB) was added to system and VolGroup01 and the data from the two 50GB drives was copied to this 4th drive.

The system was shut down and the two 50GB drives were removed (using VMware). The system was booted and it complained that it could not find the two drives. The system dropped into Repair Filesystem mode and would not boot normally.

Reattaching the 2 physical volumes has not resolved the issue

Environment

  • Red Hat Enterprise Linux 5.3 guest under VMWare

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content