2014-05-14 3:40 GMT-06:00 <cov...@ccs.covici.com>: > 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. >> >> Everything is documented in the man page: man 1 systemd. > > Well, I rebooted under dracut, but it did not do the lvmscan and so the > job trying to find the root file system timed out after 90 seconds. It > took me to the emergency shell which I had specified, and I was able to > do the lvm_scan and them magically root got mounted under sysroot, but I > had no idea what to do next to maybe get things going. > > So how can I get dracut to do its lvm_scan -- I even added the line > add_dracutmodules+="lvm"
This is a must if you are not running 'dracut --lvmconf' > but no joy. > I saved the rdsosreport.txt and if that is of any use, I can post it. > In the dracut manpage, I found the '--print-cmdline' argument , it generates a suggested kernel command line , I hadn't used it before, but this what it printed: rd.lvm.lv=gentoovg/usr rd.lvm.lv=gentoovg/root root=/dev/mapper/gentoovg-root rootflags=defaults rootfstype=ext4 So I guess, its neccesary to have this in the command line. At the time I struggled for an entire day with the same timeout when my LVs where not recognized, did research trial/error with dracut and genkernel, got them both working, stayed with dracut because I liked it, I tried to avoid this struggle for you on my first response, but I see is going to take you longer... > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com > PD: RTFM.
