You are not logged in.
Every so often, when I update my system with pacman -Syu, I see the error message below. This has been the case for quite some time with no apparent ill-effects, but I'd like to see if I can "fix" (or understand the cause of) the error:
...
:: Running post-transaction hooks...
( 1/19) Creating system user accounts...
( 2/19) Updating journal message catalog...
( 3/19) Reloading system manager configuration...
( 4/19) Updating udev hardware database...
( 5/19) Applying kernel sysctl settings...
( 6/19) Creating temporary files...
error: command failed to execute correctly
( 7/19) Reloading device manager configuration...
( 8/19) Arming ConditionNeedsUpdate...
( 9/19) Updating module dependencies...
(10/19) Install DKMS modules
...
The pacman.log file suggests that the problem is with 30-systemd-tmpfiles.hook:
...
[2019-12-31T12:03:58+0000] [ALPM] transaction completed
[2019-12-31T12:04:00+0000] [ALPM] running '20-systemd-sysusers.hook'...
[2019-12-31T12:04:00+0000] [ALPM] running '30-systemd-catalog.hook'...
[2019-12-31T12:04:00+0000] [ALPM] running '30-systemd-daemon-reload.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '30-systemd-hwdb.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '30-systemd-sysctl.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '30-systemd-tmpfiles.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '30-systemd-udev-reload.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '30-systemd-update.hook'...
[2019-12-31T12:04:01+0000] [ALPM] running '60-depmod.hook'...
[2019-12-31T12:04:15+0000] [ALPM] running '70-dkms-install.hook'...
[2019-12-31T12:04:15+0000] [ALPM-SCRIPTLET] ==> dkms install nvidia/440.44 -k 4.19.91-1-lts
[2019-12-31T12:05:24+0000] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.1.0_OSE -k 4.19.91-1-lts
[2019-12-31T12:05:47+0000] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.1.0_OSE -k 5.4.6-arch3-1
[2019-12-31T12:06:11+0000] [ALPM-SCRIPTLET] ==> dkms install nvidia/440.44 -k 5.4.6-arch3-1
...
I haven't modified /usr/share/libalpm/hooks/30-systemd-tmpfiles.hook myself, and I can't see anything obviously wrong with it:
[Trigger]
Type = File
Operation = Install
Operation = Upgrade
Target = usr/lib/tmpfiles.d/*.conf
[Action]
Description = Creating temporary files...
When = PostTransaction
Exec = /usr/share/libalpm/scripts/systemd-hook tmpfiles
I'm not sure what else I can do to troubleshoot further. Can anyone help?
Last edited by esuhl (2020-01-02 22:34:18)
Offline
What is the output of
systemctl status /usr/lib/systemd/system/systemd-tmpfiles-setup.service
Offline
What is the output of
systemctl status /usr/lib/systemd/system/systemd-tmpfiles-setup.service
Thanks for your reply! The output is:
Unit usr-lib-systemd-system-systemd\x2dtmpfiles\x2dsetup.service.mount could not be found.
Offline
I made a mistake with the command. What is the output of
systemctl status systemd-tmpfiles-setup.service
Offline
I made a mistake with the command. What is the output of
systemctl status systemd-tmpfiles-setup.service
The output to that is:
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: active (exited) since Thu 2020-01-02 18:48:11 GMT; 3min 34s ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 560 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=73)
Main PID: 560 (code=exited, status=73)
Jan 02 18:48:11 i7pc systemd[1]: Starting Create Volatile Files and Directories...
Jan 02 18:48:11 i7pc systemd-tmpfiles[560]: Failed to write file "/sys/block/sde/queue/scheduler": Invalid argument
Jan 02 18:48:11 i7pc systemd[1]: Started Create Volatile Files and Directories.
Offline
Jan 02 18:48:11 i7pc systemd-tmpfiles[560]: Failed to write file "/sys/block/sde/queue/scheduler": Invalid argument
There will be a config file in /etc/tmpfiles.d or /usr/lib/tmpfiles.d that is failing to set the scheduler for sde.
If you correct or disable that config is the issue resolved? See also man 5 tmpfiles.d.
Offline
There will be a config file in /etc/tmpfiles.d or /usr/lib/tmpfiles.d that is failing to set the scheduler for sde.
If you correct or disable that config is the issue resolved? See also man 5 tmpfiles.d.
Aha! I discovered the following file:
/etc/tmpfiles.d/10-ioscheduler.conf
w /sys/block/sde/queue/scheduler - - - - noop
The "sde" drive contains a single NTFS partition that has never been mounted. And (according to the wiki) noop is no longer supported. Very odd.
Deleting that file resolves the systemd error:
$ systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; st>
Active: active (exited) since Thu 2020-01-02 20:59:10 GMT; 45s ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 556 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot ->
Main PID: 556 (code=exited, status=0/SUCCESS)
Jan 02 20:59:10 i7pc systemd[1]: Starting Create Volatile Files and Directories>
Jan 02 20:59:10 i7pc systemd[1]: Started Create Volatile Files and Directories.
Thanks again for your help! :-D
Offline