Gentoo Archives: gentoo-user

From: covici@××××××××××.com
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] problems debugging a systemd problem
Date: Thu, 28 May 2015 19:11:11
Message-Id: 2981.1432840260@ccs.covici.com
In Reply to: Re: [gentoo-user] problems debugging a systemd problem by "Canek Peláez Valdés"
1 Canek Peláez Valdés <caneko@×××××.com> wrote:
2
3 > On Thu, May 28, 2015 at 3:30 AM, <covici@××××××××××.com> wrote:
4 > >
5 > > Stefan G. Weichinger <lists@×××××.at> wrote:
6 > >
7 > > > On 28.05.2015 09:39, covici@××××××××××.com wrote:
8 > > >
9 > > > > No, the journal is gone, it was only in /run which is on a tmpfs file
10 > > > > system. I can boot from a cd all day long, but it would not help one
11 > > > > bit.
12 > > >
13 > > > Hm, I think it could help for sure as you could chroot in and do
14 > > > something. For example build a new kernel or initrd or ...
15 > > >
16 > > > You removed openrc? Otherwise boot via openrc and (try to) fix stuff.
17 > > >
18 > > > You could even reinstall openrc from within chroot ... just to get
19 > > > bootin again etc etc
20 > > >
21 > > >
22 > > >
23 > > >
24 > > >
25 > > >
26 > >
27 > > I still have openrc, but Dracut won't work with it, at least maybe
28 > > because I have systemd use flag enabled. Also, in retrospect, that
29 > > would not have solved my specific problems, because it was related to an
30 > > rd.lv command which is specific to dracut.
31 > >
32 > > But thanks for your suggestion. I wonder what the rescue target is -- I
33 > > have never seen that before -- maybe I could configure it so I could
34 > > boot into a shell and fix things and it would be sort of like a little
35 > > system of its own.
36 >
37 > Others have already answered, but I will add that if you put "emergency"
38 > anywhere in the kernel command line, then systemd will boot to the rescue
39 > target; that's why I suggested to do it in my first answer.
40 >
41 > Also, as Rich said, if you wait it's possible that systemd (and/or dracut)
42 > will drop you into a rescue shell anyway. Unfortunately, thanks to very
43 > slow hardware in the wild, the timeout has been increased to three minutes,
44 > and I believe those are *per hardware unit*. So if you have five disks, in
45 > theory it could take fifteen minutes to get you to a rescue shell.
46
47 Thanks much. Does the rescue target try to mount all the disks? Also,
48 I would still like to get in touch with the dracut devs -- although I
49 may never make that particular mistake again, but maybe other things
50 will happen.
51
52
53
54 --
55 Your life is like a penny. You're going to lose it. The question is:
56 How do
57 you spend it?
58
59 John Covici
60 covici@××××××××××.com

Replies

Subject Author
Re: [gentoo-user] problems debugging a systemd problem "Canek Peláez Valdés" <caneko@×××××.com>