On Wed, May 14, 2014 at 4:43 AM, <cov...@ccs.covici.com> wrote: > Canek Peláez Valdés <can...@gmail.com> wrote: > >> On Mon, May 12, 2014 at 11:52 AM, <cov...@ccs.covici.com> wrote: >> > Canek Peláez Valdés <can...@gmail.com> wrote: >> > >> >> On Mon, May 12, 2014 at 11:31 AM, <cov...@ccs.covici.com> wrote: >> >> [snip] >> >> > OK, I will try dracut, >> >> >> >> I hope it works with dracut. This is my kernel command line and >> >> RAID/LVM related stuff from GRUB2: >> >> >> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash" >> >> GRUB_PRELOAD_MODULES="lvm mdraid1x" >> >> >> >> And this is my dracut.conf (minus comments): >> >> >> >> add_dracutmodules+="crypt lvm mdraid systemd" >> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256" >> >> fscks="umount mount /sbin/fsck* e2fsck" >> >> >> >> That's it. I didn't touched anything else to make dracut+systemd work >> >> with LVM and RAID (and LUKS, but that doesn't matter). >> >> >> >> Also, dracut comes with extensive and very clear documentation; check >> >> the man pages included. >> >> >> >> > but I still want to know what systemd is doing, >> >> > what processes its spawning, etc. -- how can I find this out -- I >> >> > thought to use the confirm_spawn, but it times out and keeps going, what >> >> > can I do instead? >> >> >> >> You can use bootchart: >> >> >> >> man 1 systemd-bootchart >> >> >> >> It will produce a chart with all the processes, and how long it takes >> >> for every one of them. But remember, the order depends on which one >> >> finishes before, and that can change from boot to boot. >> >> >> >> > Thanks people for all your responses, this is a great list. >> >> >> >> Regards. >> >> -- >> >> Canek Peláez Valdés >> >> Profesor de asignatura, Facultad de Ciencias >> > >> > Well, since I am unable to see, the graph would not do me any good, any >> > way to get it in text form? What I want to see (and I know the order >> > may change) is which starts first and so on, to make sure targets, >> > etc. do what I want them to do. >> >> Try adding this to your kernel command line: >> systemd.log_target=console systemd.log_level=debug. It will add a lot >> of output, including what is being executed. > > I also in my kernel command line said rd.lvm=1 just to make sure.
John, which version of dracut are you using? Also, what was the command line you used to generate it? Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
