systemd-tmpfiles-setup.service - Create Volatile Files and Directories

English Install/Boot/Login
#1

I’m seeing this error at every boot - more detail:

  * systemd-tmpfiles-setup.service - Create Volatile Files and Directories      Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)    Active: failed (Result: exit-code) since Sun 2017-06-25 08:38:21 +10; 10min ago      Docs: man:tmpfiles.d(5)            man:systemd-tmpfiles(8)   Process: 659 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)  Main PID: 659 (code=exited, status=1/FAILURE)  Jun 25 08:38:20 beano systemd[1]: Starting Create Volatile Files and Directories... Jun 25 08:38:21 beano systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Jun 25 08:38:21 beano systemd[1]: Failed to start Create Volatile Files and Directories. Jun 25 08:38:21 beano systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Jun 25 08:38:21 beano systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.  

 I read some things on the Arch Wiki about ACL's but that seemed mostky applicable EXT* file systems and I have the default btrfs install with Tumbleweed. Can anyone suggest a fix for this, please?  

Apologies about the formatting, I couldn't work out how to separate blocks of text?
#2

Don’t know if it is the same issue
But I have the same error on boot.

https://bugzilla.opensuse.org/show_bug.cgi?id=1042053

Also:
https://www.reddit.com/r/openSUSE/comments/6cke0p/systemd_error_failed_to_start_create_volatile/

#3

Seems quite similar. I suspect it’s an ACL thing with btrfs. I’ll probably reinstall using EXT4 for root and see what happens.

#4

I am seeing that same fail message. And I am using “ext4” for the root file system.

#5

Thanks for the information. The more I read, the more it seems like a systemd problem. I did notice this: https://pastebin.com/UVvcNqRT

#6

I fixed this error message by adding sys:x:3: to the /etc/group file.

#7

Thanks for that.

I just reinstalled using EXT4 for root and the problem also went away.