You are not logged in.

#1 2020-06-25 10:57:46

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Failed unmounting /home on shutdown

I am seeing a warning indicting, "Failed unmounting /home" just before my system goes down.  It is consistently happening on everyone shutdown inspecting the journal.  I am unsure what is causing it and why systemd isn't pausing to wait for whatever it is to stop.

Any thoughts are appreciated.

Link to complete journalctl when shutdown is initiated.

Relevant pieces of journalctl showing the error:

...
Jun 24 22:20:13 ease systemd[1]: Stopped Initialize hardware monitoring sensors.
Jun 24 22:20:13 ease systemd[1]: session-1.scope: Succeeded.
Jun 24 22:20:13 ease systemd[1]: Stopped Session 1 of user facade.
Jun 24 22:20:13 ease systemd[1]: Unmounting /home...
Jun 24 22:20:13 ease systemd[1]: Stopping Login Service...
Jun 24 22:20:13 ease systemd[1]: Stopping User Manager for UID 1000...
Jun 24 22:20:13 ease systemd-logind[568]: Removed session 1.
Jun 24 22:20:13 ease systemd[609]: Stopped target Main User Target.
Jun 24 22:20:13 ease systemd[609]: Stopping Accessibility services bus...
Jun 24 22:20:13 ease umount[1094954]: umount: /home: target is busy.
Jun 24 22:20:13 ease gvfsd[745]: A connection to the bus can't be made
Jun 24 22:20:13 ease systemd[609]: Stopping D-Bus User Message Bus...
Jun 24 22:20:13 ease gpg-agent[217307]: SIGTERM received - shutting down ...
Jun 24 22:20:13 ease gvfsd[215849]: A connection to the bus can't be made
Jun 24 22:20:13 ease systemd[609]: Stopping GnuPG cryptographic agent and passphrase cache...
Jun 24 22:20:13 ease systemd[609]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Jun 24 22:20:13 ease systemd[609]: Stopping Virtual filesystem service...
Jun 24 22:20:13 ease systemd[609]: Stopping Virtual filesystem service - digital camera monitor...
Jun 24 22:20:13 ease systemd[609]: Stopping Virtual filesystem metadata service...
Jun 24 22:20:13 ease systemd[609]: Stopping Virtual filesystem service - disk device monitor...
Jun 24 22:20:13 ease systemd[1]: home.mount: Mount process exited, code=exited, status=32/n/a
Jun 24 22:20:13 ease systemd[1]: Failed unmounting /home.

I am allowing systemd to manage mounts, /etc/fstab:

tmpfs /scratch  tmpfs size=29G,nodev,lazytime  0 0

LABEL=boot             /boot         ext4  defaults  0 1
LABEL=home             /home         ext4  noauto,x-systemd.automount  0 2
LABEL=lxc              /var/lib/lxc  ext4  noauto,x-systemd.automount  0 2
LABEL=incoming         /incoming     f2fs  noauto,x-systemd.automount,nodiscard  0 0
/dev/mapper/data-crypt /mnt/data     ext4  noauto,x-systemd.automount  0 0

EDIT: Should have mentioned that googling shows other report of this but without a cause (speculation around pulseaudio seems common).  I am also seeing a failure relating to pulseaudio.service but am unsure if that is causative.  I tried killing all PIDs assicoated with pulse-audio (ps aux | grep pulse) and rebooted after I was sure none were running and saw the same error.

Last edited by graysky (2020-06-25 11:00:48)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2020-06-25 11:30:31

loqs
Member
Registered: 2014-03-06
Posts: 10,969

Re: Failed unmounting /home on shutdown

Try running lsof on /home as late in the shutdown process as possible to see if there are any open files.
Edit:
Try adding an override for home.mount with

OnFailure=lsof.service

Last edited by loqs (2020-06-25 11:34:30)

Offline

#3 2020-06-25 12:35:26

zpg443
Member
Registered: 2016-12-03
Posts: 83

Re: Failed unmounting /home on shutdown

[deleted]

Last edited by zpg443 (2020-06-25 12:42:25)

Offline

#4 2020-06-25 13:21:11

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 23,689
Website

Re: Failed unmounting /home on shutdown

What systemd user services are you running?


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2020-06-25 14:02:31

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

@loqs - I think the idea of getting a service to store lsof output.  I will try it.
@Trilby - Based on the jorunalctl output, I was thinking psd might be causing this, but I get the same error on shutdown with I stop it manually prior.

