Proxmox nach update Probleme mit Container

[e-i-k-e]

Hallo Zusammen,

betreibe auf einem NUC Poxmox, im Container läuft Ubuntu/iobroker.
Nach einem Update von Proxmox habe ich Probleme mit ioBroker bzw. dem Container.

Testweise habe ich einen neuen Container mit Ubuntu 19.04 erstellt (mit Debian 9.0 das selbe). Der Container lässt sich nicht starten.

Job for pve-container@110.service failed because the control process exited with error code.
See "systemctl status pve-container@110.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@110' failed: exit code 1

Bei journalctl -xe werden mir einige Fehler angezeigt, anbei ein kleiner Auszug.

-- The job identifier is 49564.
Nov 17 20:35:39 pve kernel: buffer_io_error: 3522 callbacks suppressed
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9264, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9280, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9296, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9312, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9328, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9344, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9360, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9376, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9392, lost async page write
Nov 17 20:35:39 pve kernel: Buffer I/O error on dev dm-14, logical block 9408, lost async page write
Nov 17 20:35:39 pve kernel: JBD2: recovery failed
Nov 17 20:35:39 pve kernel: EXT4-fs (dm-14): error loading journal
Nov 17 20:35:39 pve kernel: lxc-start[17913]: segfault at 50 ip 00007f06e53c9f8b sp 00007ffeffe7ca30 error 4 in liblxc.so.1.6.0[7f06e5370000+8a0
Nov 17 20:35:39 pve kernel: Code: 9b c0 ff ff 4d 85 ff 0f 85 82 02 00 00 66 90 48 8b 73 50 48 8b bb f8 00 00 00 e8 80 78 fa ff 4c 8b 74 24 10 48
Nov 17 20:35:39 pve lxc-start[17902]: lxc-start: 110: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receiv
Nov 17 20:35:39 pve lxc-start[17902]: lxc-start: 110: tools/lxc_start.c: main: 329 The container failed to start
Nov 17 20:35:39 pve lxc-start[17902]: lxc-start: 110: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Nov 17 20:35:39 pve lxc-start[17902]: lxc-start: 110: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfi
Nov 17 20:35:39 pve systemd[1]: pve-container@110.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support

pveversion -v

root@pve:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve)
pve-manager: 6.0-11 (running version: 6.0-11/2140ef37)
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-5.0.21-2-pve: 5.0.21-7
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-7
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-3
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

systemctl status pve-container@110.service

root@pve:~# systemctl status pve-container@110.service
● pve-container@110.service - PVE LXC Container: 110
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-11-17 20:39:06 CET; 13min ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 19244 ExecStart=/usr/bin/lxc-start -n 110 (code=exited, status=1/FAILURE)

Nov 17 20:39:04 pve systemd[1]: Starting PVE LXC Container: 110...
Nov 17 20:39:06 pve lxc-start[19244]: lxc-start: 110: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receiv
Nov 17 20:39:06 pve lxc-start[19244]: lxc-start: 110: tools/lxc_start.c: main: 329 The container failed to start
Nov 17 20:39:06 pve lxc-start[19244]: lxc-start: 110: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Nov 17 20:39:06 pve lxc-start[19244]: lxc-start: 110: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfi
Nov 17 20:39:06 pve systemd[1]: pve-container@110.service: Control process exited, code=exited, status=1/FAILURE
Nov 17 20:39:06 pve systemd[1]: pve-container@110.service: Failed with result 'exit-code'.
Nov 17 20:39:06 pve systemd[1]: Failed to start PVE LXC Container: 110.

Weiß jemand Rat?

[dali3]

ich habe dasselbe problem seit dem Update

[zsb2002]

Klappt es mit einem privilegierten Container?

[Chaot]

@e-i-k-e Bei mir die gleiche Fehlermeldung.
Immer wenn ich einen Container stoppe und neu starten will.

Wenn ich ein Backup einspiele klappt der Start wieder.

Hast du inzwischen was lösen können?