and
https://mailman.archlinux.org/pipermail … 29123.html
Solution:
Append
lvmwait=/dev/sdXY
where sdXY corresponds to where you root lv resides.
]]>#!/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.
]]>Now on to fixing an xorg problem on my second Arch box. It seems the breakages never end
Edit: Is there a way to make this happen automatically at boot time? I'm sure there must be one...
]]>You can fix your boot by executing
>lvm vgchange --sysinit -a y
manually in the console you get dropped in. This should work, in my case it didn't and the system failed to boot correctly after some initial booting up.
Anyway it seems to be an issue with 3.5.3, I didn't look deeper into it and will be using 3.4.8 for some time.
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?
]]>