Broke Fedora 20 by changing the Volume Group Name and resizing root in LVM.

asked 2014-02-25 08:50:48 -0600

VickedVenkat gravatar image

updated 2014-02-25 12:44:24 -0600

mether gravatar image

In an attempt to seperate my /home from my root, I did the following using a Parted Magic USB ISO.

  1. I resized ext4 filesystem on root using resize2fs
  2. Then reduced the lvm partition using lvreduce.
  3. Then used lvcreate to create a new partition.
  4. Mounted the new partition and moved data.
  5. I also created an Additional Partition and renamed the volume group.

I then edited fstab and added the UUIDs of the partition to the disk. It gets stuck at Reached Target System. I then tried to generate a new GRUB2 config file using grub2-mkconfig using the fedora Live USB. Still same thing.

Also the grub is on a seperate /boot partition. The entire lvm is on an ssd and grub stage 0 is on a HDD that loads this. Grub is working fine but fedora stops loading at Reached Target System.

edit retag flag offensive close merge delete

Comments

1

Verify that you can see the partitions using the Parted Magic (vgchange -ay) Edit /etc/fstab and remove the UUID and try using using the location (/dev/mapper/<lvname>) of the partitions instead of the UUIDs. </lvname>

You might have the wrong UUIDs also.

swilson gravatar imageswilson ( 2014-02-25 15:42:37 -0600 )edit

grub2-mkconfig needs to be done in a chroot, like you get with the rescue environment from the install image. dracut --regenerate-all --force to regenerate initramfs while in the chroot is a good idea too.

randomuser gravatar imagerandomuser ( 2014-02-26 16:19:48 -0600 )edit