On Thu, May 28, 2015 at 3:30 AM, <cov...@ccs.covici.com> wrote: > > Stefan G. Weichinger <li...@xunil.at> wrote: > > > On 28.05.2015 09:39, cov...@ccs.covici.com wrote: > > > > > 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. > > > > Hm, I think it could help for sure as you could chroot in and do > > something. For example build a new kernel or initrd or ... > > > > You removed openrc? Otherwise boot via openrc and (try to) fix stuff. > > > > You could even reinstall openrc from within chroot ... just to get > > bootin again etc etc > > > > > > > > > > > > > > I still have openrc, but Dracut won't work with it, at least maybe > because I have systemd use flag enabled. Also, in retrospect, that > would not have solved my specific problems, because it was related to an > rd.lv command which is specific to dracut. > > But thanks for your suggestion. I wonder what the rescue target is -- I > have never seen that before -- maybe I could configure it so I could > boot into a shell and fix things and it would be sort of like a little > system of its own.
Others have already answered, but I will add that if you put "emergency" anywhere in the kernel command line, then systemd will boot to the rescue target; that's why I suggested to do it in my first answer. Also, as Rich said, if you wait it's possible that systemd (and/or dracut) will drop you into a rescue shell anyway. Unfortunately, thanks to very slow hardware in the wild, the timeout has been increased to three minutes, and I believe those are *per hardware unit*. So if you have five disks, in theory it could take fifteen minutes to get you to a rescue shell. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
