On Sat, May 3, 2014 at 8:48 AM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 03.05.2014 15:46, schrieb Canek Peláez Valdés: >> On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld <jo...@antarean.org> wrote: >> [snip] >>> Sounds like an issue with the mdadm script/unit. >>> Where is Canek with his knowledge of systemd? >> >> Canek was sleeping because it was 6:37 AM on a Saturday morning. > > hehe ;-) > > good morning then ... (and late congrats to your phd, btw ;-) )
Thanks Stefan. Regarding your problem; as I said to Joost, I have no idea what could possibly cause the problem, but from the experiments I conducted trying to understand what happened with systemd+LVM2, I got the impression that this kind of issue happens only with people having very personalized or kinda old LVM2 setups. I remember your fstab had the volumes listed directly. The systemd+udev+dracut guys (and to some degree the kernel devs too, I believe) are trying to move away from that. Could you try to set up labels for all your mounted points and use that in fstab? It's a shot in the dark, I don't really know if it will work. Also, the usual requirements: boot with debug, rd.debug, systemd.log_target=console, systemd.log_level=debug and please share the logs. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
