After restarting snap.lxd.daemon due to this issue Error: open /tmp/lxd_editor_<number>.yaml: no such file or directory - #3 by pmarini (I also applied the patch recommended by @sdeziel1 ) one of the VMs is not starting anymore.
# lxc start backup01 --project central-services
Error: Failed to get volume disk path: Failed to locate zvol for "lxdpool02/virtual-machines/central-services_backup01.block": context deadline exceeded
Try `lxc info --show-log backup01` for more info
# lxc info --show-log backup01 --project central-services
Name: backup01
Status: STOPPED
Type: virtual-machine
Architecture: x86_64
Created: 2024/07/16 15:28 CEST
Last Used: 2025/11/28 10:51 CET
Error: open /var/snap/lxd/common/lxd/logs/central-services_backup01/qemu.log: no such file or directory
# snap list lxd
Name Version Rev Tracking Publisher Notes
lxd 5.21.4-9eb1368 36971 5.21/stable canonical✓ held
# zfs list lxdpool02/virtual-machines/central-services_backup01.block
NAME USED AVAIL REFER MOUNTPOINT
lxdpool02/virtual-machines/central-services_backup01.block 10.2G 115G 10.3G -
# lxc config show backup01 --project central-services
architecture: x86_64
config:
image.architecture: amd64
image.description: Debian bookworm amd64 (20240716_0002)
image.os: Debian
image.release: bookworm
image.serial: "20240716_0002"
image.type: disk-kvm.img
image.variant: cloud
volatile.base_image: 2f36fb7348d6ffa1515bd05d520fd2943c1cc0804f974477db5d37620c44b3cc
volatile.cloud-init.instance-id: bef576da-8d63-4e70-b018-05a055716b6e
volatile.eth0.hwaddr: 00:16:3e:ca:4c:af
volatile.last_state.power: RUNNING
volatile.uuid: cf70255c-6e9d-454a-9551-ee7a361a01b4
volatile.uuid.generation: cf70255c-6e9d-454a-9551-ee7a361a01b4
volatile.vsock_id: "3937891088"
devices:
sdb:
source: /dev/disk/by-id/scsi-SSEAGATE_<sn1>
type: disk
sdg:
source: /dev/disk/by-id/scsi-SSEAGATE_<sn2>
type: disk
ephemeral: false
profiles:
- prf-backup
stateful: false
description: ""
What could be the reason? I don’t find anything out of order at a first sight.