$ snap install hello-world
error: cannot perform the following tasks:
- Mount snap "core" (1689) ([start snap-core-1689.mount] failed with exit status 1: Job for snap-core-1689.mount failed. See "systemctl status snap-core-1689.mount" and "journalctl -xe" for details.)

Appears to be an issue with squashfs, I have run a test with squashfs to verify that it does not work in my tmp directory for loading a *.squash file with squashfs-tools. I'm running Ubuntu 16.04 and unsure how to enable support for squashfs or if it is possible. I'm running this on a dedicated server.

snap-core-1689.mount - Mount unit for core
   Loaded: loaded (/etc/systemd/system/snap-core-1689.mount; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-06-14 12:13:03 EDT; 2min 17s ago
    Where: /snap/core/1689
     What: /var/lib/snapd/snaps/core_1689.snap
  Process: 6092 ExecMount=/bin/mount /var/lib/snapd/snaps/core_1689.snap /snap/core/1689 -t squashfs -o nodev,ro (code=exited, status=32)

Jun 14 12:13:03 hostname systemd[1]: Mounting Mount unit for core...
Jun 14 12:13:03 hostname mount[6092]: mount: unknown filesystem type 'squashfs'
Jun 14 12:13:03 hostname systemd[1]: snap-core-1689.mount: Mount process exited, code=exited status=32
Jun 14 12:13:03 hostname systemd[1]: Failed to mount Mount unit for core.
Jun 14 12:13:03 hostname systemd[1]: snap-core-1689.mount: Unit entered failed state.
  • 1
    Who is your host? We've run into a few situations where hosts claim they provide Ubuntu 16.04 but then use a custom kernel.
    – kyrofa
    Jun 14, 2017 at 16:52
  • @Kyle I'm using Kimsufi, I can see that in the advanced server install options there is an option to use the distribution kernel. This appears to be the problem.
    – gopher
    Jun 14, 2017 at 16:57
  • 1
    Yep, that'll do it. Super frustrating, I'm sorry!
    – kyrofa
    Jun 14, 2017 at 17:19
  • I'm on OVH and same thing seems to be happening, anyway I can check if I'm running a custom kernel?
    – Anthony
    Apr 12, 2018 at 23:06

1 Answer 1


My dedicated server host was using a custom kernel which was the cause of this issue. Beware of hosting providers not installing the distribution kernel when they appear to do so.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.