[SOLVED] Failed to start CentOS LXC

[Editor]

I get this latest error:

/lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

I wanted to restart the server and turned it off. I can't open it back now. And I deleted the backup this morning (unlucky.. did hdd cleaning)

How do I open this container on Proxmox?

Proxmox Error screen:

root@prox:~# systemctl status pve-container@104.service
● pve-container@104.service - PVE LXC Container: 104
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-12-22 10:19:13 EET; 17s ago
    Docs: man:lxc-start
          man:lxc
          man:pct
  Process: 25537 ExecStart=/usr/bin/lxc-start -n 104 (code=exited, status=1/FAILURE)

Dec 22 10:19:12 prox systemd[1]: Starting PVE LXC Container: 104...
Dec 22 10:19:13 prox systemd[1]: pve-container@104.service: Control process exited, code=exited status=1
Dec 22 10:19:13 prox systemd[1]: Failed to start PVE LXC Container: 104.
Dec 22 10:19:13 prox systemd[1]: pve-container@104.service: Unit entered failed state.
Dec 22 10:19:13 prox systemd[1]: pve-container@104.service: Failed with result 'exit-code'.

root@prox:~# pct fsck 104
fsck from util-linux 2.29.2
/calisanHDD/images/104/vm-104-disk-0.raw is mounted.
e2fsck: Cannot continue, aborting.


command 'fsck -a -l /calisanHDD/images/104/vm-104-disk-0.raw' failed: exit code 8

root@prox:~# lxc-start -n 104 -F -l DEBUG -o /tmp/lxc-ID.log
lxc-start: 104: conf.c: run_buffer: 353 Script exited with status 2
lxc-start: 104: start.c: lxc_init: 828 Failed to run lxc.hook.pre-start for container "104"
lxc-start: 104: start.c: __lxc_start: 1914 Failed to initialize container "104"
lxc-start: 104: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: 104: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options

Spoiler: PVEversions

proxmox-ve: 5.3-1 (running kernel: 4.15.18-4-pve)
pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df)
pve-kernel-4.15: 5.2-12
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.15.15-1-pve: 4.15.15-6
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-3-pve: 4.13.16-50
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.13-1-pve: 4.13.13-31
pve-kernel-4.13.8-3-pve: 4.13.8-30
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.8-1-pve: 4.13.8-27
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-3-pve: 4.10.17-23
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-34
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
openvswitch-switch: 2.7.0-3
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

Proxmox 5.3.6

I'm waiting for your help.
Thank you.

 

[Editor]

I solved.