Default Installation on LVM is not working

Question

New Thread (Default installation of LVM not working):
First I did everything exactly as the LVM guide tells me. Then I continued with the Installation Guide.  No extra options, no change from defaults. When I try to boot it, it fails.
I tried downgrading to 2.02.103-1. No result.
Old Thread (when I did not know that LVM was at fault):
Current state:
EDIT5: OK I have boiled it down to LVM. When I copied all files from etcvol to /etc in root it continued booting until it hit mounting /home... I have no idea what the §$%&/ is wrong.
Everything that is not root and should get mounted by fstab from LVM dies o.O
Even stranger: After I removed homevol and swapvol from fstab i get stuck at
A start job is running for dev-sdb4.device
I did a "proof of concept" installation just now and it worked out of the box.
Parameters of the "proof of concept" installation:
/dev/sda5 ext4 /
/dev/sda4 EFI /boot
Rest is default installation guide
Gummiboot:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda5 rw
Changed Parameters of the broken installation:
/dev/sda3 LVM on LUKS
Partitions
/dev/mapper/MyStorage-rootvol ext4 /
/dev/sda4 EFI /boot
/dev/mapper/MyStorage-swapvol swap
/dev/mapper/MyStorage-homevol ext4 /home
title Arch Linux (Encrypted)
linux /initramfs-linux.img
options initrd=/initramfs-linux.img cryptdevice=/dev/sda3:MyStorage root=UUID=$UUIDofRoot rw
I added the HOOKS
HOOKS="... encrypt lvm2 keymap ... filesystems ... shutdown ..."
Fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=767d41f7-afb5-4a9f-a39b-604c830654e7
/dev/mapper/MyStorage-rootvol / ext4 rw,relatime,space_cache 0 0
# UUID=6e00082a-4fc4-47a5-9e80-e2330428d2fe
/dev/mapper/MyStorage-etcvol /etc ext4 rw,relatime,space_cache 0 0
# UUID=ce066cf1-230a-48b4-b7a8-2635ef39a881
/dev/mapper/MyStorage-homevol /home ext4 rw,relatime,space_cache 0 0
# UUID=0C88-FA2A
/dev/sdb4 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=9369aa55-d055-4fab-98ef-ccc97b3f3e05
/dev/mapper/MyStorage-swapvol none swap defaults 0 0
So what goes wrong? I can't provide the exact logs as the journal persistency module dies in this case. If you know a way to get the actual files please tell me.
Everything works fine down to "Reached target Local File Systems"
He runs some isEmpty checks on tmpfiles.d directories which some succeed and /etc/tmpfiles.d and /usr/local/lib/tmpfiles.d fail
systemd-tmpfiles --create --remove --exclude-prefix=/dev gets forked
journald gets killed by systemctl
systemd-tmpfile SIGCHILDs and dies
systemd-udevd gets notified and changes from start to running
udevd-control.socket gets changes to running
system-tmpfiles-setup exits with failure
Failed to start Recreate Volatile Files and Directories
systemd-update-utmp gets forked
accepts connection on private bus
10 times dbus request: org.freedesktop.dbus.local.disconnect() on /org/freedesktop/dbus/local
SIGCHILD from systemctl belonged to systemd-journal-flush.service
Failed to start Trigger Flushing of Journal to Persistent Storage
more dbus request: org.freedesktop.dbus.local.disconnect() on /org/freedesktop/dbus/local
systemd-update- from systemd-update-utmp SIGCHILDs and dies
Failed to start Update UTMP about System Reboot/Shutdown
starts system initialization sysinit.target -> active
starts dbus.socket to listeing
starts sockets.target to active
systemd-tmpfiles-clean.timer gets started by monotonic timer to cleanup
dbus-daemon gets forked
dbus.socket from listening to running
systemd-logind gets forked
Failed to start D-Bus System Message Bus
Failed to start Login Service
I had a look at higher debug levels, but they all just showed systemd starting something which either failed or in the case of D-Bus died soon after.
When I broke into init, I could see the volumes which contained what they were supposed to contain.
Except that nothing really interesting. I noticed a complaint that the AHCI driver should be replaced against a specialized one. But I don't think thats the problem.
Thank you for your help!
Last edited by GNA (2014-01-15 21:44:01)

Answer 1

Removed the fsck filehook.
posted the fstab.
Boot logs will follow shortly. I just have to figure out how to get them in file form when the journal does not contain anything.
EDIT: OK I have no idea how to get my own boot logs sad but true. ill just try to add as much context as I can see but I can't possibly write all of this down by hand.
EDIT2: Ah no wonder when flushing of journal to persistent storage fails
EDIT3: Ill just start decreasing the complexity one by one. And as it is so easy ill start with btrfs.
EDIT4: Changing btrfs to ext4 did not change anything.
EDIT5: OK I have boiled it down to LVM. When I copied all files from etcvol to /etc in root it continued booting until it hit mounting /home... I have no idea what the §$%&/ is wrong.
Everything that is not root and should get mounted by fstab from LVM dies o.O
Even stranger: After I removed homevol and swapvol from fstab i get stuck at
A start job is running for dev-sdb4.device
EDIT6: Today I tried to make a "failsafe" system with lvm and luks. Turns out it is not failsafe.
First I did everything exactly as the LVM on LUKS guide tells me. Then I continued with the Installation Guide.  No extra options, no change from defaults. The result is the very same I currently have.
EDIT7: Now that I think about it; There was something strange during pvcreate /dev/mapper/lvm. It complained: "/dev/sdc: open failed: No medium found" which is strange as there was never a /dev/sdc to begin with.
I'll try to install on a pure LVM partition without crypto.
EDIT8: OK pure install only LVM is also broken.
Last edited by GNA (2014-01-15 20:46:49)