Yet another can't start LXC containers (Proxmox 7.2-14)

Kim A

New Member
Nov 19, 2022
6
0
1
Hi.
I've been traversing this forum for hours trying to fix my broken server.
Here's the story
  • After a restart the CT containers couldn't start - only VM starts
  • I installed all updates, and restarted - same problem.
  • I tried to restore a backup of one of the containers, which led to it being deleted - now if I re-run the backup, I get the message
    Bash:
    recovering backed-up configuration from 'vzdump-lxc...'
    TASK ERROR: unable to restore CT 104 - no such logical volume pve/5.58793544769287e-09
I have tried to get the log for starting the container, which says:

Bash:
lxc-start 105 20221119071343.623 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 105 20221119071343.623 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 105 20221119071343.623 INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 105 20221119071343.623 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "105", config section "lxc"
lxc-start 105 20221119071343.624 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 105 lxc pre-start produced output: perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LC_TIME = "en_DK.UTF-8",
        LC_MONETARY = "en_DK.UTF-8",
        LC_ADDRESS = "en_DK.UTF-8",
        LC_TELEPHONE = "en_DK.UTF-8",
        LC_NAME = "en_DK.UTF-8",
        LC_MEASUREMENT = "en_DK.UTF-8",
        LC_IDENTIFICATION = "en_DK.UTF-8",
        LC_NUMERIC = "en_DK.UTF-8",
        LC_PAPER = "en_DK.UTF-8",
        LANG = "da_DK.UTF-8"
    are supported and installed on your system.

lxc-start 105 20221119071343.624 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 105 lxc pre-start produced output: perl: warning: Falling back to a fallback locale ("da_DK.UTF-8").

lxc-start 105 20221119071343.990 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 105 lxc pre-start produced output: objdump on /usr/lib/systemd/systemd failed: open3: exec of objdump -p /var/lib/lxc/105/rootfs/usr/lib/systemd/systemd failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 455.

lxc-start 105 20221119071343.997 ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 2
lxc-start 105 20221119071343.997 ERROR    start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "105"
lxc-start 105 20221119071343.997 ERROR    start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "105"
lxc-start 105 20221119071343.997 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "105", config section "lxc"
lxc-start 105 20221119071343.998 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LC_TIME = "en_DK.UTF-8",
        LC_MONETARY = "en_DK.UTF-8",
        LC_ADDRESS = "en_DK.UTF-8",
        LC_TELEPHONE = "en_DK.UTF-8",
        LC_NAME = "en_DK.UTF-8",
        LC_MEASUREMENT = "en_DK.UTF-8",
        LC_IDENTIFICATION = "en_DK.UTF-8",
        LC_NUMERIC = "en_DK.UTF-8",
        LC_PAPER = "en_DK.UTF-8",
        LANG = "da_DK.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("da_DK.UTF-8").

lxc-start 105 20221119071344.308 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp3: not mounted.

lxc-start 105 20221119071344.308 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp3' failed: exit code 32

lxc-start 105 20221119071344.315 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp2: not mounted.

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

lxc-start 105 20221119071344.317 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp4: not mounted.

lxc-start 105 20221119071344.317 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 105 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp4' failed: exit code 32

lxc-start 105 20221119071344.358 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "105", config section "lxc"
lxc-start 105 20221119071344.859 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 105 20221119071344.859 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

It's the same with all the containers.

Is anybody capable of seeing how to get on from here?

Thanks!
 
Got it fixed. It is the update: Open a shell to your Proxmox host and type:
Bash:
sudo apt install binutils
. After that you can start your containers as usual.
 
Is this the same problem as you have https://forum.proxmox.com/threads/c...s-after-upgrading-and-disabling-iommu.118227/ ? I will try to update my backup machine. If it also fails after a restart it is the update that causes these problems.

Got it fixed. It is the update: Open a shell to your Proxmox host and type:
Bash:
sudo apt install binutils
. After that you can start your containers as usual.
I have no words - you are amazing! I've spent around 6 hours now - and lost all hope.
All containers started as you said.
Thank you extremely much!

While I have you on the line - I still have a problem with the container I tried to restore, that got deleted. I can't restore it.
The error is the same:

Bash:
recovering backed-up configuration from 'vzdump-lxc...'
TASK ERROR: unable to restore CT 104 - no such logical volume pve/5.58793544769287e-09
 
Got it fixed. It is the update: Open a shell to your Proxmox host and type:
Bash:
sudo apt install binutils
. After that you can start your containers as usual.

Got hurt by this 10 minutes ago!
Solved

Fantastic!
Thanks
 
You're welcome. How do you restore your CT? From PBS? Does your storage exist?
I believe it's because it's a snapshot. If I restore another container that is not a snapshot it runs through. I guess it's just my bad...
Anyway - I am thrilled that all is working now.
Thanks again!
 

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!