You are not logged in.
Hi guys,
many system upgrades trigger the `systemd-tmpfiles.hook` which fails for me and leaves the error message "command not executed correctly" (translated myself) during upgrade. Digging deeper I learned that the hook executes `systemd-tmpfiles --create` which fails:
# systemd-tmpfiles --create
Failed to write file "/sys/block/sda/queue/scheduler": Invalid argument
Following the problem in strace gives me a hint:
openat(5, "scheduler", O_WRONLY|O_NOCTTY|O_NONBLOCK|O_CLOEXEC) = 4
write(4, "noop", 4) = -1 EINVAL (Invalid argument)
where systemd tries to write `noop` to the file `/sys/block/sda/queue/scheduler` which only supports the schedulers
# cat /sys/block/sda/queue/scheduler
[mq-deadline] kyber bfq none
So apparently systemd tries to set an invalid scheduler. But I have no clue where it takes the `noop` scheduler from. Can anybody give me a hint on how to fix this, please? I really don't like this error message during upgrades
Last edited by aliena (2019-04-02 07:34:15)
Offline
The locations systemd-tmpfiles will search for conf files are listed in `man 5 tmpfiles.d`
Offline
I found the faulty file in /etc/tmpfiles.d/10_ioscheduler.conf. No clue how it got there but now it's gone.
Thank you for the hint
Offline