[Solved]systemd kills boot up till version 252.1-2-arch

Morta · 2022-12-04 11:23:27

My NAS

sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/okxk.txt

seth · 2022-12-04 14:03:52

That's 127MB?

Morta · 2022-12-04 14:10:32

Yes but don’t ask me why

seth · 2022-12-04 14:52:46

Cause it'S running for a week.

Nov 27 16:47:35 archlinux kernel: Linux version 6.0.10-arch2-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Sat, 26 Nov 2022 16:51:18 +0000
…
Nov 27 16:47:50 archlinux systemd[1]: Found device /dev/vg_data/root.

That's 15 seconds until the root partition shows up - how exactly is that better than your other system?
The log is virtually indistinguishable form the one you posted at filehorst

Morta · 2022-12-04 15:02:39

seth wrote:

Cause it'S running for a week.
Nov 27 16:47:35 archlinux kernel: Linux version 6.0.10-arch2-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Sat, 26 Nov 2022 16:51:18 +0000
…
Nov 27 16:47:50 archlinux systemd[1]: Found device /dev/vg_data/root.
That's 15 seconds until the root partition shows up - how exactly is that better than your other system?
The log is virtually indistinguishable form the one you posted at filehorst

I don’t fall in emergency mode and don’t have to downgrade systemd to boot properly!

How I can make my journal “pretty” ?

seth · 2022-12-04 15:09:59

What? Pretty??
Raise the rootdelay or use rootwait to wait indefinitely.
Alternatively look at your cryptsetup config again, 15-20 seconds delay is rather not normal?

Morta · 2022-12-04 15:17:31

seth wrote:

What? Pretty??
Raise the rootdelay or use rootwait to wait indefinitely.
Alternatively look at your cryptsetup config again, 15-20 seconds delay is rather not normal?

Sorry my english is limited.

I thought my journalctl is to big, not uploaded properly
and you can’t read. My fault.

The difference is that on my server machine I fall automatically in emergency mode with latest systemd 252.2-2 and on my nas not with systemd 252.2-2.

With systemd 252.1-2 the server boot up properly!

So why? I can increase root wait but I think won’t fix the problem which exists till systemd 252.2-1

Last edited by Morta (2022-12-04 15:17:49)

seth · 2022-12-04 15:31:02

I can increase root wait

No you can't.
https://raw.githubusercontent.com/torva … meters.txt

With systemd 252.1-2 the server boot up properly!

Post a journal of that as well, but I suspect it's merely between "almost too slow" and "too slow".

Morta · 2022-12-04 15:46:23

seth wrote:

I can increase root wait
No you can't.
https://raw.githubusercontent.com/torva … meters.txt
I added now rootwait to the bootloader. I will test it. -> Now it's going in emergency mode after long long time....
With systemd 252.1-2 the server boot up properly!
Post a journal of that as well, but I suspect it's merely between "almost too slow" and "too slow".

Sorry to say you it's really not a problem of this 15 second was it's far long but not too long. It's problem after prompting the password and boot like on the pictures above it's not finding the partitions root, data and backup. I prompted the right password. The services doesn't show up. Why should work with systemd252.1-2 and with systemd252.2-2 not? There is no other reason than other code of systemd, nor?

How can I show the two latest two boot sequence one with systemd252.1-2 and the other with systemd252.2-2?

I have no internet access in the emergency mode!

Morta · 2022-12-04 15:50:01

That should be the latest boot up

The other one can't find in the journal

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

https://0x0.st/okgW.txt

Last edited by Morta (2022-12-04 15:57:46)

seth · 2022-12-04 16:19:30

The emergency mode is triggered because the root device doesn't show up…

That journal is a bit older, is it?

Aug 09 01:03:22 archlinux kernel: Linux version 5.13.9-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Sun, 08 Aug 2021 11:25:35 +0000

but

Aug 09 01:03:22 archlinux systemd[1]: Starting Cryptography Setup for cryptdata...
Aug 09 01:03:22 archlinux systemd[1]: Starting Cryptography Setup for cryptroot...
Aug 09 01:03:44 archlinux systemd[1]: Finished Cryptography Setup for cryptdata.
Aug 09 01:03:52 archlinux systemd[1]: Finished Cryptography Setup for cryptroot.

cryptseup is likewise slow.

Morta · 2022-12-16 03:48:47

I did a bug report on systemd they said I have to open a bug report on the distro which I did.

The response was I have to bisect systemd version 252.1-2 and systemd 252.2.-1 to revert the wrong commit. Could someone help me?

