Cant start ct after shutdown

nzucode

New Member
Dec 22, 2022
5
0
1
i have log
cat lxc-102_1.log
lxc-start 102 20221222045602.970 INFO confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 102 20221222045602.970 INFO confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 102 20221222045602.970 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 102 20221222045602.970 INFO conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"
lxc-start 102 20221222045959.139 DEBUG conf - ../src/lxc/conf.c:run_buffer:310 - 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 20221222045959.139 DEBUG conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: command 'mount /dev/dm-6 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32

lxc-start 102 20221222045959.161 ERROR conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 32
lxc-start 102 20221222045959.161 ERROR start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "102"
lxc-start 102 20221222045959.161 ERROR start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "102"
lxc-start 102 20221222045959.161 INFO conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"
lxc-start 102 20221222050000.434 DEBUG conf - ../src/lxc/conf.c:run_buffer:310 - 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 20221222050000.434 DEBUG conf - ../src/lxc/conf.c:run_buffer:310 - 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 20221222050000.452 ERROR conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 1
lxc-start 102 20221222050000.452 ERROR start - ../src/lxc/start.c:lxc_end:988 - Failed to run lxc.hook.post-stop for container "102"
lxc-start 102 20221222050000.452 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 102 20221222050000.452 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the

I can't start my ct
 
/var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/mapper/pve-vm--102--disk--0. sounds like a corrupt disk.. is your storage looking okay?
 

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!