Hi folks. I spent a very frustrating time last night trying to figure
out why my systemd would not boot using systemd. I am using dracut and
its version is 041r2. Now what was happening is that the system would
get to the pre-init-queue -- and I even set the rd.break there, but
after that the system would not boot -- when I used debug it endlessly
said calling setl forever. Now it turned out that the problem was that
I had mistyped an rd.lv= line -- instead of ssd-files/usr I had
ssd-files/-usr . Now, what I would like to know is how could I tell
that it was trying to look for a non-existent lv? At the point of the
break. no lvm volumes were active, although strangely enough I saw a
e2fsck for the real root file system which was an lvm volume. I am
finding its generally hard to debug systemd problems, several other
times the system just sat there till I figured it out some other way.
Any observations on this would be appreciated, but I don't want to get
into a flame war, I just want to minimize the down time.
--
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