seth · 2022-12-16 07:58:02

https://wiki.archlinux.org/title/Bisect … s_with_Git
https://wiki.archlinux.org/title/Arch_Build_System

What bootloader do you use? Grub? systemd-boot?

Morta · 2022-12-16 12:09:04

Yes systemd-boot

seth · 2022-12-16 13:17:25

There's a truckload of reports for systemd-boot 252 causing this, see eg. https://bbs.archlinux.org/viewtopic.php?id=281738 and https://bbs.archlinux.org/viewtopic.php?id=281990 and https://bbs.archlinux.org/viewtopic.php?id=281376 and there're resp. upstream bugreports.

I did a bug report on systemd they said I have to open a bug report on the distro which I did.

Please link those here, I'm curious how whether they try to reason "open a bug report on the distro"…

Morta · 2022-12-16 13:33:58

https://github.com/systemd/systemd/issu … 1351942623
https://bugs.archlinux.org/task/76834

seth · 2022-12-16 13:50:03

sYsTeMd dOeS NoT SuPpOrT LvM

…

Steps you need to take
1.

seth wrote:

Raise the rootdelay or use rootwait to wait indefinitely.

to see whether the abnormally late root device triggers this
2. use a different bootloader (eg. grub) along the recent systemd to see whether your problem is also down to systemd-boot

Morta · 2022-12-16 14:13:00

seth wrote:

sYsTeMd dOeS NoT SuPpOrT LvM
…
Steps you need to take
1.
seth wrote:
Raise the rootdelay or use rootwait to wait indefinitely.
to see whether the abnormally late root device triggers this
2. use a different bootloader (eg. grub) along the recent systemd to see whether your problem is also down to systemd-boot

1. already done

2. Ok I will do

seth · 2022-12-16 14:36:44

Already done where, how, with what outcome? Journal of that boot?

Morta · 2022-12-16 14:44:59

There is no journal it’s goes to the emergency console exactly the same behaviour as normal

seth · 2022-12-16 15:08:31

And how *exactly* did you increase the rootdelay?

Morta · 2022-12-16 18:15:30

I added rootwait to the kernel parameter

Last edited by Morta (2022-12-16 18:15:40)

Morta · 2022-12-16 18:21:46

I have this list as git tag command. How I know which is systemd252.1-2 and the other systemd252.2-1 to add a good commit and bad commit

I did following

git clone https://github.com/archlinux/svntogit-packages.git
git tag
git bisect good 4bbea20
git bisect bad 5ad540c
cd trunk
makepkg -efsi

makepkg fails with meson error. What I did wrong?

Last edited by Morta (2022-12-16 18:58:17)

Morta · 2022-12-16 18:54:54

Ok it's fails with GRUB too

PS: Is sd-encrypt and sd-vconsole is only needed by systemd-boot?

Last edited by Morta (2022-12-16 19:00:12)

cfr · 2022-12-16 19:16:19

Morta wrote:

Ok it's fails with GRUB too
PS: Is sd-encrypt and sd-vconsole is only needed by systemd-boot?

I don't think that's related to your boot-loader, but to the other hooks you use in mkinitcpio.conf. If you use systemd rather than udev in your initramfs, you need sd-encrypt, for example, whereas udev would need encrypt instead. But what's in your initramfs is relevant to what happens after the boot-loader does its job, as far as I know, so I don't think grub should care.

Arch Linux

#26 2022-12-04 11:23:27

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#27 2022-12-04 14:03:52

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#28 2022-12-04 14:10:32

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#29 2022-12-04 14:52:46

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#30 2022-12-04 15:02:39

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#31 2022-12-04 15:09:59

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#32 2022-12-04 15:17:31

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#33 2022-12-04 15:31:02

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#34 2022-12-04 15:46:23

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#35 2022-12-04 15:50:01

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#36 2022-12-04 16:19:30

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#37 2022-12-16 03:48:47

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#38 2022-12-16 07:58:02

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#39 2022-12-16 12:09:04

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#40 2022-12-16 13:17:25

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#41 2022-12-16 13:33:58

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#42 2022-12-16 13:50:03

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#43 2022-12-16 14:13:00

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#44 2022-12-16 14:36:44

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#45 2022-12-16 14:44:59

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#46 2022-12-16 15:08:31

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#47 2022-12-16 18:15:30

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#48 2022-12-16 18:21:46

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#49 2022-12-16 18:54:54

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#50 2022-12-16 19:16:19

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Board footer