On Mon, May 5, 2014 at 1:18 AM, Stefan G. Weichinger <[email protected]> wrote: > Am 05.05.2014 07:09, schrieb Canek Peláez Valdés: >> On Sat, May 3, 2014 at 2:41 PM, Canek Peláez Valdés <[email protected]> wrote: >> [snip] >>> Let me try to update this test VM to see if I can hit the same issue as >>> you. >> >> OK, I updated everything, and I certainly hit an issue. With >> sys-kernel/dracut-037, I cannot boot; it gets stuck after loading the >> initramfs and it complains about not able to mounting /. This happens >> even with the patch on [1]. >> >> With sys-kernel/dracut-036-r4, everything works perfectly. I don't >> know what the problem is exactly, but as a workaround I would >> recommend staying on With sys-kernel/dracut-036-r4. >> >> Regards. >> >> [1] >> http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=12819a579900b9691e2bfaf14e76fbb025851530 > > Interesting. > > I had my VG not activated again when I booted today. > > Going back to sys-kernel/dracut-036-r4 means downgrading systemd as well > here (at least with the current ebuilds in portage) ... I will skip that > for now as today I need this box up and running for work ;-)
I think I already mentioned this: dracut is the only package keyworded, so I run the stable version of systemd: 208-r3. > Do you think we should file a bug for ... something? ;-) There is for sure a regression with the latest dracut. That should be reported, yes. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
