When shutting down Debian 13 GNOME I face for tens of seconds a black screen with:

```
[86218.566170] systemd-shutdown[1]: Waiting for process: 2565 (etesync-dav)
```

Then for less than a second:

```
[86298.757926] systemd-shutdown[1]: Unable to finalize remaining DM devices, ignoring.
```

is appended, before the computer is no more running.

What is taking tens of seconds? etesync-dav or finalizing remaining DM devices?
Jun 1, 3:59pm

The tens of seconds delay in your shutdown process is almost certainly caused by etesync-dav (process 2565).

Why?

  • The first message:

    text
    [86218.566170] systemd-shutdown[1]: Waiting for process: 2565 (etesync-dav)

    indicates that systemd-shutdown is blocking the shutdown sequence, waiting for etesync-dav to terminate. This is the primary bottleneck.

  • The second message:

    text
    [86298.757926] systemd-shutdown[1]: Unable to finalize remaining DM devices, ignoring.

    appears after the long wait (about 80 seconds later, based on the timestamps). This is a consequence of the shutdown process being stuck, not the cause. systemd eventually gives up on finalizing Device Mapper (DM) devices (e.g., LVM, encrypted volumes) because the shutdown is already delayed by etesync-dav.

What is etesync-dav?

etesync-dav is a background service for EteSync, a secure, end-to-end encrypted sync solution for contacts, calendars, and other PIM data. It likely runs as a DAV (WebDAV/CalDAV/CardDAV) sync client.

How to Fix It

1. Check if etesync-dav is Stuck

  • Run:
    bash
    systemctl status etesync-dav.service
  • Look for errors or timeouts in the logs:
    bash
    journalctl -u etesync-dav.service -b

2. Reduce Shutdown Timeout for etesync-dav

  • Edit the service file to add a timeout:
    bash
    sudo systemctl edit etesync-dav.service
  • Add:
    ini
    [Service]
TimeoutStopSec=10s
  • Reload systemd:
    bash
    sudo systemctl daemon-reload
  • This forces systemd to kill etesync-dav after 10 seconds instead of waiting indefinitely.

3. Debug etesync-dav

  • If the service is hanging, check its configuration or logs for issues (e.g., network timeouts, corrupted local data).
  • Try restarting it manually:
    bash
    sudo systemctl restart etesync-dav.service
  • If the issue persists, consider reinstalling or updating etesync-dav.

4. Mask the Service (Temporary Workaround)

  • If you don’t need etesync-dav to run at shutdown, disable it:
    bash
    sudo systemctl mask etesync-dav.service
  • Note: This will prevent it from starting at all, so only do this if you’re okay with losing sync functionality until the next boot.

5. Check for DM Device Issues (Secondary)

  • If the DM devices message persists after fixing etesync-dav, investigate your LVM/encrypted volumes:
    bash
    sudo lvm lvs
sudo cryptsetup status
  • Ensure all volumes are properly mounted/unmounted.

Summary

The delay is caused by etesync-dav. The DM devices message is a side effect of the shutdown being stuck. Focus on debugging or limiting the timeout for etesync-dav.

Jun 1, 3:59pm

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more