Here are the user units that are not in the static category:

UNIT FILE                           STATE    VENDOR PRESET
psd.service                         enabled  enabled
dirmngr.socket                      enabled  enabled
gpg-agent-browser.socket            enabled  enabled
gpg-agent-extra.socket              enabled  enabled
gpg-agent-ssh.socket                enabled  enabled
gpg-agent.socket                    enabled  enabled
p11-kit-server.socket               enabled  enabled
pulseaudio.socket                   enabled  enabled

Last edited by graysky (2020-06-25 14:04:38)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#6 2020-06-25 14:15:45

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 8,197

Re: Failed unmounting /home on shutdown

Are you shutting down from a graphical session ?

If so, try logging out of any X sessions, then login as root on console and issue poweroff (or similar ).


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#7 2020-06-25 14:26:30

merlock
Member
Registered: 2018-10-30
Posts: 79

Re: Failed unmounting /home on shutdown

FWIW, I looked through my whole journal (back to 1 Apr), and don't have any instance of unmount fails. 

I also use PSD, but don't have puleaudio installed.


It's a big club...and you ain't in it -- George Carlin
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '

Offline

#8 2020-06-25 16:28:27

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

loqs wrote:

Try running lsof on /home as late in the shutdown process as possible to see if there are any open files.
Edit:
Try adding an override for home.mount with

OnFailure=lsof.service

Not finding lsof.service provided by any package.  Conceptually, we just need to have it call /usr/bin/lsod /home if I am not mistaken and have that output get written to journalctl.

Would this 2 step procedure work?

1) Make lsof.service
2) Override home.mount to call it.

1)

# /etc/systemd/system/lsof.service
[Unit]

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=lsof

[Service]
Type=simple
ExecStart=/usr/bin/lsof /home

2)

# systemctl edit home.mount
[Unit]
OnFailure=lsof.service

EDIT: nope that was a spectacular failure!

...
Jun 25 12:22:22 ease systemd[1]: /etc/systemd/system/home.mount.d/override.conf:1: Assignment outside of section. Ignoring.
...
un 25 12:23:09 ease systemd[1]: /etc/systemd/system/home.mount.d/override.conf:2: Failed to add dependency on /usr/bin/lsof, ignoring: Invalid argument
Jun 25 12:23:09 ease systemd[1]: /etc/systemd/system/home.mount.d/override.conf:2: Failed to add dependency on /home, ignoring: Invalid argument
...
Jun 25 12:29:12 ease systemd[1]: /etc/systemd/system/lsof.service:4: Unknown key name 'StandardOutput' in section 'Unit', ignoring.
Jun 25 12:29:12 ease systemd[1]: /etc/systemd/system/lsof.service:5: Unknown key name 'StandardError' in section 'Unit', ignoring.
Jun 25 12:29:12 ease systemd[1]: /etc/systemd/system/lsof.service:6: Unknown key name 'SyslogIdentifier' in section 'Unit', ignoring.

Last edited by graysky (2020-06-25 16:32:15)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#9 2020-06-25 16:35:11

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

Lone_Wolf wrote:

Are you shutting down from a graphical session ?

If so, try logging out of any X sessions, then login as root on console and issue poweroff (or similar ).

Yes, lxdm and xfce4.  If I log out, drop to a tty and issue a reboot command, I do not see the umount error.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#10 2020-06-25 16:36:04

loqs
Member
Registered: 2014-03-06
Posts: 10,969

Re: Failed unmounting /home on shutdown

Yes that is I was envisaging,  although I had not thought to use SyslogIdentifier and have not tried it.

Offline

#11 2020-06-25 16:50:21

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 23,689
Website

Re: Failed unmounting /home on shutdown

graysky wrote:

Yes, lxdm and xfce4.  If I log out, drop to a tty and issue a reboot command, I do not see the umount error.

I'd just narrow it down.  Assuming you did as suggested and issued the reboot while logged in as root, try loging out of X (and ensuring the DM is stopped) but log in to the tty as your user and `reboot'.  Then perhaps try either a different X session started from LXDM, or xfce4 started via startx/xinit.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#12 2020-06-25 17:33:20

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

@Trilby - Yes:

Logged in as root/no graphical = clean reboot
Logged in as user/no graphical = clean reboot
Logged in as user --> startxfce4 (no dm) = bad reboot
Logged in as user via lxdm = bad reboot
Logged in as user via sddm = bad reboot

