[systemd]Unmount error at shutdown + moc

Question

Hi there,
I have recently noticed many errors using journalctl:
systemd[1]: Failed unmounting /home.
It's always the same issue. I tried to reproduce it and I found what's going on.
When I shutdown my computer without starting moc (music on console), I have no message. If I start moc and if I use $(mocp -x) then (this command closes the server), I have no issue.
But when I shutdown my computer, without "killing" moc server before, I have the previous message. I reproduced it several times.
It's strange because I see no difference when the computer halts.
There's a similar message here: https://bbs.archlinux.org/viewtopic.php … 4#p1336594 It might be related.
I'm almost sure it started with systemd-207-5.
My fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
#tmpfs
tmpfs /tmp tmpfs nodev,nosuid,size=1G 0 0
# /dev/sda5
UUID=413f313a-ef11-43c9-b9f9-e75ae0a4c17e / ext4 defaults,noatime,rw 0 1
# /dev/sda6
UUID=7e092eea-334c-484a-a751-592a3007e6f8 none swap defaults 0 0
# /dev/sda7
UUID=ab0248ee-088b-4383-bc7b-de23b4903fed /boot ext2 defaults,rw 0 2
# /dev/sda8
UUID=e4e94f7b-7d74-41bf-8ac7-ff59bb80d46a /home ext4 defaults,noatime,rw 0 2
# /dev/sda9
UUID=dff26b18-2847-409c-9b21-b7f230f17daf /mnt/public ext4 defaults,noatime,rw,data=ordered 0 2
# USB
UUID=138D-6D32 /mnt/USB1 vfat users,noauto,noatime,fmask=133,dmask=022 0 0
My mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ahci"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Answer 1

king.flasher.dave wrote:okay, pretty nice!
But I'd like it to happen AFTER SIGTERM, because there might be processes still using the containers/devices. How can that be accomplished?
Ok. I don't know what exactly what you mean by SIGTERM (can't find that in my journalctl logs), but I presume you simply mean it to unmount after mpd/any-other-service has been stopped?
The answers I got on the mailing list were hard to understand for me in the first place, but at least I now figured out a new way of doing the (un)mounting of tc volumes with an advantage:
As Matthew pointed out, it may be sensible to use truecrypt for the mapping (to /dev/mapper/truecrypt1) only and let the mounting be done via fstab (thus, fsck's should be more easily possible) via this service & a corresponding entry in fstab:
[Unit]
Description=Truecrypt Setup for /dev/sda4
DefaultDependencies=no
Conflicts=umount.target
Before=umount.target
Before=cryptsetup.target
After=systemd-readahead-collect.service systemd-readahead-replay.service
BindsTo=dev-mapper-truecrypt1.device
[Service]
RemainAfterExit=yes
StandardInput=tty-force
ExecStart=/usr/bin/truecrypt --filesystem=none --slot=1 /dev/sda4
ExecStop=/usr/bin/truecrypt --filesystem=none -d /dev/sda4
[Install]
WantedBy=cryptsetup.target
/etc/fstab:
/dev/mapper/truecrypt1 /home ext4 defaults 0 0
But I think this still means that /home ts unmounted before mpd is shutdown, which I don't understand. OTOH, mpd continues playing the song it was interrupted during shutdown correctly after the reboot… weird