Systemd automount of /home results in locate ignoring /home

Hi,
Per the suggestion on the systemd wiki page, I have instructed systemd (via /etc/fstab) to automount /home. This is supposed to allow me to boot faster on those occasions when my /home needs to be fsck'ed. (Please correct me if I've misunderstood this point.) This results in "mount" reporting that my /home filesystem type is "autofs".
This again results in locate ignoring my entire /home when indexing my harddisk, since the default /etc/updatedb.conf has PRUNEFS="(...) autofs (...)", i.e. it ignores all autofs filesystems. Now, I don't want to remove autofs from this list, since other filesystems that should be ignored (e.g. /proc/sys/fs/binfmt_misc) are of autofs type. I also would prefer to keep the automount trick from the wiki.
Any suggestions as to how this can be accomplished? I have RTFM for updatedb.conf, and it does not have a "whitelist" of any sort. That would be the optimal solution, IMO, but requires an update from the mlocate maintainer upstream. Can I tell systemd to fake the filesystem type of home, or to pass on the actual filesystem type (ext4)?

Here is another discussion of this issue: https://bbs.archlinux.org/viewtopic.php?id=154539
Apparently the time savings provided by automounting /home may not be not significant enough to make it worthwhile. You can test this yourself, or continue with the other workarounds you are already aware of.

