Broken LVM setup due to recent systemd upgrade

Question

So yeah, a couple of days ago I let the system upgrade and rebooted. My setup is basically two identical HDDs in a RAID 0 array + LVM. After the recent upgrade, boot hangs somewhere in the reading of the init ramdisk and tells me that it cannot find my volume groups. Any clues as to what I could do to fix it?
In the case that a fresh install is needed (which would quite annoy me) - any clues as to why the god-damned install media refuses to boot from a USB?

Answer 1

I haven't tested it but people claim that adding lvmwait to your bootloader command line and modifying the lvm2 hook (/usr/lib/initcpio/hooks/lvm2) to this
#!/usr/bin/ash
run_hook() {
local pvdev
modprobe -q dm-mod >/dev/null 2>&1
# If the lvmwait= parameter has been specified on the command line
# wait for the device(s) before trying to activate the volume group(s)
for pvdev in ${lvmwait//,/ }; do
poll_device ${pvdev} ${rootdelay}
done
msg "Activating logical volumes..."
lvm pvscan
[ -d /etc/lvm ] && lvm vgscan
if [ -n "$quiet" ]; then
lvm vgchange --sysinit -a y >/dev/null
else
lvm vgchange --sysinit -a y
fi
Fixes the problem.
I've found the fix in this thread : https://bbs.archlinux.org/viewtopic.php?id=145714
It's not clear where the bug comes from, it's probably upstream but only Arch users have experienced it, so it seems that it was made apparent by the options used during compilation by Arch maintainers.
Personally I prefer a downgrade to such a work around. I'm tired of new kernels breaking my system. I had major issues after the upgrades to 3.3 and 3.4, and now this.
Last edited by anon1054572 (2012-09-07 09:22:19)