The system doesn't shutdown normally

wishmaster · 2022-05-24 12:35:24

Hi.

I started to have the following problem. I shut down my PC and the following message appears on the screen:

"Broadcast message from wishmaster@arch
The system is going down for poweroff NOW"

with a beep sound.

When I rebooted the errors continued, a black screen saying that I needed to run fsck to my problematic partition.
I did that, correcting all the problems. And rebooted again.

Now the system boots normally but "Broadcast message from wishmaster@arch
The system is going down for poweroff NOW" continue to appear. But the system boots normally. I don't need to check my filesystem again.

What is going on with my system?

This is my last journalctl from the poweroff process.

Thanks for your answers.

may 24 09:22:27 ARCH-LINUX kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-17
may 24 09:22:27 ARCH-LINUX kernel: Linux version 5.17.9-arch1-1 (linux@archlinux) (gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 SM>
may 24 09:22:27 ARCH-LINUX kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=0e06f92c-9bff-4e8a-8ce9-c3ccf770023d rw loglevel=>
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
may 24 09:22:27 ARCH-LINUX kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
may 24 09:22:27 ARCH-LINUX kernel: signal: max sigframe size: 2032
may 24 09:22:27 ARCH-LINUX kernel: BIOS-provided physical RAM map:
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000073e86fff] usable
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x0000000073e87000-0x0000000074786fff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x0000000074787000-0x000000008a99dfff] usable
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008a99e000-0x000000008ab9dfff] type 20
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008ab9e000-0x000000008b59dfff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008b59e000-0x000000008bc8dfff] ACPI NVS
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008bc8e000-0x000000008bd0dfff] ACPI data
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008bd0e000-0x000000008bd0efff] usable
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x000000008bd0f000-0x000000008f7fffff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x00000000ff600000-0x00000000ffffffff] reserved
may 24 09:22:27 ARCH-LINUX kernel: BIOS-e820: [mem 0x0000000100000000-0x000000026e7fffff] usable

Last edited by wishmaster (2022-05-24 12:39:01)

seth · 2022-05-24 12:44:42

Please use code tags, https://bbs.archlinux.org/help.php#bbcode or a pastebin service (1st link below)

That's not your last boots journal, but its head - what brings us to the next item: don't copy out of the pager (the journal will be horizontally capped)

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

V1del · 2022-05-24 12:47:55

That's a single truncated page of a journal. Produce the faulty situation then post a complete

sudo journalctl -b-1

to get the previous boot's journal and post that directly via a pastebin service

e.g.

 sudo journalctl -b-1 | curl -F 'f:1=<-' ix.io

See also the following similar thread for some potential further suggestions: https://bbs.archlinux.org/viewtopic.php?id=276631

Edit: Fuck...

Last edited by V1del (2022-05-24 12:48:26)

wishmaster · 2022-05-24 13:01:18

Thanks for the answers.

Here is the complete journalctl output: http://ix.io/3YuV

seth · 2022-05-24 13:21:41

The message isn't in that journal (nor any obvious error) - when and where exactly does the message show up?

LarryIsBet · 2022-05-24 19:50:28

Hi I have the same issue along side a beep when shutting down, rebooting and entering hibernation, downgrading systemd to systemd-250 made the issue go away so it seems like systemd issue?

Last edited by LarryIsBet (2022-05-24 19:52:35)

seth · 2022-05-24 19:57:46

The shutdown/reboot/hibernation behavior is discussed in forementioned https://bbs.archlinux.org/viewtopic.php?id=276631 but the OP seems to indicate that the message also appears during the boot process.

rudolf_schlepke · 2022-05-24 20:00:11

Hi all. This same thing happened to me after I updated my system on May 23. I suspect this happened as a result of updating systemd from version 250 to 251. Could not find any solution, so I had roll back my packages to May 22.

Used this article: https://wiki.archlinux.org/title/Arch_L … cific_date
Link to rollback date in the archive: https://archive.archlinux.org/repos/2022/05/22/

Last edited by rudolf_schlepke (2022-05-24 20:01:04)

wishmaster · 2022-05-24 22:49:13

Thanks to all for the replies!
I downgraded the packages to 05/22 and the issue seems to be fixed.
It's the first time I made a downgrade of my system. When should I continue with the update of my system?
Should I wait until a new version of systemd is available?

seth · 2022-05-25 05:54:20

The OP wrote:

Now the system boots normally but "Broadcast message from wishmaster@arch
The system is going down for poweroff NOW" continue to appear. But the system boots normally.

Please clearify whether this was a shutdown/reboot issue only or whether you also saw it *during* the boot process.

You need to wait until the problem is fixed ( whenever that is, they might have re-introduced https://github.com/systemd/systemd/issues/2796 ) or learn to live with it when lennart declares it notabug™…
In any event it's likely going to require a journal that covers the incident to get this ahead.

rudolf_schlepke · 2022-05-25 07:10:02

wishmaster wrote:

When should I continue with the update of my system?
Should I wait until a new version of systemd is available?

I will wait for newer systemd version for sure, postponing my updates for the moment.

Arch Linux

#1 2022-05-24 12:35:24

The system doesn't shutdown normally

#2 2022-05-24 12:44:42

Re: The system doesn't shutdown normally

#3 2022-05-24 12:47:55

Re: The system doesn't shutdown normally

#4 2022-05-24 13:01:18

Re: The system doesn't shutdown normally

#5 2022-05-24 13:21:41

Re: The system doesn't shutdown normally

#6 2022-05-24 19:50:28

Re: The system doesn't shutdown normally

#7 2022-05-24 19:57:46

Re: The system doesn't shutdown normally

#8 2022-05-24 20:00:11

Re: The system doesn't shutdown normally

#9 2022-05-24 22:49:13

Re: The system doesn't shutdown normally

#10 2022-05-25 05:54:20

Re: The system doesn't shutdown normally

#11 2022-05-25 07:10:02

Re: The system doesn't shutdown normally

Board footer