Re: Reboot After Systemd 215-5 Upgrade

2014-09-29 Thread David Baron
On Sunday 28 September 2014 15:59:33 PaulNM wrote: > On 09/28/2014 03:26 PM, Carlo wrote: > > 2014-09-28 20:31 GMT+02:00 David Baron : > >> Here 'tis: ~$ cat /etc/fstab > >> # /etc/fstab: static file system information. > >> # > >> # Use 'blkid' to print the universally unique identifier for a > >>

Re: Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread PaulNM
On 09/28/2014 03:26 PM, Carlo wrote: > 2014-09-28 20:31 GMT+02:00 David Baron : >> Here 'tis: ~$ cat /etc/fstab >> # /etc/fstab: static file system information. >> # >> # Use 'blkid' to print the universally unique identifier for a >> # device; this may be used with UUID= as a more robust way to na

Re: Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread Carlo
2014-09-28 20:31 GMT+02:00 David Baron : > Here 'tis: ~$ cat /etc/fstab > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are

Re: Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread Carlo
2014-09-28 17:07 GMT+02:00 David Baron : > ~$ systemctl status systemd-remount-fs.service > ● systemd-remount-fs.service - Remount Root and Kernel File Systems >Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; static) >Active: failed (Result: exit-code) since Sun 2014-09-28 1

Re: Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread Carlo
2014-09-28 16:45 GMT+02:00 David Baron : > OK, here it is:~$ systemctl --failed > UNIT LOAD ACTIVE SUBDESCRIPTION > ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File > Systems > > LOAD = Reflects whether the unit definition was properly l

Re: Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread Carlo
2014-09-28 15:04 GMT+02:00 David Baron : > I am NOT complaining about systemd. Booted quickly as usual, and just fine. > > However: Very early on, their were two "FAILED" notices which I did were lost > too quickly to read, The boot went out of the quiet mode and then proceeded > just fine (with al

Reboot After Systemd 215-5 Upgrade

2014-09-28 Thread David Baron
I am NOT complaining about systemd. Booted quickly as usual, and just fine. However: Very early on, their were two "FAILED" notices which I did were lost too quickly to read, The boot went out of the quiet mode and then proceeded just fine (with all the startup text). Dmesg shows nothing Jounal