On Wed 26 Nov 2014 at 14:34:36 -0500, Haines Brown wrote: > On Wed, Nov 26, 2014 at 06:56:18PM +0100, Sven Hartge wrote: > > > Use > > > > systemctl --failed > > > > to list failed units. Then use > > > > systemctl status name_of_failed.service > > > > to get further information. > > Sven, thank you. I did as you suggested:
This is a new Jessie install? No customisations made, especially to the kernel and modules and module loading? > # systemctl --failed > ... Does "..." indicate the output of the command has been edited? Not a good thing to do in general. > * systemd-modules-load.service > * systemd-remount-fs.service > > # systemctl status systemd-modules-load.service > ... > Locked: loaded (/lib/sysdemd/system/systemd-modules-load.service; static > Active: failed (Result: exit-code)... > Process: 199 ExecStart=/lib/systemd/system/systemd-modules-load (code > = existed, status=1/FAILURE > > The systemctl status run on systemd-remount-fs.service has same return > except for the process number. > > > systemctl status systemd-modules-load.service > > > > which should show you the logs associated with the failed modules. > > Probably you have modules listed in /etc/modules which cannot be loaded. > > Did I miss a pointer to a log? How otherwise would I identify modules > that can't be loaded? journalctl _PID=199 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/26112014201859.e118de881...@desktop.copernicus.demon.co.uk
