Am 22.10.2013 05:46, schrieb Sean Greenslade:
On Mon, Oct 21, 2013 at 02:55:20PM +0200, Thomas Bächler wrote:
Am 21.10.2013 03:34, schrieb Sean Greenslade:
And now, after another system update, the problem has vanished. There was a kernel update, so I'm willing to believe that it was just some strange transient interaction between LVM, mdadm and the initramfs kernel. Just another day in the life of Arch, I suppose.
This is confusing.
A common problem is that the mkinitcpio image is generated mid-upgrade. If some component of lvm is updated before the kernel and another is upgraded after, this may lead to broken images. We can't prevent this from happening right now, but OTOH I haven't seen it in a while.
To be on the safe side, run 'mkinitcpio -P' after kernel updates.
That would make sense. I didn't try enough downgrade-upgrade cycles to test that theory. I'll add that to the list of things to do when updating.
For the future, pacman hooks ([1]) may solve that problem without user interaction, but as far as I know nothing has been implemented yet. [1] https://wiki.archlinux.org/index.php?title=User:Allan/Pacman_Hooks