" On Sun, Jul 23, 2017 at 3:51 PM, Winfried de Heiden <wdh@xxxxxx> wrote: > Hi all, > > After installing Fedora 26 on a Raspberry Pi 2 I modified the default > install somewhat. Since I use a 32 GB SDcard, thereś plenty of extra space I > replaced the swap partition for an LVM2 partition to put swap, /home, > /var/log, /var/log/audit on a separate partition. (used gparted to do so) > > This all seems to work fine but when /tmp is put on an LVM-partition boot > will fail: > > [root@rpi2 ~]# 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; > static; vendor preset: disabled) > Active: failed (Result: exit-code) since Tue 2017-06-27 23:45:19 CEST; 3 > weeks 4 days ago > Docs: man:tmpfiles.d(5) > man:systemd-tmpfiles(8) > Main PID: 569 (code=exited, status=1/FAILURE) > > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: Unable to fix SELinux > security context of /var/tmp: Read-only file system > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: Unable to fix SELinux > security context of /var/spool: Read-only file system > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: Unable to fix SELinux > security context of /tmp/.X11-unix: Read-only file system > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: Unable to fix SELinux > security context of /tmp/.ICE-unix: Read-only file system > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: Unable to fix SELinux > security context of /tmp/.font-unix: Read-only file system > Jun 27 23:45:19 rpi2.blabla.bla systemd-tmpfiles[569]: > rm_rf(/tmp/systemd-private-a9f0ce0042314665bae7fc5f45b79f4f-chronyd.service-mrb21j): > Read-o > Jun 27 23:45:19 rpi2.blabla.bla systemd[1]: systemd-tmpfiles-setup.service: > Main process exited, code=exited, status=1/FAILURE > Jun 27 23:45:19 rpi2.blabla.bla systemd[1]: Failed to start Create Volatile > Files and Directories. > Jun 27 23:45:19 rpi2.blabla.bla systemd[1]: systemd-tmpfiles-setup.service: > Unit entered failed state. > Jun 27 23:45:19 rpi2.blabla.bla systemd[1]: systemd-tmpfiles-setup.service: > Failed with result 'exit-code'. > > > The root-partition will mount read only during boot when /tmp is on a > separate (LVM) partition. Now, after booting: > - mount -o remount,rw / > - mount -a > > and all will work fine be shouldn't be that way.... > > What going wrong here....? I have no idea but if I was to guess I suspect the initird doesn't have the lvm related components to enable it to mount tmp on that type of filesystem stack (it is usually either tmpfs or on root) so you'll probably need a dracut config that adds the appropriate dracut and kernel modules into the initrd and then regenerate the initrd. "man 5 dracut.conf" will likely give you all the information you need. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
