LXC container suddenly can't start with mounted HDD image

[Saihtam]

Hello everyone!

After having a solid uptime of 5 days for my server without problems, I decided to try a reboot of the system just to see if everything autostarts the way it should - Which it obviously didn't...

Two containers failed to autostart as they usually do for some reason, and one of them in particular doesn't even start manually at all anymore. It just gives me this error message "command 'systemctl start pve-container@102' failed: exit code 1", and I have no idea why since the container in question have been running for several days without issues.

I am running a normal no-subscription install with, as far as i know, the latest packages available:

proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

A more complete error description for the startup:

-- Unit pve-container@102.service has begun starting up.
Nov 22 15:53:02 proxmox kernel: EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: (null)
Nov 22 15:53:04 proxmox pveproxy[1234]: proxy detected vanished client connection
Nov 22 15:53:04 proxmox kernel: JBD2: Invalid checksum recovering block 86 in log
Nov 22 15:53:05 proxmox kernel: JBD2: Invalid checksum recovering block 93 in log
Nov 22 15:53:06 proxmox kernel: JBD2: recovery failed
Nov 22 15:53:06 proxmox kernel: EXT4-fs (dm-0): error loading journal
Nov 22 15:53:06 proxmox lxc-start[5370]: lxc-start: 102: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
Nov 22 15:53:06 proxmox lxc-start[5370]: lxc-start: 102: tools/lxc_start.c: main: 368 The container failed to start.
Nov 22 15:53:06 proxmox lxc-start[5370]: lxc-start: 102: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode.
Nov 22 15:53:06 proxmox lxc-start[5370]: lxc-start: 102: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and --logpriority options.
Nov 22 15:53:06 proxmox systemd[1]: pve-container@102.service: Control process exited, code=exited status=1
Nov 22 15:53:06 proxmox pvestatd[1209]: unable to get PID for CT 102 (not running?)
Nov 22 15:53:06 proxmox systemd[1]: Failed to start PVE LXC Container: 102.
-- Subject: Unit pve-container@102.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@102.service has failed.
--

I am not sure how to interpret this data. Any ideas would be really appreciated