Seems pretty clear that something xfce4 is running is to blame and that is independent of DM.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#13 2020-06-25 17:42:38

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

I restored my xfce4 profile to the default thus removing any plugins that I configured but found that the unclean shutdown is still present on a brand new profile.  I really need to get that lsof to run properly to find the smoking gun.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#14 2020-06-25 17:44:33

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 23,689
Website

Re: Failed unmounting /home on shutdown

There are the gvfsd messages which suggest it is the source.  Are you able to stop gvfsd while still within xfce then reboot?


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#15 2020-06-25 17:52:31

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

@Trilby - Yes, I removed gvfs-gphoto2 gvfs-afc gvfs and rebooted.  Checked ps aux | grep gvfs (none found) and rebooted.  Same error.  I also removed xfce4-notifyd after seeing an error on it but again, unclean reboot.

I installed lxqt, and found that it too causes the error on reboot hmm


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#16 2020-06-25 17:55:05

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

I created a brand new user, logged into xfce4, confirmed that no processes from my original user were running and found that rebooting on the new user also causes the error.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#17 2020-06-26 11:58:02

zpg443
Member
Registered: 2016-12-03
Posts: 83

Re: Failed unmounting /home on shutdown

How is /etc/systemd/logind.conf configured?

Offline

#18 2020-06-26 12:09:42

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

zpg443 wrote:

How is /etc/systemd/logind.conf configured?

Unchanged.  I only customized several systemd files but in ways that should not affect this I think...

# pacman -Qkk systemd
backup file: systemd: /etc/systemd/coredump.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/coredump.conf (Size mismatch)
backup file: systemd: /etc/systemd/journald.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journald.conf (Size mismatch)

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#19 2020-06-26 16:48:40

zpg443
Member
Registered: 2016-12-03
Posts: 83

Re: Failed unmounting /home on shutdown

Try KillUserProcesses=yes in  /etc/systemd/logind.conf

Offline

#20 2020-06-26 17:07:29

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 612

Re: Failed unmounting /home on shutdown

If I recall correctly both LXQT and XFCE use XDG autostart, which could launch the entries you have in /etc/xdg/autostart and/or ~/.config/autostart. Try something light like OpenBox instead to see if the lock still happens, in which case you should be able to narrow it down from your autostart entries.

There was an issue reported over the last couple of week with PCManFM not closing gracefully, if I recall correctly. Are you using PCManFM?

Offline

#21 2020-06-26 17:11:12

loqs
Member
Registered: 2014-03-06
Posts: 10,969

Re: Failed unmounting /home on shutdown

The following does not produce any errors for me:

# /etc/systemd/system/home.mount.d/override.conf
[Unit]
OnFailure=lsof.service
# /etc/systemd/system/lsof.service
[Service]
Type=simple
ExecStart=/usr/bin/lsof /home
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=lsof

Offline

#22 2020-06-26 18:24:48

GaKu999
Member
Registered: 2020-06-21
Posts: 35

Re: Failed unmounting /home on shutdown

As i see on a previous post you use profile sync daemon. Try before shutdown systemctl —user stop psd (or disable —now) instead of stop and test if it still fails to unmount /home

I had to manually enable and disable it because it sometimes runs in a deadlock and locks the user session in place, preventing a successful logout, locking as well the /home partition...(or worse, locking the homed container)

Offline

#23 2020-06-26 18:47:09

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,001
Website

Re: Failed unmounting /home on shutdown

GaKu999 wrote:

As i see on a previous post you use profile sync daemon. Try before shutdown systemctl —user stop psd (or disable —now) instead of stop and test if it still fails to unmount /home

@GaKu999- I tried that but got the same result... maybe I am misunderstanding your suggestion?

graysky wrote:

I was thinking psd might be causing this, but I get the same error on shutdown with I stop it manually prior.

@loqs - I tried your two modifications but didn't get the expected lsof output in journactl:

...
Jun 26 14:38:48 ease systemd[1]: Requested transaction contradicts existing jobs: Transaction for lsof.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
Jun 26 14:38:48 ease systemd[1]: home.mount: Failed to enqueue OnFailure= job, ignoring: Transaction for lsof.service/start is destructive (system-systemd\x2dfsck.slice has 'stop' job queued, but 'start' is included in transaction).
...

