[arch-general] Error message with full disk encryption

[PeLo L]

Hi,


I've followed the arch wiki and deployed a full disk encrypted install. 
Everything works fine and am able to boot properly into the install. While 
trying to shutdown my system, systemd displays an error which says "systemd: 
stopped (with error)  /dev/mapper/crypt-boot". 'crypt-boot' is the device 
mapper name for the encrypted boot partition. Could someone explain this. Do I 
need to be concerned of any data loss in the boot partition?


- Solomon

Re: [arch-general] Error message with full disk encryption

[Carsten Mattner]

On Sat, Feb 13, 2016 at 10:49 AM, PeLo L  wrote:
>
> Hi,
>
>
> I've followed the arch wiki and deployed a full disk encrypted install.
> Everything works fine and am able to boot properly into the install.
> While trying to shutdown my system, systemd displays an error
> which says "systemd: stopped (with error)  /dev/mapper/crypt-boot".
> 'crypt-boot' is the device mapper name for the encrypted boot
> partition. Could someone explain this. Do I need to be concerned
> of any data loss in the boot partition?

I've seen this on old and newly installed root-luks systems myself.
Here it's always dm1 and I'm not sure if it's luks-root or luks-swap,
but it looks like a bug in systemd or one of the units because this
appeared sometime in the last 6 months or less.

Re: [arch-general] Alternative init system proposal

[João Miguel]

Sorry if I was too harsh. But the methods are for fundamentally
different purposes, apg's intends to remain compatible with systemd and
is backed up by the AUR, while artoo's intends to replace systemd and
has its own repositories elsewhere. AFAIK, artoo tried to convince apg
to join forces, with no success. So 2 methods remain, each with their
merits.

However, as you say, it's true it wasn't clear in the original article
why were there 2 methods. So I copied the article before the edit that
removed artoo's method to a sandbox [1]. Then I'll add new info from the
current article and finally present in the discussion page reasons for
it to be added back as it will be in the sandbox. I think a sandbox is
necessary because the original article with artoo's way is too much out
of date and incomplete.

Thank you for understanding,
João Miguel

[1] - https://wiki.archlinux.org/index.php/User:JMCF125/OpenRC

Re: [arch-general] Alternative init system proposal

[João Miguel]

