Arch Linux

shaohao

Member

Registered: 2008-04-28

Posts: 21

[SOLVED]systemd cannot boot lvm2 partion in fstab

My archlinux has been migrated to systemd.
I installed lvm2 to manage my hard disk.

Here is my /etc/fstab:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
tmpfs		/tmp	tmpfs	nodev,nosuid	0	0
/dev/mapper/VolGroup00-lv_root / ext4 defaults 0 1
/dev/mapper/VolGroup00-lv_home /home ext4 defaults 0 1

My system cannot boot into DM now.
Everything works well If i comment the line "VolGroup00-lv_home" in fstab. I have to mount the lv_home partition manally before I login the DE.

Last edited by shaohao (2012-08-13 12:04:33)

shaohao

Member

Registered: 2008-04-28

Posts: 21

Re: [SOLVED]systemd cannot boot lvm2 partion in fstab

Solved! Just reinstall the linux kernel package.

rpolzer

Member

Registered: 2012-08-15

Posts: 1

Re: [SOLVED]systemd cannot boot lvm2 partion in fstab

I got this one too. The oddity is that the device for /home (in my case /dev/mapper/cryptvg-home) did exist, so "mount /home" on the emergency shell worked (but I could not continue boot from there).

But I also got like millions of other times an unbootable system that only "mkinitcpio -p linux" could get fixed. Why can't pacman do this right? Can we at least have a temporary workaround option for pacman to ALWAYS do mkinitcpio -p linux at the end of the run (maybe generic PostInstall=/path/to/script and PostRun=/path/to/script options, where the former runs after every package and the latter runs at the very end)?