Stefan G. Weichinger <li...@xunil.at> wrote: > Am 2015-05-28 um 08:15 schrieb cov...@ccs.covici.com: > > > Thanks for your quick reply, but I do have rd.shell=1, but it did not > > drop to a shell,it just hung, so I could not do journalctl or anything > > -- the nearest break point was pre-initqueue which was maybe too early > > and the next one is pre-mount which it never got to. Unfortunately, I > > was in a position where I could not use an older kernel, because the > > older ones didn't have the configs to read gui type partitions-- I > > always keep several kernels around normally, but this was one of those > > transitional times when I was stuck. So do I need emergency aswell as > > rd.shell andis there any way to get a shell when the system appearsto > > be in some kind of a loop, like calling setl over andover again? > > > http://freedesktop.org/wiki/Software/systemd/Debugging/ ? > > Do you try to boot into rescue.target? > > Why not use a live-cd, boot, mount, chroot and get on there? > > You can read the journal of your failing installation via the > journalctl-binary of your booted live-system (I assume fedora live-media > boots with systemd ... dunno ad hoc which one to use) >
No, the journal is gone, it was only in /run which is on a tmpfs file system. I can boot from a cd all day long, but it would not help one bit. -- 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