May 20 22:09:01 dl380g7 systemd[1]: Starting VDO volume services...
-- Subject: A start job for unit vdo.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit vdo.service has begun execution.
--
-- The job identifier is 6046.
May 20 22:09:01 dl380g7 vdo[5672]: Traceback (most recent call last):
May 20 22:09:01 dl380g7 vdo[5672]: File "/usr/bin/vdo", line 46, in <module>
May 20 22:09:01 dl380g7 vdo[5672]: from vdo.utils import Command
May 20 22:09:01 dl380g7 vdo[5672]: ModuleNotFoundError: No module named 'vdo'
May 20 22:09:01 dl380g7 systemd[1]: vdo.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 vdo.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
May 20 22:09:01 dl380g7 systemd[1]: vdo.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit vdo.service has entered the 'failed' state with result 'exit-code'.
May 20 22:09:01 dl380g7 systemd[1]: Failed to start VDO volume services.
-- Subject: A start job for unit vdo.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit vdo.service has finished with a failure.
--
-- The job identifier is 6046 and the job result is failed.
I've searched the tickets here, and even Google didn't help shed any light on the situation. I do apologize if, as is likely, the issue is on my end, but after retrying a few times and being unable to otherwise track down a solution, this seemed an appropriate next step.
Hello!
I am having trouble getting VDO and KVDO working on a debian based machine (proxmox). Here are the steps I followed initially:
Which leads to: (
journalctl -xe
)I've searched the tickets here, and even Google didn't help shed any light on the situation. I do apologize if, as is likely, the issue is on my end, but after retrying a few times and being unable to otherwise track down a solution, this seemed an appropriate next step.