Similar Messages

  • X-systemd.automount and sshfs

    I've been using sshfs to access files on my pi for serveral months now. Today i tried to enable automatic mounting with x-systemd.automount, but although a manual mount is still possible, the automatic mount fails constantly with a "no such device" error since i added the additional option in /etc/fstab. Journalctl -f on the pi reveals that the "Connection is closed [preauth]", so I would guess that something is wrong with my client authenticating. But I don't understand how is this possible because I can in fact mount the partition manually. Even if I use the exact command used by systemd (found via ps -fe) with root it prompts me for the password of my key and then it mounts correctly. Shouldn't automount then prompt for my password, when my X starts? Any ideas?
    line in /etc/fstab:
    herrzinter-pi.local:/media/mediacrypt /home/herrzinter/Multimedia fuse.sshfs users,noauto,_netdev,reconnect,x-systemd.automount 0 0
    Last edited by MrTea (2013-07-01 15:34:13)

    WonderWoofy is right, until now I always used the automatically generated nautilus entry to mount the remote folder. In this case mount command is executed as <user> and so I don't need to put the additional information in the /etc/fstab. btw i didn't exactly look this up, but I've used this setup for quiet some time now, and I guess, that I forgot the herrzinter@ part once and noted that it worked anyway
    I now added this and the "IdentityFile=/..." option pointing to a dummy ssh key without passphrase and it then it's working, but I am not to happy with this, as an empty passphare key is not really nice, and also nautilus is showing me duplicated entries... but in genreal I have to look at the setup again I am not sure anymore if the x-systemd.automount option is really such a good idea in my case, as the network setup of my laptop is changing quite often... perhaps a bash script at login, or a custom systemd unit is better suited for my purpose
    Thank you all anyway

  • Can systemd automounter unmount inactive fileystems?

    Hi,
    tl;dr: Can systemd automounter unmount fileystems after a period of inactivity, like autofs does?
    I've just started discovering the wonderful new world of systemd, and to my great joy I found that it contains an automounter, so I thought that I would be able to use that instead of using autofs.
    The single thing that I like to automount is my home NAS on my laptop (via NFSv4) that I every day take from home to work and then back home.
    To do this with autofs is kind of like killing mosquitoes with a flamethrower. I would much rather just have my automounted NAS defined in my fstab than having to force the slightly mysterious autofs.xxx-files to mount the drive with the options I want it to use.
    So, I got systemd to automount my NAS and all was joy! Until I realized that it wasnt unmounting it after a time of non-use. I have googled quite a bit, searched the forums, but have found no mention that systemd either has or doesnt have this kind of functionality.
    So my purpose with this post is to get a definitive answer, does systemd do this? And if it doesn't, maybe others searching for the same information will end up here, and find the answer...
    /DonO

    I've been having this problem for as long as I can remember. I have finally decided to sit down and work something out instead of my laptop hanging all the time when it can't find the nfs server. The systemd.automount feature is nice, but it really sucks that it does not auto unmount when the share is not found.
    Also, having systemd.automount means that every time I open vim, or a manpage, and there is no network connection, systemd tries to mount the shares. I'm not sure why because I am not directly accessing them. Everything loads slowly when systemd automount is active for my shares and there is no network connection.
    Using soft instead of hard is a workaround, but then when the network connection is lost, corruption can occur.
    It seems like the only way to really solve this problem is to have some kind of script run when the network comes up to mount the shares, and to unmount when it goes down. This would require custom systemd units or something. Diving into the systemd manuals is something I have been putting off because they are so hefty.
    For anyone that is interested, here is my fstab:
    lithium:/mnt/data /mnt/data nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
    lithium:/var/cache/pacman /var/cache/pacman nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
    Last edited by demizer (2013-07-14 09:00:23)

  • I searched for "Download FireFox 5 - got the following results: Found 1023 results for download firefox 5 in English. Please save me from having to wade through 1023 results to locate this download!

    I searched for "Download FireFox 5 - got the following results: Found 1023 results for download firefox 5 in English. Please save me from having to wade through 1023 results to locate this download!

    Why do you want the 5.0 version and not the just released Firefox 6 version?
    *Firefox 6.0.x: http://www.mozilla.com/en-US/firefox/all.html
    *Firefox 3.6.x: http://www.mozilla.com/en-US/firefox/all-older.html
    *http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest-5.0/

  • X-systemd.automount nfs drive

    Hi,
    I can't seem to get systemd.automount to behave.  I have an nfs share available on machine 'kombi' and am trying to access it from machine 'forrest':
    [root@forrest ~]# showmount -e kombi
    Export list for kombi:
    /mnt/nfs4/georgia 192.168.1.202
    /mnt/nfs4 192.168.1.202
    It is set up to automount in /etc/fstab:
    kombi:/georgia /mnt/georgia nfs4 rw,suid,dev,exec,noauto,nouser,async,clientaddr=192.168.1.202,_netdev,x-systemd.automount,x-systemd.device-timeout=8 0 0
    Logging output from journalctl indicates it timed out but then mounted:
    Dec 14 17:45:11 forrest systemd[1]: mnt-georgia.mount mounting timed out. Stopping.
    Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
    Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
    However it is not mounted. Any process trying to access /mnt/georgia hangs.
    Any ideas where I have gone wrong?  I don't care if it automounts at boot or at first access.  What I'd like is for it to gracefully handle mounting when 'kombi' is up, and unmounting when 'kombi' is down.

    Thanks, I guess I have misread other advice on the forums.  Even systemd.mount man page states:
    If x-systemd.device-timeout= is specified it may be used to configure how long systemd should wait for a device to show up before giving up on an entry from /etc/fstab.
    From this statement I would expect the remote filesystem to not be mounted if the other machine is down, but not to cause a local process to hang trying to access the unmounted directory.
    It looks like autofs may be the way to go - from the NFS wiki:
    Using autofs is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares.

  • [Solved] Systemd automounts /boot (was mlocate not traversing /boot)

    For some reason, mlocate does not index my /boot:
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /home/jason/Build/chroot/root/boot/vmlinuz-linux
    ┌─[Shiv ~ ]
    └─╼ sudo updatedb -U /boot
    [sudo] password for jason:
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /boot/vmlinuz-linux
    /boot/vmlinuz-linux-jwr
    ┌─[Shiv ~ ]
    └─╼ sudo updatedb
    ┌─[Shiv ~ ]
    └─╼ locate vmlinuz-linux
    /home/jason/Build/chroot/root/boot/vmlinuz-linux
    My /etc/updatedb.conf is the stock Arch one, /boot is obviously mounted (as the -U switch works), but a plain updatedb does not return any results from /boot.
    I recently moved my ESP from /boot/efi to /boot, and as this is the only machine exhibiting this behaviour, it leads me to suspect something is amiss here.
    My fstab:
    # ESP: /dev/sda1
    UUID=696A-09B3 /boot vfat defaults,relatime,discard 0 2
    # /dev/mapper/vgroup-lvroot
    UUID=1d2dfd7d-adeb-4786-ag98-c8fg675f8e2f / ext4 rw,relatime,discard,data=ordered 0 1
    # /dev/mapper/vgroup-lvhome
    UUID=50798021-94b5-4011-a593-9087gfhcd59b8 /home ext4 rw,relatime,discard 0 2
    Am I missing something obvious?
    # edit: updated thread title with the cause, as opposed to the symptom...

    WonderWoofy wrote:There is a mechanism in systemd (or maybe gummiboot) that mounts the ESP on /boot as a systemd autostart unit.  So it shows up as autofs, which mlocate does not venture into.
    Bingo!
    ┌─[Shiv ~ ]
    └─╼ mount | grep boot
    systemd-1 on /boot type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    /dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,discard)
    falconindy wrote:If there's one thing I've learned about remote debugging over the years, it's to not trust people.
    Especially Antipodeans
    lolilolicon wrote:I Googled for this and found this relevant talk in our (duh) wiki
    I spent some time yesterday searching, but missed this--to my shame
    65kid on the wiki wrote:* this feature isn't even documented in systemd yet
    Great. Any way to suppress this?

  • Systemd kiosk volatile $HOME

    How may systemd populate a volatile user $HOME from persistent storage, before users can login, or before Arch logs in automatically?
    The needed rsync call is trivial. I've attempted several unit/service files. I must not know something basic. The Arch OS is a charm and pure systemd. It just needs an automated rsync.
    The kiosk must avoid periodic sync (a la various AUR daemons). Users can bork it. $HOME in tmpfs leaves us in control of what lands on SSD. We can tell people to reboot a borked system. We also want to minimize slow writes and maximize SSD life.
    All we need is for systemd to rsync at the right stage in the boot sequence.
    Thanks Arch
    fstab,
    tmpfs /kioskuserhome tmpfs auto,uid=4000,gid=users,rw,nosuid,exec,noatime,size=300M,nr_inodes=30K 0 0
    boot setup,
    rsync --archive /home/kioskuserhome/ /

    Subject to correction, here's a solution. I hope it doesn't depend on timings. It works on our kiosk. Rsync is touchy about trailing slashes but works fine. We renamed kioskuserhome to ramhome. Another annoying fact is that systemd requires absolute pathnames in execution lines.
    So this rigging boots a kiosk with $HOME in tmpfs and automatically logs into tty1. From there, auto-starting X is trivia.
    $HOME in tmpfs is a nice speedup since apps are always reading and writing dotfiles.
    # /etc/fstab
    tmpfs /ramhome tmpfs auto,uid=2000,gid=users,rw,nosuid,exec,noatime,size=300M,nr_inodes=30k 0 0
    # /etc/systemd/system/ramhome-setup.service (UPDATE: see corrected unit below)
    [Unit]
    Description=Populate RAM user files from persistent store
    After=local-fs.target
    [Service]
    Type=oneshot
    ExecStart=/usr/bin/rsync --archive /home/ramhome/ /ramhome
    RemainAfterExit=no
    [Install]
    RequiredBy=getty.target
    And following automatic login advice but tweaking After and Install, we have
    # /etc/systemd/system/[email protected]
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    [Unit]
    Description=Autologin Getty on %I
    Documentation=man:agetty(8) man:systemd-getty-generator(8)
    Documentation=https://wiki.archlinux.org/index.php/Automatic_login_to_virtual_console
    After=systemd-user-sessions.service plymouth-quit-wait.service ramhome-setup.service
    # If additional gettys are spawned during boot then we should make
    # sure that this is synchronized before getty.target, even though
    # getty.target didn't actually pull it in.
    Before=getty.target
    IgnoreOnIsolate=yes
    # On systems without virtual consoles, don't start any getty. (Note
    # that serial gettys are covered by [email protected], not this
    # unit
    ConditionPathExists=/dev/tty0
    [Service]
    # the VT is cleared by TTYVTDisallocate
    ExecStart=-/sbin/agetty --noclear -a anyone %I 38400 linux
    Type=idle
    Restart=always
    RestartSec=0
    UtmpIdentifier=%I
    TTYPath=/dev/%I
    TTYReset=yes
    TTYVHangup=yes
    TTYVTDisallocate=yes
    KillMode=process
    IgnoreSIGPIPE=no
    # Unset locale for the console getty since the console has problems
    # displaying some internationalized messages.
    Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION=
    # Some login implementations ignore SIGTERM, so we send SIGHUP
    # instead, to ensure that login terminates cleanly.
    KillSignal=SIGHUP
    [Install]
    WantedBy=getty.target
    Then of course the obligatory commands
    # systemctl daemon-reload
    # systemctl enable ramhome-setup.service
    # systemctl disable getty@tty1
    # systemctl enable autologin@tty1
    and reboot.
    UPDATE. And we have been duly corrected. The revised service per systemd creator Lennart Poettering (1,2,3) follows.
    # /etc/systemd/system/ramhome-setup.service
    [Unit]
    Description=Populate RAM user files from persistent store
    Before=systemd-user-sessions.service
    [Service]
    Type=oneshot
    ExecStart=/usr/bin/rsync --archive /home/ramhome/ /ramhome
    [Install]
    WantedBy=multi-user.target
    Last edited by DaveCode (2013-03-05 18:11:17)

  • How to automount a home directory?

    Are there any docs that explain the steps necessary to configure iPlanet Directory Server 5.1 to automount a user's home directory? I'm using Solaris 8 & 9 clients.

    May help you:
    Calling VBScript from Remote Manager for Home Dir Creation

  • Questions on saving document, search result and location

    SAVE DOCUMENT
    Is it possible to save the document directly on the IFS's repository? Shall I save the document as local copy and then to upload the document on the IFS repository?
    SEARCH RESULT
    If I do "Find" + "on documents", I haven't unexpected results. But, in the result list, some documents are missing although they are mapping the research criterias.
    LOCATION
    In the results list, if I move the mouse cursor over a document link : I can read "http://fileserver:81/:12697" What does it means ? Where is stored this document ?
    null

    You should save the document as local copy and then to upload the document on the IFS repository.
    Some of the files might not have been indexed yet when you did search. Or possible you didn't have discovery permission to some of the files.
    "http://fileserver:81/:12697"
    It means the DocID of this document.

  • Systemd automount luks partition in background

    A bit of a technical story for systemd experts.
    Systemd causes a few seconds delay on boot when it automounts all fstab entries and one of those entries is an encrypted volume. The problem is when I mount a data partition which is really not important, i.e. it can wait until the system is completely booted. I can fix this by using noauto in crypttab and fstab or I can use a rc.local script to mount the partition manually. But how can I tell systemd this partition is not important and mounting this partition should never delay booting? Is it even possible with systemd?
    /etc/crypttab:
    data /dev/... /root/data.key
    /etc/fstab
    /dev/mapper/data /mnt/data ext4 rw,relatime 0 0

    Thanks aesiris, I've tried this but it's the same. When I don't mount the encrypted data partition on boot the system goes from text mode to X within 2 seconds. If I do mount the data partition the console goes from text mode to framebuffer (not sure how to call it but when you got a higher resolution text console) and then to X. Guess what I want is not possible with systemd.

  • Default save file location ignored for Outlook attachments

    Whenever I open an office attachment in Outlook, then edit and try to save, it always goes to "Libraries/Documents". I then have to do numerous clicks to get to my default location for every file.
    Is there somewhere to set the default for this. The "default file location" in Excel or Word are ignored.
    Thanks, Joe

    Try this:
    Open the Registry Editor (regedit) and browse to the following registry key:
    HKEY_CURRENT USER\Software\Microsoft\Office\15.0\Outlook\Options
    Create a new String value called "DefaultPath" in the right pane, modify the entry to the locate as you want.
    Another thread with the same topic for your reference:
    http://answers.microsoft.com/en-us/windows/forum/windows_7-files/default-save-location-does-it-have-to-be-a-library/11ee9557-78ba-4236-8200-ee4961f881ee
    Thanks.
    Tony Chen
    TechNet Community Support

  • Solaris LDAP without automount of /home/...

    hi,
    i need to setup an environment where users can login via ssh with their pubkey (it works fine). they are forced to execute only one command (which is in a centralized authorized_keys file on my server). user-authorization is done by ldap. my "problem" is that i do not want to have their home-directories mounted automatically. only when a user is loggin in the first time the directory should be created (or the best solution might be to have an "fake-home-dir") when users connect to the machine because there is NO need for them to have their home-dirs. on this server but i is necessary to that auth. is done by ldap!
    can someone give me an advise how to realize this?

    Have you tried:
    Mount the directory and authenticate when asked. You should have an option to have the login info added to the users keychain.
    Make an alias of the mounted share and add it to the users startup items.
    Just might work....
    PS If the server is not running when the user logs in, the Mac might hang....

  • [SOLVED] Amarok 2.7 will not Save configuration

    I have a bizarre issue with Amarok 2.7 running on KDE 4.10.1. I have a share on my server which is configured using Samba where all my music is stored. I have this share mounted at /home/user/Music on my laptop.
    My uid on the laptop is 1001, and the uid of my user account on the server is 1001. When I configure Amarok to use /home/user/Music as the source folder for the local collection it fails to save the configuration. That is to say that whether I use 'apply' 'OK' or both for that option, when I re-open the configuration dialogue nothing is selected. As a result the local collection is never scanned, and so there is no music available to the application.
    The share is mounted using this line in /etc/fstab:
    //server.home.dev/sharedfolders/Music/<user> /home/<user>/Music cifs x-systemd.automount,creds=/home/<user>/pncreds,uid=<user>,gid=users 0 0
    I have checked the ownership of the mounted Music directory, which appears to be correct. My user  has rwx permission on the directory, and on all of the sub-directories and contents.
    I thought I would re-apply the permissions just to be sure. When I attempted to do this from the client I got permission denied whether I tried to do it as my user or root. I tried re-applying the permissions on the underlying share. which was successful, but made no difference.
    As far as I can see everything is set up correctly so I cannot make sense of why the application cannot save or use the configuration. I am starting to wonder whether this is a bug in the application. Has anyone else seen this issue or one similar?
    Last edited by pfnorris (2013-04-05 15:26:13)

    I think this problem is releated to switching MariaDB rather than a permissions issue. Try the steps described in the news:
    https://www.archlinux.org/news/mariadb- … ositories/

  • Automount SSHFS drive in user-level systemd session

    Hello,
    I'm able to automount a network drive through SSHFS using the following .mount unit in the system-level systemd session:
    [Unit]
    Description=adama shared drive
    [Mount]
    What=[email protected]:/home/shared
    Where=/home/koral/remote/adama
    Type=fuse.sshfs
    Options=_netdev,noauto,users,idmap=user,IdentityFile=/home/koral/.ssh/id_rsa,allow_other
    [Install]
    WantedBy=default.target
    As is, the network drive is mounted at system start-up and it is read/write-able by any user logged into the local system.
    I'd like the drive to be mounted only when my $USER logs-in and read/write-able only by my $USER, so I considered moving the .mount unit to my user-level systemd session, but now the automounting fails with an unhelpful error message:
    systemd[1969]: Mounting adama shared drive...
    systemd[1969]: home-koral-remote-adama.mount mount process exited, code=exited status=1
    systemd[1969]: Failed to mount adama shared drive.
    systemd[1969]: Unit home-koral-remote-adama.mount entered failed state
    I guess there is a permission issue somehow, could you please help figuring it out ?
    Note: I'm still using systemd-204 as the user-level session is kind of broken in later versions as described here.
    Kind regards.
    Last edited by koral (2014-03-30 17:54:45)

    xtian wrote:I can mount using the manual command `$sshfs [email protected]:/ /mnt/mrwizard.local`
    According to the above your username is xtian, which it isn't in your fstab entry:
    xtian wrote:[email protected]:/ /mnt/mrwizard.local ...
    So without having looked for further errors nor knowing anything about sshfs, I would suppose to change this.
    Sometimes simple spelling errors are actually the hardest to solve. – Like I always try to '#include <some_library.c>'.

  • Systemd doesn't umount (encrypted) /home and /tmp on shutdown

    Hi all,
    as this is my first post in this BBS, I hope I'm actually posting in the correct forum. I also did some research but couldn't really find answers.
    I have a problem with systemd on shutdown. It doesn't unmount my encrypted home partition (and does not close the LUKS partition) and the /tmp partition. The corresponding output from journalctl would be this:
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /data...
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /boot...
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /home...
    Oct 09 16:08:18 failenovo umount[3995]: umount: /home: target is busy.
    Oct 09 16:08:18 failenovo umount[3995]: (In some cases useful info about processes that use
    Oct 09 16:08:18 failenovo umount[3995]: the device is found by lsof(8) or fuser(1))
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting Temporary Directory...
    Oct 09 16:08:18 failenovo systemd[1]: home.mount mount process exited, code=exited status=32
    Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting /home.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab...
    Oct 09 16:08:18 failenovo systemd[1]: Stopped File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping /sys/devices/virtual/block/dm-1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/sda1.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounted /boot.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partuuid/28e18189-6b46-40b5-82f8-d550ee3df47a.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partlabel/Linux\x20swap.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000cca615e3f206-part1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/ata-HITACHI_HTS543232A7A384_E2434243JK29XK-part1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-uuid/4903864c-36f8-4f05-a722-ed726c9ae492.
    Oct 09 16:08:18 failenovo umount[3997]: umount: /tmp: target is busy.
    Oct 09 16:08:18 failenovo umount[3997]: (In some cases useful info about processes that use
    Oct 09 16:08:18 failenovo umount[3997]: the device is found by lsof(8) or fuser(1))
    Oct 09 16:08:18 failenovo systemd[1]: tmp.mount mount process exited, code=exited status=32
    Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting Temporary Directory.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounted /data.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems (Pre).
    Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems (Pre).
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Remount Root and Kernel File Systems...
    Oct 09 16:08:18 failenovo systemd[1]: Stopped Remount Root and Kernel File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Starting Shutdown.
    Oct 09 16:08:18 failenovo systemd[1]: Reached target Shutdown.
    Oct 09 16:08:23 failenovo systemd-cryptsetup[3989]: Failed to deactivate: Device or resource busy
    Oct 09 16:08:23 failenovo systemd[1]: [email protected]: control process exited, code=exited status=1
    Oct 09 16:08:23 failenovo systemd[1]: Stopped Cryptography Setup for home.
    Oct 09 16:08:23 failenovo systemd[1]: Unit [email protected] entered failed state.
    Oct 09 16:08:23 failenovo systemd[1]: Starting Unmount All Filesystems.
    Oct 09 16:08:23 failenovo systemd[1]: Reached target Unmount All Filesystems.
    Now, with the usual sysv-init this wouldn't be a problem but with systemd (which I'm new to) this poses a problem. I don't know where to start debugging this issue, really. I haven't found a way to run a script directly before and after the umount.target units starts so I can't really see which files are open or what the problem is at this point.
    Is it possible to drop to a shell on such errors and inspect the problem manually? Or does anyone have a suggestion why systemd doesn't want to unmount these filesystems?
    Here's my /etc/fstab:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/root LABEL=ROOT
    UUID=27fed041-7765-4f63-a895-a7592113165b / ext4 rw,relatime,data=ordered,discard 0 1
    # /dev/mapper/home LABEL=HOME
    UUID=a9395b0a-e3f8-41d7-9feb-d433173fd5ab /home ext4 rw,relatime,data=ordered,discard 0 2
    # /dev/sdb1
    UUID=1573-8C74 /boot/ vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda1 LABEL=SWAP
    UUID=f5097167-6e12-4548-8bef-5f83942a1848 none swap defaults 0 0
    # /dev/sda2 LABEL=DATA
    UUID=dffd1518-d3b5-4d05-8b13-76e6fd841963 /data ext4 defaults 0 2
    and my /etc/crypttab:
    # <name> <device> <password> <options>
    home UUID=01f3da5d-1ca0-4bf2-b5a1-cfe69c597707 /etc/keys/home.key luks,discard
    If you need more information, please do tell! Thanks in advance.
    Cheers,
    gegenschall

    I think the /home part of the issue for me is at least partially due to how I have mpd configured.  I start it with my X session and it persists after I log out, keeping a few files in my home folder open.  If I make sure it is not running, log out to LightDM, and use its menu to reboot, I do not get a journal message about /home.  If I kill mpd, but instead issue a `systemctl reboot/poweroff` command from a terminal in X, the problem returns.  Is this normal?  I guess I expected everything to be automatically cleaned up.
    /tmp, on the other hand, remains a mystery.  If I remove it from my /etc/fstab - to use the default tmp.mount (tmpfs) systemd provides - the problem goes away.  But if I keep it as is, and do something silly like replace /bin/umount with this:
    #!/bin/sh
    /bin/test "$1" = "/tmp" && /bin/date -Ins >> /umount-tmp.log
    /bin/test "$1" = "/tmp" && /bin/lsof /tmp >> /umount-tmp.log
    /bin/umount.real "$@"
    all I get is a list of times.
    Also, I tried following the steps here (Shutdown Completes Eventually), but the output mostly mirrors what I get from journalctl:
    [ 219.132058] systemd[1]: Stopping Local File Systems.
    [ 219.132062] systemd[1]: local-fs.target changed active -> dead
    [ 219.132066] systemd[1]: Job local-fs.target/stop finished, result=done
    [ 219.132091] systemd[1]: Stopped target Local File Systems.
    [ 219.132103] systemd[1]: Unmounting /home...
    [ 219.132136] systemd[1]: About to execute: /bin/umount /home
    [ 219.132329] systemd[1]: Forked /bin/umount as 908
    [ 219.132402] systemd[1]: home.mount changed mounted -> unmounting
    [ 219.132427] systemd[1]: Unmounting /storage...
    [ 219.132480] systemd[1]: About to execute: /bin/umount /storage
    [ 219.132735] systemd[1]: Forked /bin/umount as 909
    [ 219.132805] systemd[1]: storage.mount changed mounted -> unmounting
    [ 219.132825] systemd[1]: Unmounting /tmp...
    [ 219.132872] systemd[1]: About to execute: /bin/umount /tmp
    [ 219.133047] systemd[1]: Forked /bin/umount as 910
    [ 219.133109] systemd[1]: tmp.mount changed mounted -> unmounting
    [ 219.133136] systemd[1]: Unmounting /boot...
    [ 219.133190] systemd[1]: About to execute: /bin/umount /boot
    [ 219.133355] systemd[909]: Executing: /bin/umount /storage
    [ 219.133388] systemd[1]: Forked /bin/umount as 911
    [ 219.133452] systemd[1]: boot.mount changed mounted -> unmounting
    [ 219.133676] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.134256] systemd[906]: Executing: /usr/lib/systemd/systemd-random-seed save
    [ 219.134550] systemd[908]: Executing: /bin/umount /home
    [ 219.135143] systemd[1]: Received SIGCHLD from PID 906 (systemd-random-).
    [ 219.135170] systemd[1]: Got SIGCHLD for process 906 (systemd-random-)
    [ 219.135222] systemd[1]: Child 906 died (code=exited, status=0/SUCCESS)
    [ 219.135226] systemd[1]: Child 906 belongs to systemd-random-seed.service
    [ 219.135235] systemd[1]: systemd-random-seed.service: control process exited, code=exited status=0
    [ 219.135292] systemd[907]: Executing: /sbin/swapoff /dev/dm-2
    [ 219.135462] systemd[910]: Executing: /bin/umount /tmp
    [ 219.135487] systemd[1]: systemd-random-seed.service got final SIGCHLD for state stop
    [ 219.135528] systemd[1]: systemd-random-seed.service changed stop -> dead
    [ 219.135582] systemd[911]: Executing: /bin/umount /boot
    [ 219.135622] systemd[1]: Job systemd-random-seed.service/stop finished, result=done
    [ 219.135666] systemd[1]: Stopped Load/Save Random Seed.
    [ 219.135695] systemd[1]: Unmounting /var...
    [ 219.135730] systemd[1]: About to execute: /bin/umount /var
    [ 219.135974] systemd[1]: Forked /bin/umount as 914
    [ 219.136050] systemd[1]: var.mount changed mounted -> unmounting
    [ 219.136290] systemd[1]: Accepted connection on private bus.
    [ 219.136332] systemd[1]: Accepted connection on private bus.
    [ 219.136529] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.136584] systemd[914]: Executing: /bin/umount /var
    [ 219.136890] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.137193] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.137222] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.175076] systemd[1]: Received SIGCHLD from PID 754 (sudo).
    [ 219.175102] systemd[1]: Got SIGCHLD for process 754 (sudo)
    [ 219.175155] systemd[1]: Child 754 died (code=exited, status=129/n/a)
    [ 219.200239] systemd[1]: Received SIGCHLD from PID 910 (umount).
    [ 219.200267] systemd[1]: Got SIGCHLD for process 908 (umount)
    [ 219.200338] systemd[1]: Child 908 died (code=exited, status=32/n/a)
    [ 219.200342] systemd[1]: Child 908 belongs to home.mount
    [ 219.200347] systemd[1]: home.mount mount process exited, code=exited status=32
    [ 219.200357] systemd[1]: home.mount changed unmounting -> mounted
    [ 219.200362] systemd[1]: Job home.mount/stop finished, result=failed
    [ 219.200407] systemd[1]: Failed unmounting /home.
    [ 219.200454] systemd[1]: Got SIGCHLD for process 910 (umount)
    [ 219.200524] systemd[1]: Child 910 died (code=exited, status=32/n/a)
    [ 219.200527] systemd[1]: Child 910 belongs to tmp.mount
    [ 219.200532] systemd[1]: tmp.mount mount process exited, code=exited status=32
    [ 219.200540] systemd[1]: tmp.mount changed unmounting -> mounted
    [ 219.200544] systemd[1]: Job tmp.mount/stop finished, result=failed
    [ 219.200571] systemd[1]: Failed unmounting /tmp.
    [ 219.200607] systemd[1]: Got SIGCHLD for process 914 (umount)
    [ 219.200666] systemd[1]: Child 914 died (code=exited, status=32/n/a)
    [ 219.200669] systemd[1]: Child 914 belongs to var.mount
    [ 219.200673] systemd[1]: var.mount mount process exited, code=exited status=32
    [ 219.200681] systemd[1]: var.mount changed unmounting -> mounted
    [ 219.200685] systemd[1]: Job var.mount/stop finished, result=failed
    [ 219.200711] systemd[1]: Failed unmounting /var.
    [ 219.200737] systemd[1]: Stopping File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524...
    [ 219.200763] systemd[1]: systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service changed exited -> dead
    [ 219.200769] systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service/stop finished, result=done
    [ 219.200797] systemd[1]: Stopped File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524.
    [ 219.200816] systemd[1]: Redirecting stop request from dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.device to sys-devices-virtual-block-dm\x2d6.device.
    [ 219.200823] systemd[1]: Stopping /sys/devices/virtual/block/dm-6.
    [ 219.200876] systemd[1]: Accepted connection on private bus.
    [ 219.201099] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.201186] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.201483] systemd[1]: Accepted connection on private bus.
    [ 219.201642] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.201716] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.204043] systemd[1]: Accepted connection on private bus.
    [ 219.204142] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.204219] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.234497] systemd[1]: dev-mapper-linux\x2dswap.swap changed active -> dead
    [ 219.234606] systemd[1]: Job dev-mapper-linux\x2dswap.swap/stop finished, result=done
    [ 219.234657] systemd[1]: Deactivated swap /dev/mapper/linux-swap.
    [ 219.234674] systemd[1]: dev-linux-swap.swap changed active -> dead
    [ 219.234751] systemd[1]: Job dev-linux-swap.swap/stop finished, result=done
    [ 219.234805] systemd[1]: Deactivated swap /dev/linux/swap.
    [ 219.234815] systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap changed active -> dead
    [ 219.234970] systemd[1]: Job dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap/stop finished, result=done
    [ 219.235007] systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-DevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.
    [ 219.235017] systemd[1]: dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap changed active -> dead
    [ 219.235097] systemd[1]: Job dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap/stop finished, result=done
    [ 219.235126] systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-linux-swap.
    [ 219.235135] systemd[1]: dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap changed active -> dead
    [ 219.235214] systemd[1]: Job dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap/stop finished, result=done
    [ 219.235244] systemd[1]: Deactivated swap /dev/disk/by-uuid/f8b1e59e-9804-44f0-af79-66810ee49206.
    [ 219.235297] systemd[1]: Received SIGCHLD from PID 907 (swapoff).
    [ 219.235323] systemd[1]: Got SIGCHLD for process 907 (swapoff)
    [ 219.235390] systemd[1]: Child 907 died (code=exited, status=0/SUCCESS)
    [ 219.235394] systemd[1]: Child 907 belongs to dev-dm\x2d2.swap
    [ 219.235399] systemd[1]: dev-dm\x2d2.swap swap process exited, code=exited status=0
    [ 219.235410] systemd[1]: dev-dm\x2d2.swap changed deactivating -> dead
    [ 219.235956] systemd[1]: Job dev-dm\x2d2.swap/stop finished, result=done
    [ 219.236044] systemd[1]: Deactivated swap /dev/dm-2.
    [ 219.236131] systemd[1]: Got SIGCHLD for process 911 (umount)
    [ 219.236192] systemd[1]: Child 911 died (code=exited, status=0/SUCCESS)
    [ 219.236196] systemd[1]: Child 911 belongs to boot.mount
    [ 219.236201] systemd[1]: boot.mount mount process exited, code=exited status=0
    [ 219.236210] systemd[1]: boot.mount changed unmounting -> dead
    [ 219.236294] systemd[1]: Job boot.mount/stop finished, result=done
    [ 219.236322] systemd[1]: Unmounted /boot.
    [ 219.236360] systemd[1]: Received SIGCHLD from PID 911 (n/a).
    [ 219.236413] systemd[1]: Accepted connection on private bus.
    [ 219.236551] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.237196] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.237321] systemd[1]: Accepted connection on private bus.
    [ 219.237463] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.237814] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.238324] systemd[1]: Received SIGCHLD from PID 909 (umount).
    [ 219.238348] systemd[1]: Got SIGCHLD for process 909 (umount)
    [ 219.238404] systemd[1]: Child 909 died (code=exited, status=0/SUCCESS)
    [ 219.238407] systemd[1]: Child 909 belongs to storage.mount
    [ 219.238412] systemd[1]: storage.mount mount process exited, code=exited status=0
    [ 219.238420] systemd[1]: storage.mount changed unmounting -> dead
    [ 219.238509] systemd[1]: Job storage.mount/stop finished, result=done
    [ 219.238540] systemd[1]: Unmounted /storage.
    [ 219.238556] systemd[1]: Stopping Local File Systems (Pre).
    [ 219.238562] systemd[1]: local-fs-pre.target changed active -> dead
    [ 219.238566] systemd[1]: Job local-fs-pre.target/stop finished, result=done
    [ 219.238592] systemd[1]: Stopped target Local File Systems (Pre).
    [ 219.238604] systemd[1]: Stopping Remount Root and Kernel File Systems...
    [ 219.238627] systemd[1]: systemd-remount-fs.service changed exited -> dead
    [ 219.238631] systemd[1]: Job systemd-remount-fs.service/stop finished, result=done
    [ 219.238656] systemd[1]: Stopped Remount Root and Kernel File Systems.
    [ 219.238673] systemd[1]: Starting Shutdown.
    [ 219.238676] systemd[1]: shutdown.target changed dead -> active
    [ 219.238679] systemd[1]: Job shutdown.target/start finished, result=done
    [ 219.238703] systemd[1]: Reached target Shutdown.
    [ 219.239263] systemd[1]: Accepted connection on private bus.
    [ 219.239382] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.239752] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.630816] systemd[1]: Received SIGCHLD from PID 486 (at-spi-bus-laun).
    [ 219.630840] systemd[1]: Got SIGCHLD for process 486 (at-spi-bus-laun)
    [ 219.630896] systemd[1]: Child 486 died (code=exited, status=0/SUCCESS)
    [ 219.668697] systemd[1]: Received SIGCHLD from PID 449 (X).
    [ 219.668725] systemd[1]: Got SIGCHLD for process 449 (X)
    [ 219.668781] systemd[1]: Child 449 died (code=exited, status=0/SUCCESS)
    [ 219.669379] systemd[1]: Accepted connection on private bus.
    [ 219.669545] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.669606] systemd[1]: lightdm.service: cgroup is empty
    [ 219.669636] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 220.420041] systemd[1]: Received SIGCHLD from PID 845 (sleep).
    [ 220.420064] systemd[1]: Got SIGCHLD for process 845 (sleep)
    [ 220.420103] systemd[1]: Child 845 died (code=exited, status=0/SUCCESS)
    [ 221.914117] systemd[1]: Received SIGCHLD from PID 545 (dbus-launch).
    [ 221.914141] systemd[1]: Got SIGCHLD for process 545 (dbus-launch)
    [ 221.914184] systemd[1]: Child 545 died (code=exited, status=0/SUCCESS)
    [ 221.914458] systemd[1]: Received SIGCHLD from PID 483 (dbus-launch).
    [ 221.914486] systemd[1]: Got SIGCHLD for process 483 (dbus-launch)
    [ 221.914529] systemd[1]: Child 483 died (code=exited, status=0/SUCCESS)
    [ 221.915102] systemd[1]: Accepted connection on private bus.
    [ 221.915222] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 221.915328] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 223.957616] systemd[1]: Received SIGCHLD from PID 904 (systemd-cryptse).
    [ 223.957639] systemd[1]: Got SIGCHLD for process 904 (systemd-cryptse)
    [ 223.957707] systemd[1]: Child 904 died (code=exited, status=1/FAILURE)
    [ 223.957712] systemd[1]: Child 904 belongs to systemd-cryptsetup@crypt\x2dhome.service
    [ 223.957720] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service: control process exited, code=exited status=1
    [ 223.957782] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service got final SIGCHLD for state stop
    [ 223.957818] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service changed stop -> failed
    [ 223.957904] systemd[1]: Job systemd-cryptsetup@crypt\x2dhome.service/stop finished, result=done
    [ 223.957917] systemd[1]: Stopped Cryptography Setup for crypt-home.
    [ 223.957928] systemd[1]: Unit systemd-cryptsetup@crypt\x2dhome.service entered failed state.
    [ 223.958243] systemd[1]: Accepted connection on private bus.
    [ 223.958397] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 223.958509] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 224.016365] systemd[1]: Received SIGCHLD from PID 905 (systemd-cryptse).
    [ 224.016390] systemd[1]: Got SIGCHLD for process 905 (systemd-cryptse)
    [ 224.016447] systemd[1]: Child 905 died (code=exited, status=1/FAILURE)
    [ 224.016451] systemd[1]: Child 905 belongs to systemd-cryptsetup@crypt\x2dlinux.service
    [ 224.016457] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service: control process exited, code=exited status=1
    [ 224.016529] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service got final SIGCHLD for state stop
    [ 224.016565] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service changed stop -> failed
    [ 224.016661] systemd[1]: Job systemd-cryptsetup@crypt\x2dlinux.service/stop finished, result=done
    [ 224.016676] systemd[1]: Stopped Cryptography Setup for crypt-linux.
    [ 224.016687] systemd[1]: Unit systemd-cryptsetup@crypt\x2dlinux.service entered failed state.
    [ 224.016703] systemd[1]: Starting Unmount All Filesystems.
    [ 224.016707] systemd[1]: umount.target changed dead -> active
    [ 224.016711] systemd[1]: Job umount.target/start finished, result=done
    [ 224.016717] systemd[1]: Reached target Unmount All Filesystems.
    [ 224.016728] systemd[1]: Starting Final Step.
    [ 224.016731] systemd[1]: final.target changed dead -> active
    [ 224.016734] systemd[1]: Job final.target/start finished, result=done
    [ 224.016742] systemd[1]: Reached target Final Step.
    [ 224.016754] systemd[1]: Starting Reboot...
    [ 224.016866] systemd[1]: About to execute: /usr/bin/systemctl --force reboot
    [ 224.017057] systemd[1]: Forked /usr/bin/systemctl as 928
    [ 224.017193] systemd[1]: systemd-reboot.service changed dead -> start
    [ 224.018230] systemd[928]: Executing: /usr/bin/systemctl --force reboot
    [ 224.018328] systemd[1]: Accepted connection on private bus.
    [ 224.018435] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 224.018504] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 224.019495] systemd[1]: Accepted connection on private bus.
    [ 224.019712] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reboot() on /org/freedesktop/systemd1
    [ 224.019734] systemd[1]: Shutting down.
    [ 224.023022] systemd[1]: Hardware watchdog 'NV_TCO', version 0
    [ 224.023031] systemd[1]: Failed to set timeout to 600s: Invalid argument
    [ 224.023033] nv_tco: Unexpected close, not stopping watchdog!
    [ 225.162099] systemd-journald[215]: Received SIGTERM
    [ 225.515048] EXT4-fs (dm-6): re-mounted. Opts: (null)
    [ 225.687382] EXT4-fs (dm-4): re-mounted. Opts: (null)
    [ 225.796081] EXT4-fs (dm-3): re-mounted. Opts: (null)
    [ 225.915129] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 225.919881] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 225.919911] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 226.283469] EXT4-fs (dm-1): re-mounted. Opts: data=ordered

Maybe you are looking for