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