I resized the root filesystem on Fedora 29 in VirtualBox from 15GB to 20GB but can no longer get it to boot. It always lands in the dracut emergency shell. After first resizing the VDI and the snapshots in VirtualBox, I enlarged the disks as per steps 1.1 to 1.11 according to the accepted answer on this thread. I was executing step 2 (reboot) when I hit the problem.
Running blkid
I see /dev/sda1
and /dev/sda2
. I have mounted /dev/sda1
in Fedora Live and can see that it is the boot partition, so can edit the grub configuration if I wanted to, but I can find no way of mounting /dev/sda2
. LVM reports no devices.
There is a difference in the output of blkid
for the two devices. While /dev/sda1
reports UUID
, TYPE
and PARTUUID
I only see PARTUUID
on /dev/sda2
. When I deleted and re-created the partition with fdisk
, did it wipe out some metadata that LVM needs? Any idea how I can get this system booting again?
The partition in question was recreated larger but its starting sector remained
. In your case LVM is an additional layer but the general rule stands: enlarging a partition to the right by deleting and re-creating it requires the left end (starting sector) to stay put. Is it possible you changed the starting sector?dd
with that of the same device from an earlier snapshot taken a month ago when I was still running FC23. I found that thelvm_type
field in theLABEL_HEADER
had been zeroed out! I'm not sure whyfdisk
would have done that and I wasn't sure if there was a "proper" way to fix it, but a quick binary edit anddd
the modified block back to disk and hey presto the missing volumes reappeared in/dev/mapper
and could be mounted. I will try to reproduce this and post a proper analysis.