Am 03.05.2014 15:59, schrieb Canek Peláez Valdés: > 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.
... kinda old ... yep ... as mentioned this box and its setup has grown over the years. I think it is rather straight but sure, maybe the syntax is outdated -> > 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. Hmm, ok, I will check out how to change this. But isn't that later on in the sequence of boooting? The problem is that the mdadm-RAIDs aren't assembled and then systemd waits for these arrays to have the PVs ready for the LVM-VGs and LVs ... So I suspect the initramfs more ... and the assembly of the RAIDs. > Also, the usual requirements: boot with debug, rd.debug, > systemd.log_target=console, systemd.log_level=debug and please share > the logs. Yes, thanks, I will return with more infos ...
