After reboot CT does not start

[altomarketing]

After a restart lxc container are not starting,

Container with Centos 6.9 with cpanel working for several months without any problem, but after restart CT it does not start any more.

lxc-start -F -n 100 --logfile=lxc.log --logpriority=debug

unsupported redhat release 'CentOS release 6.10 (Final)'
lxc-start: conf.c: run_buffer: 336 Script exited with status 25
lxc-start: conf.c: lxc_setup: 3827 failed to run mount hooks for container '100'                                     .
lxc-start: start.c: do_start: 702 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1172 failed to spawn '100'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

pveversion -v

proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-29
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-25
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-6
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie

cat /etc/pve/lxc/100.conf

#cpanel .183 percona ROLMEC
arch: amd64
cpulimit: 2
cpuunits: 1024
hostname: amk
memory: 4000
nameserver: 8.8.8.8 8.8.4.4
net0: bridge=vmbr0,gw=190.7.18.1,hwaddr=12:CD:52:78:8C:2D,ip=190.7.18.23/27,ip6=auto,name=eth183,type=veth
onboot: 1
ostype: centos
rootfs: local:100/vm-100-disk-1.raw,size=300G
searchdomain: altomarketing.net
swap: 512

cat /var/lib/lxc/100/config

lxc.arch = amd64
lxc.include = /usr/share/lxc/config/centos.common.conf
lxc.tty = 2
lxc.environment = TERM=linux
lxc.utsname = amk
lxc.cgroup.memory.limit_in_bytes = 4194304000
lxc.cgroup.memory.memsw.limit_in_bytes = 4731174912
lxc.cgroup.cpu.cfs_period_us = 100000
lxc.cgroup.cpu.cfs_quota_us = 200000
lxc.cgroup.cpu.shares = 1024
lxc.rootfs = loop:/var/lib/vz/images/100/vm-100-disk-1.raw
lxc.network.type = veth
lxc.network.veth.pair = veth100i0
lxc.network.hwaddr = 12:CD:52:78:8C:2D
lxc.network.name = eth183

df

Filesystem           1K-blocks      Used Available Use% Mounted on
udev                     10240         0     10240   0% /dev
tmpfs                  1621256      8988   1612268   1% /run
/dev/dm-0             98952796   6040936  87862312   7% /
tmpfs                  4053136     40560   4012576   2% /dev/shm
tmpfs                     5120         0      5120   0% /run/lock
tmpfs                  4053136         0   4053136   0% /sys/fs/cgroup
/dev/mapper/pve-data 357643060 316959152  40667524  89% /var/lib/vz
/dev/fuse                30720        20     30700   1% /etc/pve
cgmfs                      100         0       100   0% /run/cgmanager/fs

any clue how to fix it ?

 

[altomarketing]

I noticed that the server is showing :

EXT4-fs (loop0) : couldn't mount as ext2 due to feature incompatibilties
EXT4-fs (loop0) : couldn't mount as ext3 due to feature incompatibilties

 

[altomarketing]

anyone can help me please ?

 

[altomarketing]