| 1 |
On Monday, August 22, 2011 12:31:19 PM Stefan G. Weichinger wrote: |
| 2 |
> Am 22.08.2011 12:26, schrieb Joost Roeleveld: |
| 3 |
> > Are they actually started in the right order? |
| 4 |
> > In other words, first RAID, then LVM? |
| 5 |
> |
| 6 |
> I don't know ;-) |
| 7 |
> |
| 8 |
> I still try to understand all this. |
| 9 |
> There is no specific RAID-service-file, so it seems to be done by udev |
| 10 |
> and the related target/service somehow. |
| 11 |
> |
| 12 |
> |
| 13 |
> lvm.service says |
| 14 |
> |
| 15 |
> After=udev-settle.service |
| 16 |
> |
| 17 |
> so udev should detect all devices first, then lvm.service gets started. |
| 18 |
> |
| 19 |
> But somehow this doesn't work here, only after hitting that timeout one |
| 20 |
> time. |
| 21 |
|
| 22 |
That's unfortunate. The stop-service might be started to try to clean up when |
| 23 |
it fails. |
| 24 |
|
| 25 |
What kind of RAID are you using? Does it perhaps rely on a module that is |
| 26 |
loaded in the background? |
| 27 |
In which case you could try adding that module as a dependency? |
| 28 |
|
| 29 |
-- |
| 30 |
Joost |
Archives