Page 1 of 1

Deleted LVM volume, now Fedora will not boot!

Posted: Wed Apr 28, 2010 10:44 pm
by dsmialek
Hello,

I am a Linux novice, so please excuse me if I don't make sense.

My first experience with Linux has been with Amahi and Fedora 12. I setup my server following another user's experience here: http://forums.amahi.org/viewtopic.php?f ... atch#p5065

I wanted to be able to add to a storage pool in the future so I followed the direction to create a LVM volume group. Everything worked fine.

Now with Greyhole released which can provide the storage pool I was looking for, I want to get rid of LVM. So I copied off my data and went into LVM Manager and deleted my volume groups. No problem. I was then able to reformat the unallocated disk space.

No problem. Until reboot. Upon reboot, Fedora would not come up. The fsck filesystem check failed and I am left at a command line. The error message I get has:
/sbin/fsck.xfs: /dev/mapper/vg_server-LogVol00 does not exist
I am guessing fsck is trying to check the volume group I deleted and can't find it, causing the problem. Why is fsck looking for this volume group if I deleted it?

At the command prompt, I tried :
lvremove -f
and other ideas I found, but I get this response:
locking type -1 initialization failed
.

I then tried from a Ubuntu live CD, but still no luck. lvdisplay and vgdisplay show nothing. The live CD shows all my disks and data, but I still cannot boot to Fedora.

Any ideas?

Thanks.

Re: Deleted LVM volume, now Fedora will not boot!

Posted: Wed Apr 28, 2010 11:45 pm
by moredruid
I think you've forgotten to modify your /etc/fstab file.
The OS looks there which disks (partitions, logical volumes) should be mounted and where.
You'll need to hash out the entries in the /etc/fstab file that want to mount the LVs.
Just put a "#" at the beginning of the line, it should look like this:

Code: Select all

# /dev/vg_server/LogVol00 /your/mountpoint ...

Re: Deleted LVM volume, now Fedora will not boot!

Posted: Thu Apr 29, 2010 6:32 pm
by dsmialek
Thanks moredruid! That fixed it!

I've got a lot to learn about linux! I figured deleting the volume group in a nice GUI application like LVM manager would have taken care of all these things. Thanks again for your quick help.