On Fri, 03.02.17 09:23, Isla Finney (dr.isla.fin...@gmail.com) wrote: > > Feb 03 08:28:35 debian systemd-modules-load[386]: Failed to insert 'fuse': > No such file or directory > Feb 03 08:28:35 debian systemd[1]: systemd-modules-load.service: main > process exited, code=exited, status=1/FAILURE > Feb 03 08:28:35 debian systemd[1]: Failed to start Load Kernel Modules. > Feb 03 08:28:35 debian systemd[1]: Unit systemd-modules-load.service > entered failed state. > > root@debian:/home/lsc# dpkg -l | grep 'cifs' > ii cifs-utils 2:6.4-1 > amd64 Common Internet File System utilities > > root@debian:/home/lsc#lsmod | grep 'cifs' dmesg > (gives nothing) > > root@debian:/home/lsc# dmesg | grep 'cifs' > [ 14.347254] cifs: Unknown symbol setattr_prepare (err 0) > [ 14.347510] cifs: Unknown symbol setattr_prepare (err 0) > [ 14.347760] cifs: Unknown symbol setattr_prepare (err 0) > [ 34.359501] cifs: Unknown symbol setattr_prepare (err 0) > [ 34.361373] cifs: Unknown symbol setattr_prepare (err 0) > [ 34.363185] cifs: Unknown symbol setattr_prepare (err 0) > [ 1886.314336] cifs: Unknown symbol setattr_prepare (err 0)
This appears to be a problem with your kernel modules. Please contact you downstream distro for help, i.e. the folks who provide the modules and kernel to you. It has nothing to do with systemd really. Sorry, Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
