You are not logged in.
Pages: 1
Hello everyone I'm a novice, I just signed up and I'm learning how to use Linux. On the shutdown screen, a message appears that has never appeared before:
[ 17.732640] systemd-shutdown[1]: Failed to move /run/initramfs to /: Invalid argument
[ 17.732640] systemd-shutdown[1]: Failed to switch root to " /run/initramfs": Invalid argument
Could someone please help me understand what it means?
Thank you very much
Offline
Were you able to restart your machine? And did this happen again after updating and restarting? What did you do beforehand? An update? Some more information would be helpful if you can.
Offline
Hi thanks for the reply
My machine works regularly actually. I noticed two days ago this strange message in the shutdown phase. I updated the machine most days. Could it be a kernel bug?Could you explain the meaning of the message?
Thank you very much
Last edited by syonth (2023-07-21 04:27:08)
Offline
Please post your complete system journal for the boot:
sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io
Offline
I'm very sorry for my crosspost.
PROBLEM SOLVED!!!
I had installed systemd254rc2, i don't know why, but a downgrade to systemd253.7-1 solved problem.
Maybe someone can explain to me what problem was created? I had to update initramfs, perhaps?
thank you very much for help, now I learned something more.
Last edited by syonth (2023-07-23 07:04:14)
Offline
I have started seeing this message on shutdown after upgrading to systemd 254-1 today. Is this an error we should be concerned about?
Offline
I encounter the same issue since updating to systemd 254-1 .
@seth : At the time of the messages the journal has already stopped.
Maybe there is a way to enable logging for the systemd-shutdown service ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
https://bbs.archlinux.org/viewtopic.php?id=282429 (probably unrelated to the login subject of that thread, though)
=> https://github.com/systemd/systemd/issues/28645
Offline
Me, too. Same error messages. Reboots fine though. Sounds like from your links, @seth, that the systemd devs reproduced it and are working on it.
Offline
Pages: 1