Link to complete journalctl from this particular reboot command: note that now two partitions failed to unmount according to the log.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#24 2020-06-26 19:09:19

loqs
Member
Registered: 2014-03-06
Posts: 10,969

Re: Failed unmounting /home on shutdown

Will systemd allow a stop command instead?

# /etc/systemd/system/lsof.service
[Service]
Type=simple
ExecStop=/usr/bin/lsof /home
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=lsof

Edit:
Was psd running for the newly created user that also had the issue?
Is home mounted cleanly on the next boot?
Edit2:
Systemd has scheduled home to be unmounted before psd is stopped and before the user session is stopped:

Jun 26 14:38:42 ease systemd[1]: Failed unmounting /home.
Jun 26 14:38:42 ease systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-home.service: Succeeded.
Jun 26 14:38:42 ease systemd-logind[567]: Removed session 2.
Jun 26 14:38:42 ease systemd[1]: Stopped File System Check on /dev/disk/by-label/home.
Jun 26 14:38:42 ease CROND[1497]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease systemd[637]: gvfs-daemon.service: Succeeded.
Jun 26 14:38:42 ease CROND[4235]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease systemd[637]: Stopped Virtual filesystem service.
Jun 26 14:38:42 ease systemd[637]: gvfs-udisks2-volume-monitor.service: Succeeded.
Jun 26 14:38:42 ease systemd[637]: Stopped Virtual filesystem service - disk device monitor.
Jun 26 14:38:42 ease systemd[637]: gvfs-afc-volume-monitor.service: Succeeded.
Jun 26 14:38:42 ease systemd[637]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Jun 26 14:38:42 ease CROND[10754]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease CROND[5123]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease systemd-networkd[363]: lxcbr0: Link DOWN
Jun 26 14:38:42 ease systemd-networkd[363]: lxcbr0: Lost carrier
Jun 26 14:38:42 ease CROND[7008]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease kernel: lxcbr0: port 1(vethGl91a1) entered disabled state
Jun 26 14:38:42 ease dnsmasq[11255]: reading /etc/resolv.conf
Jun 26 14:38:42 ease dnsmasq[11255]: using nameserver 172.17.1.250#53
Jun 26 14:38:42 ease CROND[6122]: pam_unix(crond:session): session closed for user facade
Jun 26 14:38:42 ease mkinitcpio[17223]: ==> Starting build: none
Jun 26 14:38:42 ease mkinitcpio[17223]:   -> Running build hook: [sd-shutdown]
Jun 26 14:38:42 ease systemd[1]: lxc-net.service: Succeeded.
Jun 26 14:38:42 ease systemd[637]: pulseaudio.service: Succeeded.
Jun 26 14:38:42 ease systemd[637]: Stopped Sound Service.
Jun 26 14:38:42 ease systemd[1]: Stopped LXC network bridge setup.
Jun 26 14:38:42 ease systemd[1]: lm_sensors.service: Succeeded.
Jun 26 14:38:42 ease systemd[1]: Stopped Initialize hardware monitoring sensors.
Jun 26 14:38:42 ease mkinitcpio[17223]: ==> Build complete.
Jun 26 14:38:42 ease systemd[1]: mkinitcpio-generate-shutdown-ramfs.service: Succeeded.
Jun 26 14:38:42 ease systemd[1]: Finished Generate shutdown-ramfs.
Jun 26 14:38:42 ease systemd[637]: at-spi-dbus-bus.service: Succeeded.
Jun 26 14:38:42 ease systemd[637]: Stopped Accessibility services bus.
Jun 26 14:38:42 ease kernel: [drm] Got external EDID base block and 1 extension from "edid/27UK650.bin" for connector "DP-1"
Jun 26 14:38:42 ease systemd[1]: mnt-data.mount: Succeeded.
Jun 26 14:38:42 ease systemd[1]: Unmounted /mnt/data.
Jun 26 14:38:42 ease systemd[1]: Stopped target Block Device Preparation for /dev/mapper/data-crypt.
Jun 26 14:38:42 ease profile-sync-daemon[17254]: chromium resync successful
Jun 26 14:38:42 ease sddm[583]: Display server stopped.
Jun 26 14:38:42 ease sddm[583]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jun 26 14:38:42 ease systemd[1]: sddm.service: Succeeded.
Jun 26 14:38:42 ease systemd[1]: Stopped Simple Desktop Display Manager.
Jun 26 14:38:42 ease systemd[1]: Stopping Login Service...
Jun 26 14:38:43 ease sudo[17424]:  facade : TTY=unknown ; PWD=/home/facade ; USER=root ; COMMAND=/usr/bin/psd-overlay-helper -d /run/user/1000/facade-chromium mountdown
Jun 26 14:38:43 ease sudo[17424]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 26 14:38:43 ease systemd[1]: run-user-1000-facade\x2dchromium.mount: Succeeded.
Jun 26 14:38:43 ease systemd[637]: run-user-1000-facade\x2dchromium.mount: Succeeded.
Jun 26 14:38:43 ease systemd[1]: Unmounted /run/user/1000/facade-chromium.
Jun 26 14:38:43 ease sudo[17424]: pam_unix(sudo:session): session closed for user root
Jun 26 14:38:43 ease profile-sync-daemon[17254]: chromium unsync successful
Jun 26 14:38:43 ease systemd[637]: psd.service: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Stopped Profile-sync-daemon.
Jun 26 14:38:43 ease systemd[637]: Stopped target Basic System.
Jun 26 14:38:43 ease systemd[637]: Stopped target Paths.
Jun 26 14:38:43 ease systemd[637]: Stopped target Sockets.
Jun 26 14:38:43 ease systemd[637]: Stopped target Timers.
Jun 26 14:38:43 ease systemd[637]: psd-resync.timer: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Stopped Timer for profile-sync-daemon - 1Hour.
Jun 26 14:38:43 ease systemd[637]: dbus.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed D-Bus User Message Bus Socket.
Jun 26 14:38:43 ease systemd[637]: dirmngr.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed GnuPG network certificate management daemon.
Jun 26 14:38:43 ease systemd[637]: gpg-agent-browser.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun 26 14:38:43 ease systemd[637]: gpg-agent-extra.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jun 26 14:38:43 ease systemd[637]: gpg-agent-ssh.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jun 26 14:38:43 ease systemd[637]: gpg-agent.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed GnuPG cryptographic agent and passphrase cache.
Jun 26 14:38:43 ease systemd[637]: p11-kit-server.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed p11-kit server.
Jun 26 14:38:43 ease systemd[637]: pulseaudio.socket: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Closed Sound System.
Jun 26 14:38:43 ease systemd[637]: Reached target Shutdown.
Jun 26 14:38:43 ease systemd[637]: systemd-exit.service: Succeeded.
Jun 26 14:38:43 ease systemd[637]: Finished Exit the Session.
Jun 26 14:38:43 ease systemd[637]: Reached target Exit the Session.
Jun 26 14:38:43 ease systemd[641]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[facade] ruser=[<unknown>] rhost=[<unknown>]
Jun 26 14:38:43 ease systemd[1]: user@1000.service: Succeeded.
Jun 26 14:38:43 ease systemd[1]: Stopped User Manager for UID 1000.
Jun 26 14:38:43 ease systemd[1]: Stopping User Runtime Directory /run/user/1000...
Jun 26 14:38:43 ease systemd[1]: run-user-1000.mount: Succeeded.
Jun 26 14:38:43 ease systemd[1]: Unmounted /run/user/1000.
Jun 26 14:38:43 ease systemd[1]: user-runtime-dir@1000.service: Succeeded.
Jun 26 14:38:43 ease systemd[1]: Stopped User Runtime Directory /run/user/1000.
Jun 26 14:38:43 ease systemd[1]: Removed slice User Slice of UID 1000.

Last edited by loqs (2020-06-26 19:22:55)

Offline

#25 2020-06-26 19:09:55

GaKu999
Member
Registered: 2020-06-21
Posts: 35

Re: Failed unmounting /home on shutdown

Al right a headbreaker then, lastditch effort....

Instead of starting the graphical.target first, login as root (on tty2) and trigger the /home automount (cd /home should be enough) then unmount it and run fsck.ext4.

Later manually mount it and start whatever you use to login into xfce4 (keeping root logged in)
systemctl status (with root) and keep the output, logout with your user as usual, systemctl status (with root) and keep the output, if you wish also stop whatever you use to login on xfce4. And finally umount /home.

This at least would make it clear who is getting stuck...I hope...

Also if the home.mount override causes issues during this process with no useful output remove it temporarily...

Offline

Board footer

Powered by FluxBB