| 1 |
Am 03.05.2014 15:59, schrieb Canek Peláez Valdés: |
| 2 |
|
| 3 |
> Regarding your problem; as I said to Joost, I have no idea what could |
| 4 |
> possibly cause the problem, but from the experiments I conducted |
| 5 |
> trying to understand what happened with systemd+LVM2, I got the |
| 6 |
> impression that this kind of issue happens only with people having |
| 7 |
> very personalized or kinda old LVM2 setups. |
| 8 |
|
| 9 |
... kinda old ... yep ... as mentioned this box and its setup has grown |
| 10 |
over the years. |
| 11 |
|
| 12 |
I think it is rather straight but sure, maybe the syntax is outdated -> |
| 13 |
|
| 14 |
> I remember your fstab had the volumes listed directly. The |
| 15 |
> systemd+udev+dracut guys (and to some degree the kernel devs too, I |
| 16 |
> believe) are trying to move away from that. Could you try to set up |
| 17 |
> labels for all your mounted points and use that in fstab? It's a shot |
| 18 |
> in the dark, I don't really know if it will work. |
| 19 |
|
| 20 |
Hmm, ok, I will check out how to change this. |
| 21 |
|
| 22 |
But isn't that later on in the sequence of boooting? The problem is that |
| 23 |
the mdadm-RAIDs aren't assembled and then systemd waits for these arrays |
| 24 |
to have the PVs ready for the LVM-VGs and LVs ... |
| 25 |
|
| 26 |
So I suspect the initramfs more ... and the assembly of the RAIDs. |
| 27 |
|
| 28 |
|
| 29 |
> Also, the usual requirements: boot with debug, rd.debug, |
| 30 |
> systemd.log_target=console, systemd.log_level=debug and please share |
| 31 |
> the logs. |
| 32 |
|
| 33 |
Yes, thanks, I will return with more infos ... |
Archives