LXC Container startet nicht mehr ---HILFE----

Danny1605

Member
Apr 6, 2020
4
0
6
36
Hallo ich hoffe mir kann jemand helfen. Nach einem reboot meins lxc Container startet dieser nicht mehr. Ich bin mit Proxmox erst seid 3 Tagen unterwegs also alles total Neuland für mich. Ich denke das es daran liegt das, dass Backup was ich gestern eingerichtet habe nicht abgeschlossen war als ich den reboot durchgeführt habe. Nur leider weiß ich nicht mehr weiter. Über eine genaue Anleitung wäre ich sehr dankbar.

Lg Danny

-------------------
Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1


root@server:~# systemctl status pve-container@100.service


pve-container@100.service - PVE LXC Container: 100

Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-04-06 11:22:03 CEST; 5s ago


Docs: man:lxc-start
man:lxc
man:pct

Process: 6959 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Apr 06 11:22:02 server systemd[1]: Starting PVE LXC Container: 100...
Apr 06 11:22:03 server lxc-start[6959]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container state
Apr 06 11:22:03 server lxc-start[6959]: lxc-start: 100: tools/lxc_start.c: main: 329 The container failed to start
Apr 06 11:22:03 server lxc-start[6959]: lxc-start: 100: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Apr 06 11:22:03 server lxc-start[6959]: lxc-start: 100: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Apr 06 11:22:03 server systemd[1]: pve-container@100.service: Control process exited, code=exited, status=1/FAILURE
Apr 06 11:22:03 server systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Apr 06 11:22:03 server systemd[1]: Failed to start PVE LXC Container: 100.
-----------


root@server:~# lxc-start -n 100 -F


lxc-start: 100: conf.c: run_buffer: 352 Script exited with status 2


lxc-start: 100: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "100"


lxc-start: 100: start.c: __lxc_start: 2032 Failed to initialize container "100"


Segmentation fault
--------------

root@server:~# pct mount 100


mounting container failed


cannot open directory //WDHD/subvol-100-disk-0: No such file or directory
---------------

Bildschirmfoto 2020-04-06 um 13.19.57.png
 
Last edited:
Hallo erst einmal viel dank für die Antwort !

Hier die Logs.




lxc-start 100 20200406123207.972 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type u nsid 0 hostid 100000 range 65536


lxc-start 100 20200406123207.973 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type g nsid 0 hostid 100000 range 65536


lxc-start 100 20200406123207.980 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor


lxc-start 100 20200406123207.980 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for reject_force_umount action 0(kill)


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)


lxc-start 100 20200406123207.981 INFO seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "[all]"


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "kexec_load errno 1"


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for kexec_load action 327681(errno)


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)


lxc-start 100 20200406123207.982 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "open_by_handle_at errno 1"


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)


lxc-start 100 20200406123207.983 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "init_module errno 1"


lxc-start 100 20200406123207.984 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for init_module action 327681(errno)


lxc-start 100 20200406123207.984 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for init_module action 327681(errno)


lxc-start 100 20200406123207.984 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for init_module action 327681(errno)


lxc-start 100 20200406123207.984 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for init_module action 327681(errno)


lxc-start 100 20200406123207.984 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "finit_module errno 1"


lxc-start 100 20200406123207.985 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for finit_module action 327681(errno)


lxc-start 100 20200406123207.985 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)


lxc-start 100 20200406123207.985 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)


lxc-start 100 20200406123207.985 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)


lxc-start 100 20200406123207.986 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"


lxc-start 100 20200406123207.986 INFO seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)


lxc-start 100 20200406123207.986 INFO seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)


lxc-start 100 20200406123207.986 INFO seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)


lxc-start 100 20200406123207.987 INFO seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)


lxc-start 100 20200406123207.987 INFO seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context


lxc-start 100 20200406123207.988 INFO conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"


lxc-start 100 20200406123207.983 DEBUG conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: cannot open director$





lxc-start 100 20200406123208.253 ERROR conf - conf.c:run_buffer:352 - Script exited with status 2


lxc-start 100 20200406123208.262 ERROR start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "100"


lxc-start 100 20200406123208.273 ERROR start - start.c:__lxc_start:2032 - Failed to initialize container "100"
 
please use code-tags when pasting log-files - it makes reading them much easier!

please post the container config and your storage config:
* pct config $vmid
* cat /etc/pve/storage.cfg
 
Code:
arch: amd64
cores: 4
features: keyctl=1,nesting=1
hostname: nextcloud
memory: 8000
mp0: WDHD:subvol-100-disk-0,mp=/mnt/hdd,backup=1,size=600G
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.178.1,hwaddr=76:31:F6:21:FD:6F,ip=192.168.178.20/24,ip6=dhcp,type=veth
onboot: 1
ostype: ubuntu
parent: Install_fresh
rootfs: local-lvm:vm-100-disk-0,size=5G
startup: order=1
swap: 8000
unprivileged: 1





Code:
dir: local
    path /var/lib/vz
    content vztmpl,backup,iso

lvmthin: local-lvm
    thinpool data
    vgname pve
    content rootdir,images

zfspool: WDHD
    pool WDHD
    content rootdir,images
    mountpoint /WDHD
    nodes server

zfspool: SDHD
    pool SDHD
    content rootdir,images
    mountpoint /SDHD
    nodes server

nfs: MyCloud
    export /mnt/HD/HD_a2/Proxmox
    path /mnt/pve/MyCloud
    server 192.168.178.3
    content backup,images
    maxfiles 1
 
on a hunch - does the container start if you comment out the 'mp0' line?
if yes - does the container have a directory: '/mnt/hdd' inside?
 

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!