On Fri, May 16, 2014 at 5:53 AM, <cov...@ccs.covici.com> wrote: > Canek Peláez Valdés <can...@gmail.com> wrote: > >> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <li...@xunil.at> wrote: >> > Am 15.05.2014 22:38, schrieb cov...@ccs.covici.com: >> > >> >> image=/boot/vmlinuz-3.6.2-gentoo >> > >> > phew. 3.6.2 is from October 2012 ... >> > Did you recompile it with the suggested options for systemd? >> > >> > Maybe it doesn't matter, but just a thought ... that kernel is quite old. >> >> It doesn't matter, at least in theory systemd works with linux-3.0. >> >> John, could you please send the output from dracut --print-cmdline? In >> my case, it lists *ALL* my lvms, and (I think) therefore all of them >> are mounted. >> >> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and >> rd.lvm.lv=linux-files/64-usr, I think that would explain why it >> doesn't mount the others. >> >> If dracut --print-cmdline doesn't print the others, could you try to >> boot with rd.lvm.lv=linux-files/audio in the kernel command line >> specified in your lilo.conf? If after booting /audio is mounted, then >> I think we have found the problem. We'll need just to figure out why >> dracut --print-cmdline does not print the other lvms. >> >> Also, could you try to generate your initramfs again, but this time >> with add_dracutmodules+="systemd lvm"? > The secret to activate all the volumes, is to specify the volume groups > instead of each volume -- that got them all activated, but systemd still > is not working well. The print-cmdline still just prints the volumes > necessary to mount the root and user file systems, which makes sense, > but why the rest of them do not activate, I have no clue.
I don't understand the current situation .So now you get ALL your volumes activated, or not? > Now for some systemd problems. The root file system was read only when > I logged in, but I could remount it rw -- not sure why this was > happening. Set systemd.log_level=debug in your command line, and post the exit from journalctl -b. > Some units did start, but most did not. Whenever I tried to > start one manually, I got a message like the following: > I wrote > systemctl start /usr/lib/systemd/system/ntpd.service and got the error > that it was unable to start because > it could not find ntpd.service.mount:] > May 16 01:59:52 ccs kernel: <31>systemd[1]: Failed to load configuration > for usr-lib-systemd-system-ntpd.service.mount: No such file or directory > May 16 01:59:52 ccs kernel: <31>systemd[1]: Trying to enqueue job > usr-lib-systemd-system-ntpd.service.mount/start/replace > May 16 01:59:53 ccs kernel: <31>systemd[1]: Sent message type=error > sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1 > reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount > failed to load: No such file or directory. > May 16 01:59:53 ccs kernel: <31>systemd[1]: Failed to process message > [type=method_call sender=n/a path=/org/freedesktop/systemd1 > interface=org.freedesktop.sys\temd1.Manager member=StartUnit > signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to > load: No such file or directory. > > No matter what unit I tried to start I would get such a message about > the service.mount. That sounds like a problem with the cgroups hierarchy (which uses a virtual filesystem). I don't remember seeing a problem like that before. > Also, even though my network names were correct, they did not come up, > but I will try to look in the logs to see why not. systemd will not (AFAIK) start your network, and before the 209 or 210 version it needed helper program (NetwokrManager, connman, ip, ifconfig, etc.) to do it. Now it includes networkd, but you need to set up .network files (like .service files) to configure it. See [1]. > So we have made some progress, but still a long way to go yet. Note > also, that I am not booting into a display manager, just a regular > console. > > > What a lot of work just to get the system booted! Well, you have a setup that is not, by any means, simple. Also, in my experience old LVM configurations seem to cause a lot of troubles to bring to what systemd expects. John, could you also post here your kernel config? Those cgroups errors *may* be related to some missing functionality from the kernel. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
