1 |
On Sun, Dec 8, 2013 at 4:36 PM, walt <w41ter@×××××.com> wrote: |
2 |
> On 12/08/2013 10:39 AM, Neil Bothwick wrote: |
3 |
>> On Sun, 8 Dec 2013 11:12:23 -0600, Canek Peláez Valdés wrote: |
4 |
>> |
5 |
>>>> It has the same problem. I looked more carefully at the systemd logs |
6 |
>>>> and found that lvm was running before the xhci kernel module was |
7 |
>>>> loaded, hence the usb3 drive was not visible yet. |
8 |
>>>> |
9 |
>>>> I "fixed" the problem by adding "After=basic" to the lvm.service |
10 |
>>>> file, and now it works as expected. (Expected by me, anyway :) |
11 |
>>> |
12 |
>>> Well, at least is working, however is kinda an ugly fix. Could you |
13 |
>>> create the file /etc/modules-load.d/usb3.conf, with the line xhci in |
14 |
>>> it, reboot, and see if your little hack is not needed then? Also, if |
15 |
>>> you are using an initramfs, could you rebuild it before trying? |
16 |
>> |
17 |
>> Alternatively, build xhci into the kernel, since you need it at every |
18 |
>> boot. |
19 |
> |
20 |
> Both of the suggestions above reversed the order of the journalctl |
21 |
> messages so that the usb3 drive appears before lvm.service is run, |
22 |
> but pvscan still finds no volumes and the volume group is not active |
23 |
> after bootup :( |
24 |
|
25 |
Sounds like another module is then missing at early boot up time. Do |
26 |
you have CONFIG_BLK_DEV_DM compiled in-kernel, or as a module? What |
27 |
about the other CONFIG_DM_* options? |
28 |
|
29 |
If they are modules, put them in a /etc/modules-load.d/*.config file. |
30 |
|
31 |
> I changed After=basic.target to After=sysinit.target, which still |
32 |
> gets it working well enough for my primitive needs. IMHO that fix |
33 |
> allows me to decrement ${HACKED} by one :) |
34 |
|
35 |
Not editing unit files would be best, I think. |
36 |
|
37 |
Regards. |
38 |
-- |
39 |
Canek Peláez Valdés |
40 |
Posgrado en Ciencia e Ingeniería de la Computación |
41 |
Universidad Nacional Autónoma de México |