[SOLVED] Unable to start Ubuntu container

crider17

New Member
Mar 7, 2021
19
0
1
55
Hello -

I lost power today and when I booted back up my Proxmox server (6.3-3) my Ubuntu (18.04) container will not spin up. It had "Config locked (snapshot-delete)" status.

"pct unlock 100" removed the status. However, I still cannot get the container to spin up.

When I run "lxc-start -n 100 --foreground --logfile test.log --logpriority=2"

test.log says:
lxc-start 100 20210319224424.819 ERROR conf - conf.c:run_buffer:314 - Script exited with status 32
lxc-start 100 20210319224424.819 ERROR start - start.c:lxc_init:798 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20210319224424.819 ERROR start - start.c:__lxc_start:1945 - Failed to initialize container "100"
lxc-start 100 20210319224425.838 ERROR lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 100 20210319224425.838 ERROR lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options

I'm a bit over my head at this point. Any idea how I can fix this?

Thanks!
 
More detail:

root@pve:~# lxc-start -n 100 -F -lDEBUG -o lxc-100.log
lxc-start: 100: conf.c: run_buffer: 314 Script exited with status 32
lxc-start: 100: start.c: lxc_init: 798 Failed to run lxc.hook.pre-start for container "100"
lxc-start: 100: start.c: __lxc_start: 1945 Failed to initialize container "100"
lxc-start: 100: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: 100: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
root@pve:~# cat lxc-100.log
lxc-start 100 20210320013108.372 INFO lsm - lsm/lsm.c:lsm_init:40 - Initialized LSM security driver AppArmor
lxc-start 100 20210320013108.372 INFO conf - conf.c:run_script_argv:331 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20210320013108.916 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/mp2: special device /dev/sdc1 does not exist.

lxc-start 100 20210320013108.916 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: command 'mount /dev/sdc1 /var/lib/lxc/.pve-staged-mounts/mp2' failed: exit code 32

lxc-start 100 20210320013108.924 ERROR conf - conf.c:run_buffer:314 - Script exited with status 32
lxc-start 100 20210320013108.924 ERROR start - start.c:lxc_init:798 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20210320013108.924 ERROR start - start.c:__lxc_start:1945 - Failed to initialize container "100"
lxc-start 100 20210320013108.924 INFO conf - conf.c:run_script_argv:331 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "100", config section "lxc"
lxc-start 100 20210320013109.426 INFO conf - conf.c:run_script_argv:331 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc"
lxc-start 100 20210320013109.928 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 100 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp2: not mounted.

lxc-start 100 20210320013109.928 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 100 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp2' failed: exit code 32

lxc-start 100 20210320013109.951 ERROR lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 100 20210320013109.951 ERROR lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options
 
Again,
I had the same concerns after backup crash.
Removed whole entry in .conf file but snapshot remain in zfs.
Is it safe to remove it with zfs destroy rpool/data/subvol-111-disk-1@vzdump ?
 
Last edited:
Hi - seems to be working now. The system seemed to be choking on trying to mount my USB drive:
lxc-start 100 20210320013108.916 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/mp2: special device /dev/sdc1 does not exist.

So, I unplugged the drive rebooted. It booted right up. I've since reset it and plugged it back in and it seems to be fine.

Thanks.
 
test.log says:
lxc-start 100 20210319224424.819 ERROR conf - conf.c:run_buffer:314 - Script exited with status 32
lxc-start 100 20210319224424.819 ERROR start - start.c:lxc_init:798 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20210319224424.819 ERROR start - start.c:__lxc_start:1945 - Failed to initialize container "100"
lxc-start 100 20210319224425.838 ERROR lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 100 20210319224425.838 ERROR lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options
Got same errors, with a container having /etc directory moved away... seems like /etc directory is mandatory for lxc.
 

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!