> > I feel it pertinent to point out that a different rolling-release
> > distrobution ( http://www.voidlinux.eu/ ) does not use systemd, openrc, or
> > sysvinit. Void Linux uses runit exclusively, and thus patches projects like
> > KDE4 and Gnome3 to work without systemd (I don't mention KDE5 since nobody
> > has cared enough yet to put in the effort).
> Well, that's *amazing*... what does it mean for me, the user?
To me, the user, it means I there is a possibility for an alternative
init system without the devs having to do anything. It means there are
people out there working on this and work towards alternatives does not
need to start from scratch. You're on Linux: you ought not to be only a
user, but also a contributor, thus "voting" with your actions. That's
why you're on a mailing list, or at least why I am.

> I can only re-iterate: Can we please stop this thread?
I deleted the first half of it. I think it may turn out to be productive
now. Void Linux is a distribution besides Gentoo we can base off to
allow different init systems to be used.

Regards,
João Miguel

Re: [arch-general] Alternative init system proposal

[Bardur Arantsson]

On 02/13/2016 04:17 PM, João Miguel wrote:
>>> I feel it pertinent to point out that a different rolling-release
>>> distrobution ( http://www.voidlinux.eu/ ) does not use systemd, openrc, or
>>> sysvinit. Void Linux uses runit exclusively, and thus patches projects like
>>> KDE4 and Gnome3 to work without systemd (I don't mention KDE5 since nobody
>>> has cared enough yet to put in the effort).
>> Well, that's *amazing*... what does it mean for me, the user?
> To me, the user, it means I there is a possibility for an alternative
> init system without the devs having to do anything. It means there are
> people out there working on this and work towards alternatives does not
> need to start from scratch. You're on Linux: you ought not to be only a
> user, but also a contributor, thus "voting" with your actions. That's
> why you're on a mailing list, or at least why I am.

I don't think you've presented any plausible "use case" except "I want
to be different" -- which is fine, btw, but shouldn't drive development
decisions in the large.

I mean, if you really want to you can still write your own /sbin/init,
but I'm not seeing the point here.

(If your goal is to *learn*, then yes $DEITY yes, do that, but for
practical things... you need some more concrete and tangible goals to
challenge the decision of systemd-only for Arch Linux.)

Regards,

Re: [arch-general] Error message with full disk encryption

[Yaro Kasear]

On Sat, 2016-02-13 at 13:47 +0100, Carsten Mattner wrote:
> On Sat, Feb 13, 2016 at 10:49 AM, PeLo L  wrote:
> > 
> > Hi,
> > 
> > 
> > I've followed the arch wiki and deployed a full disk encrypted
> > install.
> > Everything works fine and am able to boot properly into the
> > install.
> > While trying to shutdown my system, systemd displays an error
> > which says "systemd: stopped (with error)  /dev/mapper/crypt-boot".
> > 'crypt-boot' is the device mapper name for the encrypted boot
> > partition. Could someone explain this. Do I need to be concerned
> > of any data loss in the boot partition?
> 
> I've seen this on old and newly installed root-luks systems myself.
> Here it's always dm1 and I'm not sure if it's luks-root or luks-swap,
> but it looks like a bug in systemd or one of the units because this
> appeared sometime in the last 6 months or less.

I have also seen this issue come up on my system. It doesn't seem to
affect anything except causing a slightly longer shutdown time. Still,
would be good to see this fixed.

Re: [arch-general] Alternative init system proposal

[João Miguel]

> (If your goal is to *learn*, then yes $DEITY yes, do that, but for
> practical things... you need some more concrete and tangible goals to
> challenge the decision of systemd-only for Arch Linux.)
The decision was to have systemd as a default, not to forbid any other
init system to be mentioned. I don't agree with the OP of this thread
when he said there should be an official version of Arch with OpenRC,
that's too much work.

I mean this: https://wiki.archlinux.org/index.php/User:JMCF125/OpenRC
should be here: https://wiki.archlinux.org/index.php/OpenRC. So that
this: http://systemd-free.org/ is not necessary, but instead just a nice
plus.

Best regards,
João Miguel

Re: [arch-general] Alternative init system proposal

[Bardur Arantsson]

On 02/13/2016 05:35 PM, João Miguel wrote:
>> (If your goal is to *learn*, then yes $DEITY yes, do that, but for
>> practical things... you need some more concrete and tangible goals to
>> challenge the decision of systemd-only for Arch Linux.)
> The decision was to have systemd as a default, not to forbid any other
> init system to be mentioned

Again... no "use case" apart from "I don't want to use systemd".

. I don't agree with the OP of this thread
> when he said there should be an official version of Arch with OpenRC,
> that's too much work.
>

OK, so thread over?

Regards,

Re: [arch-general] Alternative init system proposal

[João Miguel]

> If you want to make OpenRC easier to use on Arch, here's how:
> 1. Get more involved in the AUR to develop more/better OpenRC-specific
> packages
There are 4 mirrors for an unnoficial user repository with packages that
are officially used in Manjaro.
> 2. Draft a new OpenRC wiki article on your User page
Done. https://wiki.archlinux.org/index.php/User:JMCF125/OpenRC
> 3. Work on 1 and 2 until you feel like you have a clearly superior method
The method already existed, I just wanted to make it visible.
> 4. Open a discussion on the OpenRC talk page about replacing the article
> (this will most likely involved discussion on your User page as well on how
> to improve your draft)
> 5. Success
Or in this case, failure:
https://wiki.archlinux.org/index.php?title=Talk:OpenRC=420556
> 
> Max

João Miguel

Re: [arch-general] Alternative init system proposal

[respiranto]

On 2016-02-13 17:35, João Miguel wrote:
> The decision was to have systemd as a default, not to forbid any other
> init system to be mentioned. I don't agree with the OP of this thread
> when he said there should be an official version of Arch with OpenRC,
> that's too much work.
> 
> I mean this: https://wiki.archlinux.org/index.php/User:JMCF125/OpenRC
> should be here: https://wiki.archlinux.org/index.php/OpenRC. So that
> this: http://systemd-free.org/ is not necessary, but instead just a nice
> plus.
> 
> Best regards,
> João Miguel

I agree with you on the point, that the possibility of choice should not
be suppressed, but instead be welcome on the Wiki.
However, I also see how having two ways of doing something rather
unusual and officially unsupported may create notable confusion or at
least makes the article hard to read.

Hence I would suggest creating a totally new Wiki entry which explains
solely artoo's way, named e.g. 'OpenRC (eudev)'.
To prevent identical sections of both articles, your one should only
address the differences, i.e. sections 1{,.3} (Installation and Booting)
and 2.3 (Network) and some notes on further differences.
Obviously, the two articles should point to each other as a respective
alternative.

Re: [arch-general] Error message with full disk encryption

[Carsten Mattner]

On Sat, Feb 13, 2016 at 4:51 PM, Yaro Kasear  wrote:
> On Sat, 2016-02-13 at 13:47 +0100, Carsten Mattner wrote:
>> On Sat, Feb 13, 2016 at 10:49 AM, PeLo L  wrote:
>> >
>> > Hi,
>> >
>> >
>> > I've followed the arch wiki and deployed a full disk encrypted
>> > install.
>> > Everything works fine and am able to boot properly into the
>> > install.
>> > While trying to shutdown my system, systemd displays an error
>> > which says "systemd: stopped (with error)  /dev/mapper/crypt-boot".
>> > 'crypt-boot' is the device mapper name for the encrypted boot
>> > partition. Could someone explain this. Do I need to be concerned
>> > of any data loss in the boot partition?
>>
>> I've seen this on old and newly installed root-luks systems myself.
>> Here it's always dm1 and I'm not sure if it's luks-root or luks-swap,
>> but it looks like a bug in systemd or one of the units because this
>> appeared sometime in the last 6 months or less.
>
> I have also seen this issue come up on my system. It doesn't seem to
> affect anything except causing a slightly longer shutdown time. Still,
> would be good to see this fixed.

There's also some message bus errors on shutdown that are intermittent,
but even though it may sounds stupid, I've grown to ignore systemd
shutdown and startup issues for the most part, because they happen
occasionally and sometimes they don't. Nothing to write home about,
just growing pains or Kinderkrankheiten as they say in Germany :).

Re: [arch-general] Alternative init system proposal

[Carsten Mattner]

Just throwing this out there: Given nosh's support for importing
systemd units, that one might be another viable option.

Re: [arch-general] Error message with full disk encryption

[P . A . López-Valencia]

El 13/02/2016 a las 4:49 a. m., PeLo L escribió:
> Hi,
>
>
> I've followed the arch wiki and deployed a full disk encrypted install. 
> Everything works fine and am able to boot properly into the install. While 
> trying to shutdown my system, systemd displays an error which says "systemd: 
> stopped (with error)  /dev/mapper/crypt-boot". 'crypt-boot' is the device 
> mapper name for the encrypted boot partition. Could someone explain this. Do 
> I need to be concerned of any data loss in the boot partition?
>
>
> - Solomon
>

As you are shutting down, the filesystem becomes unreadable for the 
systemd process, you need to add the shutdown hook to mkinitcpio  in 
order to have a copy of the initramfs at shutdown time.

-- 
Pedro A. López-Valencia
http://about.me/palopezv/
Recession is when a neighbor loses his job. Depression is when you lose yours. 
-Ronald Reagan

Re: [arch-general] Error message with full disk encryption

[Merlin Büge]

Hi,

> As you are shutting down, the filesystem becomes unreadable for the 
> systemd process, you need to add the shutdown hook to mkinitcpio  in 
> order to have a copy of the initramfs at shutdown time.


I thought this was obsolete since mkinitcpio 16?
See 
https://lists.archlinux.org/pipermail/arch-dev-public/2013-December/025742.html
(I'm not sure, just curious...)

@OP: I had a similar issue a few months ago and fixed it, see second post of 
this: https://bbs.archlinux.org/viewtopic.php?id=205275
(But I still haven't understood *why* that fixed it...)


Best Regards,

mearon

Re: [arch-general] Alternative init system proposal

[Maxwell Anselm]

> There are 4 mirrors for an unnoficial user repository with packages that
> are officially used in Manjaro.
> > 3. Work on 1 and 2 until you feel like you have a clearly superior
method
> The method already existed, I just wanted to make it visible.

I think you misunderstood. I was not suggesting that you simply re-add the
information to the wiki with different wording.

artoo's method was already rejected from the wiki for several reasons as
pointed out on the talk page. If you find the current method on the wiki
lacking, then you will need to come up with some new method that both
improves on the wiki's method and avoids the pitfalls of artoo's.

Again, this is not about lack of choice. This is about a particular choice
being deemed unfit for the wiki. Any method that *relies* on an unofficial
repository (i.e. has no AUR alternative) is certainly not appropriate.

Max

Re: [arch-general] Error message with full disk encryption

[P . A . López-Valencia]

El 13/02/2016 a las 6:28 p. m., Merlin Büge escribió:
> Hi,
>
> I thought this was obsolete since mkinitcpio 16? See 
> https://lists.archlinux.org/pipermail/arch-dev-public/2013-December/025742.html
>  
> (I'm not sure, just curious...) @OP: I had a similar issue a few 
> months ago and fixed it, see second post of this: 
> https://bbs.archlinux.org/viewtopic.php?id=205275 (But I still haven't 
> understood *why* that fixed it...) Best Regards, mearon 

Well, it doesn't happen to me unless I add the hook. Probably it was 
true three years ago, but it got broken along the way. I customarily 
replace the udev hook with the systemd hook and not even then is the 
initramfs copy created on /run/initramfs unless I add the sd-shutdown 
hook. Or keep the udev hook and add the shutdown hook. Both work for me. :-)

-- 
Pedro A. López-Valencia
http://about.me/palopezv/
Recession is when a neighbor loses his job. Depression is when you lose yours. 
-Ronald Reagan

Re: [arch-general] Error message with full disk encryption

[P . A . López-Valencia]

El 13/02/2016 a las 6:44 p. m., P. A. López-Valencia escribió:
>
> Well, it doesn't happen to me unless I add the hook. Probably it was
> true three years ago, but it got broken along the way. I customarily
> replace the udev hook with the systemd hook and not even then is the
> initramfs copy created on /run/initramfs unless I add the sd-shutdown
> hook. Or keep the udev hook and add the shutdown hook. Both work for me. :-)
>

I correct myself. I was under the impression that the sd-systemd hook 
worked but it doesn't. Stick to the old udev and shutdown hooks.

-- 
Pedro A. López-Valencia
http://about.me/palopezv/
Recession is when a neighbor loses his job. Depression is when you lose yours. 
-Ronald Reagan