TASK ERROR: command 'lxc-start -n 100' failed: exit code 1

[Alexander Fox]

Hi

I have try save OpenVz Container (50 GB) and import it like the Guide of this

https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC

than I have on start this error



lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK ERROR: command 'lxc-start -n 100' failed: exit code 1

 

[fabian]

Please post

• pveversion -v
• pct config 100

and get a debug log by starting the container in foreground mode:
"lxc-start -n 100 -F -lDEBUG -o lxc-100.log"
and post the log here (if the container starts, you can shut it down with "pct shutdown 100" in another shell).

 

[bizzarrone]

I have the same problem after migration offline from another node..

root@pippo-prox02:/var/log# lxc-start -n 109 -F -lDEBUG -o lxc-109.log
mount: wrong fs type, bad option, bad superblock on /dev/mapper/pve2-vm--109--disk--1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
command 'mount /dev/dm-5 /var/lib/lxc/109/rootfs//' failed: exit code 32
lxc-start: conf.c: run_buffer: 347 Script exited with status 32
lxc-start: start.c: lxc_init: 465 failed to run pre-start hooks for container '109'.
lxc-start: start.c: __lxc_start: 1313 failed to initialize the container
lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

root@-prox02:/var/log# pveversion -v
proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve)
pve-manager: 4.3-10 (running version: 4.3-10/7230e60f)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-47
qemu-server: 4.0-94
pve-firmware: 1.1-10
libpve-common-perl: 4.0-80
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-68
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.3-14
pve-qemu-kvm: 2.7.0-6
pve-container: 1.0-81
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

root@xx-prox02:/var/log# pct config 109
arch: amd64
cpulimit: 4
cpuunits: 1024
description: 139.191.9.200, mac-address 0050563f09c8 %0A
hostname: xxx-mongo-dev2
memory: 4096
net0: name=eth0,bridge=vmbr0,gw=139.191.9.1,hwaddr=00:50:56:3f:09:6e,ip=139.191.9.110/24,type=veth
onboot: 1
ostype: centos
rootfs: vmstore1:vm-109-disk-1,size=12G
swap: 5120
lxc.aa_profile: unconfined

 

[vilhelmprytz]

Did you solve this issue? I get the same issue, even if the CT is just newly created!!

Thanks a lot .