M A Young durham.ac.uk> writes:
> Have you checked /etc/fstab? That is the traditional place to put mount
> details and I think systemd still uses it, so you may have a dead entry
> in that file.
Thank you! That was exactly it - there was a line
/dev/mapper/fedora-home /home
2013/1/13 M A Young
> On Sun, 13 Jan 2013, Andre Robatino wrote:
>
> After this, the contents of /home are back in place, and the output of
>> vgdisplay, lvdisplay, and fdisk -l look normal. But after rebooting, I get
>>
>> [ OK ] Started monitoring of LVM2 mirrors, snapshots etc. using
>> dme
On Sun, 13 Jan 2013, Andre Robatino wrote:
After this, the contents of /home are back in place, and the output of
vgdisplay, lvdisplay, and fdisk -l look normal. But after rebooting, I get
[ OK ] Started monitoring of LVM2 mirrors, snapshots etc. using dmeventd or
progress polling.
Timed out
> cd /
> tar cvf home.tar home
> umount home
> lvremove /dev/mapper/fedora-home
> lvextend -l +100FREE /dev/mapper/fedora-root
> resize2fs /dev/mapper/fedora-root
> tar xvf home.tar
Easy to reproduce in a VM after a minimal install with a large enough HDD that
it creates a separate home partition,
cornel panceac gmail.com> writes:
> afaik systemd wants nofail option for devices that may be missing at boot
> time.
But isn't that just covering up the problem? It shouldn't be looking for that
specific device, since it no longer exists. If I knew where the reference to it
was, I could remove
2013/1/13 Andre Robatino
> Normally I prefer not to have a separate home partition, but forgot to
> delete it
> during F18 installation. I used the following procedure to get rid of it
> and
> give the space back to the root partition, while preserving the contents of
> /home:
>
> cd /
> tar cvf
