Re: [gentoo-user] problems debugging a systemd problem

Canek Peláez Valdés <caneko@×××××.com> wrote:

> On Thu, May 28, 2015 at 2:11 PM, <covici@××××××××××.com> wrote:
> >
> > > 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.
> >
> > Thanks much.  Does the rescue target try to mount all the disks?  Also,
> > I would still like to get in touch with the dracut devs -- although I
> > may never make that particular mistake again, but maybe other things
> > will happen.
>
> As I said in my previous mail: emergency mounts the root filesystem
> read-only; rescue mounts all the filesystems read/write. If dracut cannot
> mount the root filesystem, it *WILL* drop you to a shell, but it will take
> some time while all the timeouts expire. This could be *several* minutes
> depending on hardware.
>
> The dracut mailing list is in [1].
>
> Regards.

OK, thanks much.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@××××××××××.com