Cannot start a container.

proxmox_dumb_user

New Member
May 23, 2020
2
0
1
43
Hello,
I had a container for owncloud on my proxmox. I added more space to a user. Never had issues with it... now it is just not starting:

These are the logs I am getting:

Code:
root@proxmox:~# lxc-start -lDEBUG -o lxc-start.log -F -n 102

lxc-start: 102: conf.c: run_buffer: 323 Script exited with status 32

lxc-start: 102: start.c: lxc_init: 804 Failed to run lxc.hook.pre-start for container "102"

lxc-start: 102: start.c: __lxc_start: 1903 Failed to initialize container "102"

lxc-start: 102: conf.c: run_buffer: 323 Script exited with status 1

lxc-start: 102: start.c: lxc_end: 971 Failed to run lxc.hook.post-stop for container "102"

lxc-start: 102: tools/lxc_start.c: main: 308 The container failed to start

lxc-start: 102: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options


These are the logfile contents:

Code:
lxc-start 102 20200523192033.310 INFO     lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor

lxc-start 102 20200523192033.310 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"

lxc-start 102 20200523192038.995 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/mapper/pve-vm--102--disk--0.


lxc-start 102 20200523192038.995 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: command 'mount /dev/dm-7 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32


lxc-start 102 20200523192039.356 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 32

lxc-start 102 20200523192039.362 ERROR    start - start.c:lxc_init:804 - Failed to run lxc.hook.pre-start for container "102"

lxc-start 102 20200523192039.364 ERROR    start - start.c:__lxc_start:1903 - Failed to initialize container "102"

lxc-start 102 20200523192039.374 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"

lxc-start 102 20200523192039.475 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: umount: /var/lib/lxc/102/rootfs: not mounted


lxc-start 102 20200523192039.475 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: command 'umount --recursive -- /var/lib/lxc/102/rootfs' failed: exit code 1


lxc-start 102 20200523192039.483 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 1

lxc-start 102 20200523192039.483 ERROR    start - start.c:lxc_end:971 - Failed to run lxc.hook.post-stop for container "102"

lxc-start 102 20200523192039.483 ERROR    lxc_start - tools/lxc_start.c:main:308 - The container failed to start

lxc-start 102 20200523192039.483 ERROR    lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options

lxc-start 102 20200523192258.146 INFO     lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor

lxc-start 102 20200523192258.146 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"

lxc-start 102 20200523192303.715 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/mapper/pve-vm--102--disk--0.


lxc-start 102 20200523192303.715 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: command 'mount /dev/dm-7 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32


lxc-start 102 20200523192303.724 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 32

lxc-start 102 20200523192303.724 ERROR    start - start.c:lxc_init:804 - Failed to run lxc.hook.pre-start for container "102"

lxc-start 102 20200523192303.724 ERROR    start - start.c:__lxc_start:1903 - Failed to initialize container "102"

lxc-start 102 20200523192303.724 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"

lxc-start 102 20200523192304.191 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: umount: /var/lib/lxc/102/rootfs: not mounted


lxc-start 102 20200523192304.191 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: command 'umount --recursive -- /var/lib/lxc/102/rootfs' failed: exit code 1


lxc-start 102 20200523192304.199 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 1

lxc-start 102 20200523192304.199 ERROR    start - start.c:lxc_end:971 - Failed to run lxc.hook.post-stop for container "102"

lxc-start 102 20200523192304.199 ERROR    lxc_start - tools/lxc_start.c:main:308 - The container failed to start

lxc-start 102 20200523192304.199 ERROR    lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options

lxc-start 102 20200523192809.737 INFO     lsm - lsm/lsm.c:lsm_init:29 - LSM security driver AppArmor

lxc-start 102 20200523192809.737 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"

lxc-start 102 20200523192815.432 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/mapper/pve-vm--102--disk--0.


lxc-start 102 20200523192815.432 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: command 'mount /dev/dm-7 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32


lxc-start 102 20200523192815.441 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 32

lxc-start 102 20200523192815.441 ERROR    start - start.c:lxc_init:804 - Failed to run lxc.hook.pre-start for container "102"

lxc-start 102 20200523192815.441 ERROR    start - start.c:__lxc_start:1903 - Failed to initialize container "102"

lxc-start 102 20200523192815.441 INFO     conf - conf.c:run_script_argv:340 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"

lxc-start 102 20200523192815.911 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: umount: /var/lib/lxc/102/rootfs: not mounted


lxc-start 102 20200523192815.911 DEBUG    conf - conf.c:run_buffer:312 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: command 'umount --recursive -- /var/lib/lxc/102/rootfs' failed: exit code 1


lxc-start 102 20200523192815.919 ERROR    conf - conf.c:run_buffer:323 - Script exited with status 1

lxc-start 102 20200523192815.919 ERROR    start - start.c:lxc_end:971 - Failed to run lxc.hook.post-stop for container "102"

lxc-start 102 20200523192815.919 ERROR    lxc_start - tools/lxc_start.c:main:308 - The container failed to start

lxc-start 102 20200523192815.919 ERROR    lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority o



This is the container configuration:

Code:
rch: amd64
cores: 1
hostname: owncloud
memory: 2048
nameserver: 10.0.0.1
net0: name=eth0,bridge=vmbr0,gw=10.0.0.1,hwaddr=DE:22:E8:25:2D:79,ip=10.0.0.101/24,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-102-disk-0,size=200G
swap: 512


And my proxmox version is Virtual Environment 6.2-4
 
Hi, glad you solved your issue.

As thread starter you can mark your own threads as solved yourself, at the top right there's a menu with "Edit Thread" where you can set the "Solved" tag.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!