Job for zfs-mount.service failed because the control process exited with error code

informant

Renowned Member
Jan 31, 2012
775
10
83
hi, following error comes after a normal upgrade

zfs-import-scan.service is a disabled or a static unit, not starting it.
Job for zfs-mount.service failed because the control process exited with error code.
See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
zfs-mount.service couldn't start.
Job for zfs-share.service failed because the control process exited with error code.
See "systemctl status zfs-share.service" and "journalctl -xe" for details.
zfs-share.service couldn't start.

how can i fix it?
regards
 
Hi,
What is the error message form journalctl -xe?
 
i have use small command:
systemctl status zfs-mount.service
* zfs-mount.service - Mount ZFS filesystems
Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-09-16 15:13:17 CEST; 4 days ago
Main PID: 59419 (code=exited, status=1/FAILURE)

Sep 16 15:13:17 prometheus systemd[1]: Starting Mount ZFS filesystems...
Sep 16 15:13:17 prometheus zfs[59419]: The ZFS modules are not loaded.
Sep 16 15:13:17 prometheus zfs[59419]: Try running '/sbin/modprobe zfs' as root to load them.
Sep 16 15:13:17 prometheus systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 15:13:17 prometheus systemd[1]: Failed to start Mount ZFS filesystems.
Sep 16 15:13:17 prometheus systemd[1]: zfs-mount.service: Unit entered failed state.
Sep 16 15:13:17 prometheus systemd[1]: zfs-mount.service: Failed with result 'exit-code'.

on all other nodes comes Unit zfs-mount.service could not be found. or
* zfs-mount.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
and on one comes
* zfs-mount.service - Mount ZFS filesystems
Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled)
Active: active (exited) since Sat 2017-09-16 15:12:42 CEST; 4 days ago
Process: 8061 ExecStart=/sbin/zfs mount -a (code=exited, status=0/SUCCESS)
Main PID: 8061 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/zfs-mount.service

Sep 16 15:12:42 daedalus systemd[1]: Starting Mount ZFS filesystems...
Sep 16 15:12:42 daedalus systemd[1]: Started Mount ZFS filesystems.
but we do not use it, but all nodes have other messages?
regards
 
I am also having this issue after updating to the latest Proxmox version:

Code:
root@TracheServ:/# systemctl start zfs-mount.service
Job for zfs-mount.service failed because the control process exited with error code.
See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
root@TracheServ:/# journalctl -xe
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 1124072.
Nov 27 10:06:01 TracheServ systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Nov 27 10:06:01 TracheServ systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 1124072.
Nov 27 10:06:52 TracheServ systemd[1]: Starting Mount ZFS filesystems...
-- Subject: A start job for unit zfs-mount.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zfs-mount.service has begun execution.
--
-- The job identifier is 1124127.
Nov 27 10:06:52 TracheServ zfs[24968]: cannot mount '/Nextcloud.Storage': directory is not empty
Nov 27 10:06:52 TracheServ systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zfs-mount.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 27 10:06:52 TracheServ systemd[1]: zfs-mount.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zfs-mount.service has entered the 'failed' state with result 'exit-code'.
Nov 27 10:06:52 TracheServ systemd[1]: Failed to start Mount ZFS filesystems.
-- Subject: A start job for unit zfs-mount.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zfs-mount.service has finished with a failure.
--
-- The job identifier is 1124127 and the job result is failed.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!