I can't start LXC

[emanuelebruno]

Hi, after Proxmox update (from 7.0-x to 7.1-7) one container doesn't start correctly... It freezes at startup:

Executing the container with the debug option, this is the output:

I have attacched the log file with the hope that someone can help me.

This is the configuration file:
arch: i386
cores: 4
hostname: xxx.xxx.xxx
memory: 4096
nameserver: 127.0.0.1 213.186.33.99
net0: name=eth0,bridge=vmbr8,gw=192.168.1.1,hwaddr=xx:xx:xx:xx:xx:xx,ip=192.168.1.100/24,type=veth
onboot: 0
ostype: ubuntu
rootfs: disco3:vm-105-disk-0,size=250G
searchdomain:xxx.xxx
startup: order=6
swap: 4096

PS: this is my pve version

proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-12
pve-kernel-5.15: 7.2-10
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.6-1
proxmox-backup-file-restore: 2.2.6-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-2
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

 

[leesteken]

Please also attach the container configuration file (/etc/pve/lxc/105.conf).

 

[emanuelebruno]

This is the configura

Please also attach the container configuration file (/etc/pve/lxc/105.conf).

ok thank you

 

[alexskysilk]

fsck -fy /path/to/your/vdisk. if you explain what type of pool is disco3, could give more exact syntax.

 

[emanuelebruno]

fsck -fy /path/to/your/vdisk. if you explain what type of pool is disco3, could give more exact syntax.

disco3 is a lvm-thin volume...

digiting "fsck -fy /dev/mapper/disco3-vm--105--disk--0" this is the output:

fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
Pass 1: Checking inodes, blocks, and sizes
Inode 12473802 extent tree (at level 1) could be shorter. Optimize? yes
Inode 12483321 extent tree (at level 1) could be shorter. Optimize? yes
Inode 12484686 extent tree (at level 1) could be shorter. Optimize? yes
Inode 12494738 extent tree (at level 1) could be shorter. Optimize? yes
Inode 13369577 extent tree (at level 1) could be shorter. Optimize? yes
Inode 13369609 extent tree (at level 1) could be shorter. Optimize? yes
Inode 14289348 extent tree (at level 1) could be shorter. Optimize? yes
Inode 14295857 extent tree (at level 1) could be shorter. Optimize? yes
Inode 14296089 extent tree (at level 1) could be shorter. Optimize? yes
Inode 14296325 extent tree (at level 1) could be shorter. Optimize? yes
Inode 14296460 extent tree (at level 1) could be shorter. Optimize? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/disco3-vm--105--disk--0: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/disco3-vm--105--disk--0: 7447734/16384000 files (0.1% non-contiguous), 49522716/65536000 blocks

 

[alexskysilk]

try starting it now. if its still breaks your container is broken. make a new one- and you can always recover your data by mounting the old disk, either on the hypervisor or in the new container.

 

[emanuelebruno]

try starting it now. if its still breaks your container is broken. make a new one- and you can always recover your data by mounting the old disk, either on the hypervisor or in the new container.

It is not broken. I have a backup (of some months ago) of the container before proxmox update and it is the same: it can't start and I don't want to downgrade proxmox for starting the container again...