Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to move /run/initramfs to / #28645

Closed
Freyon77 opened this issue Aug 2, 2023 · 14 comments · Fixed by #28648
Closed

Failed to move /run/initramfs to / #28645

Freyon77 opened this issue Aug 2, 2023 · 14 comments · Fixed by #28648
Labels
bug 🐛 Programming errors, that need preferential fixing regression ⚠️ A bug in something that used to work correctly and broke through some recent commit shutdown

Comments

@Freyon77
Copy link

Freyon77 commented Aug 2, 2023

systemd version the issue has been seen with

254-1-arch

Used distribution

Archlinux

Linux kernel version used

6.4.7

CPU architectures issue was seen on

x86_64

Component

other

Expected behaviour you didn't see

I want to see my shutdown clean and fast

Unexpected behaviour you saw

While shutting down / reboot archlinux receiving errors but system reboot correctly.

systemd-shutdown: Failed to move /run/initramfs to /: invalid argument

systemd-shutdown: Failed to switch root to "run/initramfs" invalid argument

Steps to reproduce the problem

Shutdown system / reboot system

Additional program output to the terminal or log subsystem illustrating the issue

No response

@Freyon77 Freyon77 added the bug 🐛 Programming errors, that need preferential fixing label Aug 2, 2023
@yuwata yuwata added regression ⚠️ A bug in something that used to work correctly and broke through some recent commit shutdown labels Aug 2, 2023
@Freyon77
Copy link
Author

Freyon77 commented Aug 2, 2023

Propably releated

Generated archiso with latest systemd few minutes ago and on shutdown getting same errors as above plus one error extra.

system-d shutdown: Unable to finalize remaining loop device, ignoring

Not sure if official latest iso is affected

yuwata added a commit to yuwata/systemd that referenced this issue Aug 2, 2023
@yuwata
Copy link
Member

yuwata commented Aug 2, 2023

Could anyone test #28648?

@akiirui
Copy link

akiirui commented Aug 2, 2023

Could anyone test #28648?

I've tried building systemd with your PR. But it looks like it doesn't solve the issue.

@WebReflection
Copy link

same issue here, looking forward to see the patch landed in ArchLinux, thanks for the fix 👋

@Oldfart28
Copy link

Same issue here.

@Puxap-3opre
Copy link

The same. Also it seems shutdown takes a couple of seconds longer.

@vecinohk
Copy link

vecinohk commented Aug 5, 2023

Hi, I am also adding 6.4.8-arch1-1 + 254-1 and every time I reboot I get this error. If you want to test the fix - I'm happy to test it on myself. Thanks

@PaulPintang
Copy link

PaulPintang commented Aug 7, 2023

same issue here. don't know but it also affects programs like vscode, chrome, and alacrity. It glitches when I launch them.

Edit: glitches fixed: change kernel from linux-zen to linux-lts. glitches not related to this bug.

@Freyon77
Copy link
Author

Freyon77 commented Aug 7, 2023

Exactly, it is not possible. To test it properly you would have to check after a fresh system installation without any system shutdown.

@DrPicklez
Copy link

I also have this issue on:
6.4.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 03 Aug 2023

systemd-shutdown[1]: Failed to move /run/initramfs to /: Invalid argument
systemd-shutdown[1]: Failed to switch root to "/run/initramfs": Invalid argument

This is my first Arch install have I done something wrong?

@Freyon77
Copy link
Author

Freyon77 commented Aug 8, 2023

I also have this issue on:
6.4.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 03 Aug 2023

systemd-shutdown[1]: Failed to move /run/initramfs to /: Invalid argument
systemd-shutdown[1]: Failed to switch root to "/run/initramfs": Invalid argument

This is my first Arch install have I done something wrong? No, you will get rid of it in next update.

@vecinohk
Copy link

vecinohk commented Aug 8, 2023

Guys this bug has already been fixed in the upstream and now we are waiting for a release. No need to report it anymore just wait for the patch to be released.

@WebReflection
Copy link

WebReflection commented Aug 8, 2023

No need to report it anymore just wait for the patch to be released.

all Arch users are waiting indeed ... thinking Y U SO LATE in the process 😅

@vecinohk
Copy link

It's here ... after today's installation of systemd 254.1-1 the error message is gone. 👍

systemd 254.1-1
https://archlinux.org/packages/core/x86_64/systemd/

mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
This should provide coverage for shutdown initrd related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
This should provide coverage for shutdown initrd related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
This should provide coverage for shutdown initrd related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
And move the initrd related tests from TEST-01-BASIC there.

Additionally, this should provide coverage for recemt shutdown initrd
related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
And move the initrd related tests from TEST-01-BASIC there.

Additionally, this should provide coverage for recemt shutdown initrd
related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 11, 2023
And move the initrd related tests from TEST-01-BASIC there.

Additionally, this should provide coverage for recemt shutdown initrd
related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
mrc0mmand added a commit to mrc0mmand/systemd that referenced this issue Aug 12, 2023
And move the initrd related tests from TEST-01-BASIC there.

Additionally, this should provide coverage for recemt shutdown initrd
related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
YHNdnzj pushed a commit to YHNdnzj/systemd that referenced this issue Aug 12, 2023
And move the initrd related tests from TEST-01-BASIC there.

Additionally, this should provide coverage for recemt shutdown initrd
related issues, see:
  - systemd#28645
  - systemd#28648
  - systemd#28793
minimada added a commit to minimada/openbmc that referenced this issue Sep 20, 2023
Issue:
We cannot perform BMC FW update due to systemd-shutdown error.
systemd/systemd#28645
systemd-shutdown: Failed to move /run/initramfs to /: invalid argument
systemd-shutdown: Failed to switch root to "run/initramfs" invalid argument

Fix:
systemd/systemd#28648
The systemd upstream already fix this issue, but poky not merge it.
So we need manual cherry-pick the fix patches into our repository, and
remove it once poky merge these changes.

Signed-off-by: Brian Ma <chma0@nuvoton.com>
maxdog988 pushed a commit to Nuvoton-Israel/openbmc that referenced this issue Sep 25, 2023
Issue:
We cannot perform BMC FW update due to systemd-shutdown error.
systemd/systemd#28645
systemd-shutdown: Failed to move /run/initramfs to /: invalid argument
systemd-shutdown: Failed to switch root to "run/initramfs" invalid argument

Fix:
systemd/systemd#28648
The systemd upstream already fix this issue, but poky not merge it.
So we need manual cherry-pick the fix patches into our repository, and
remove it once poky merge these changes.

Signed-off-by: Brian Ma <chma0@nuvoton.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Programming errors, that need preferential fixing regression ⚠️ A bug in something that used to work correctly and broke through some recent commit shutdown
Development

Successfully merging a pull request may close this issue.

9 participants