Failed To Unmount messages at shutdown

If none of the more specific forums is the right place to ask

Failed To Unmount messages at shutdown

Postby Shamak » 2018-04-14 16:38

Hi everybody. I'm on Stretch with the Gnome desktop. Just installed a few days ago. I encrypted my home folder and swap using this Debian wiki page. I'm getting some intermittent red shutdown messages.

Code: Select all
Failed to unmount /run/user/116
Failed to unmount /run/user/1000
Failed to unmount /home/<username>

And there's lots of other green messages mixed in there in between and after the messages but the /run/user/116 message is first. Everything seems to work fine regardless. No error messages. Boot up is normal. Even though this is a recent installation of Stretch I've been on Stretch before but without encrypting the home folder and swap and never got these messages.

There's a number of threads out there which have to do with systemd and seem to relate to my issue. Here are some of them.

https://github.com/systemd/systemd/issu ... -127913028
https://github.com/systemd/systemd/issues/1507
https://bugs.debian.org/cgi-bin/bugrepo ... bug=801361
https://bbs.archlinux.org/viewtopic.php?id=200469

There's this post which I hope applies to me saying that you can get Failed To Unmount mesages without it being an error.

viewtopic.php?f=10&t=14084&p=64352&hilit=failed+unmount+shutdown#p64352

No fsck when I boot up. No mention of drives that are not clean.

I should say that after encrypting my home folder and swap I started getting the red message "Failed: Stopped (with errors) /dev/dm-0" I found a thread with someone saying he got a dirty file system on reboot. So I found that the error message would go away if I turned off the encrypted swap manually. So now I have the file /etc/systemd/system/custom-shutdown.service:

Code: Select all
[Unit]
Description=Shutdown Swap
Wants=shutdown.target reboot.target
Before=shutdown.target reboot.target

[Service]
Type=oneshot
ExecStart=/sbin/swapoff /dev/mapper/cryptswap1

[Install]
WantedBy=reboot.target shutdown.target


After adding this file the dm-0 message went away but now I get the intermittent messages I'm asking about.

Not sure if these are relevant to /run/user/116 but here is /etc/group:

Code: Select all
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:<username>
floppy:x:25:<username>
tape:x:26:
sudo:x:27:<username>
audio:x:29:pulse,<username>
dip:x:30:<username>
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:<username>
sasl:x:45:
plugdev:x:46:<username>
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-timesync:x:102:
systemd-network:x:103:
systemd-resolve:x:104:
systemd-bus-proxy:x:105:
input:x:106:
crontab:x:107:
netdev:x:108:<username>
ssl-cert:x:109:
rtkit:x:110:
messagebus:x:111:
ssh:x:112:
bluetooth:x:113:<username>
lpadmin:x:114:<username>
geoclue:x:115:
pulse:x:116:
pulse-access:x:117:
scanner:x:118:saned,<username>
avahi:x:119:
colord:x:120:
saned:x:121:
Debian-gdm:x:122:
<username>:x:1000:


And here is /etc/passwd:

Code: Select all
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
systemd-timesync:x:100:102:systemd Time Synchronization,,,:/run/systemd:/bin/false
systemd-network:x:101:103:systemd Network Management,,,:/run/systemd/netif:/bin/false
systemd-resolve:x:102:104:systemd Resolver,,,:/run/systemd/resolve:/bin/false
systemd-bus-proxy:x:103:105:systemd Bus Proxy,,,:/run/systemd:/bin/false
_apt:x:104:65534::/nonexistent:/bin/false
rtkit:x:105:110:RealtimeKit,,,:/proc:/bin/false
dnsmasq:x:106:65534:dnsmasq,,,:/var/lib/misc:/bin/false
messagebus:x:107:111::/var/run/dbus:/bin/false
usbmux:x:108:46:usbmux daemon,,,:/var/lib/usbmux:/bin/false
geoclue:x:109:115::/var/lib/geoclue:/bin/false
speech-dispatcher:x:110:29:Speech Dispatcher,,,:/var/run/speech-dispatcher:/bin/false
pulse:x:111:116:PulseAudio daemon,,,:/var/run/pulse:/bin/false
avahi:x:112:119:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
colord:x:113:120:colord colour management daemon,,,:/var/lib/colord:/bin/false
saned:x:114:121::/var/lib/saned:/bin/false
hplip:x:115:7:HPLIP system user,,,:/var/run/hplip:/bin/false
Debian-gdm:x:116:122:Gnome Display Manager:/var/lib/gdm3:/bin/false
<username>:x:1000:1000:<username>,,,:/home/<username>:/bin/bash


Thanks for your help! What do you think? Can I ignore this?
Shamak
 
Posts: 3
Joined: 2018-04-14 00:33

Re: Failed To Unmount messages at shutdown

Postby dryden » 2018-04-15 06:37

I hope something can solve your issues, but the messages


Those /run mount points are tmpfs, so obviously they are lost on shutdown and hence no fsck problems.

The /home/<user> directory is your eCryptFS mount.

It is of course a direct mapping to your underlying hardware device (or at least filesystem/volume) so as long as that underlying volume is dismounted (e.g. /) there is no issue with possible outstanding writes, the chance of which is low anyway.

So if your root filesystem actually gets properly dismounted, there is no issue.

I don't know how to troubleshoot the shutdown sequence myself, but systemd is extremely good at not being able to dismount stuff.
dryden
 
Posts: 80
Joined: 2015-02-04 08:54

Re: Failed To Unmount messages at shutdown

Postby Shamak » 2018-04-19 15:56

Thanks for the reply dryden. I've decided to not encrypt my home folder. But thanks for the info. :)
Shamak
 
Posts: 3
Joined: 2018-04-14 00:33

Re: Failed To Unmount messages at shutdown

Postby Wheelerof4te » 2018-04-19 19:09

Yea, I see those messages sometimes. Nothing to worry about.
User avatar
Wheelerof4te
 
Posts: 1041
Joined: 2015-08-30 20:14


Return to General Questions

Who is online

Users browsing this forum: No registered users and 2 guests

fashionable