All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
proxmox containers not starting
Seems like some issue with lvm
lxc-start 20170525112850.347 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 32 lxc-start 20170525112850.347 ERROR lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "101". lxc-start 20170525112850.347 ERROR lxc_start - start.c:__lxc_start:1313 - Failed to initialize container "101". lxc-start 20170525112855.353 ERROR lxc_start_ui - tools/lxc_start.c:main:365 - The container failed to start. lxc-start 20170525112855.353 ERROR lxc_start_ui - tools/lxc_start.c:main:367 - To get more details, run the container in foreground mode. lxc-start 20170525112855.353 ERROR lxc_start_ui - tools/lxc_start.c:main:369 - Additional information can be obtained by setting the --logfile and --logpriority options.
' ACTIVE '/dev/vmdata/vmstore' [500.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-101-disk-1' [20.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-102-disk-1' [100.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-103-disk-1' [100.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-104-disk-1' [50.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-105-disk-1' [30.00 GiB] inherit
ACTIVE '/dev/vmdata/vm-105-disk-2' [100.00 GiB] inherit
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [34.00 GiB] inherit
ACTIVE '/dev/pve/data' [78.45 GiB] inherit'
'NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 136.7G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 256M 0 part
└─sda3 8:3 0 136.5G 0 part
├─pve-root 251:0 0 34G 0 lvm /
├─pve-swap 251:11 0 8G 0 lvm [SWAP]
├─pve-data_tmeta 251:12 0 80M 0 lvm
│ └─pve-data-tpool 251:14 0 78.5G 0 lvm
│ └─pve-data 251:15 0 78.5G 0 lvm
└─pve-data_tdata 251:13 0 78.5G 0 lvm
└─pve-data-tpool 251:14 0 78.5G 0 lvm
└─pve-data 251:15 0 78.5G 0 lvm
sdb 8:16 0 838.3G 0 disk
└─sdb1 8:17 0 838.3G 0 part
├─vmdata-vmstore_tmeta 251:1 0 100M 0 lvm
│ └─vmdata-vmstore-tpool 251:3 0 500G 0 lvm
└─vmdata-vmstore_tdata 251:2 0 500G 0 lvm
└─vmdata-vmstore-tpool 251:3 0 500G 0 lvm
'
willing to pay 50EUR if someone has time to take a look, would spare me some hours of work to reinstall
Comments
Did you try restarting the container in foreground mode to see what it's complaining about? Although if it's "some issue with lvm" whereas LXC and LVM are two very different things, probably would be best to just throw money at someone.
yup, as I seed in initial post, I'm willing to throw some money
lxc-start -n 101 -F -l DEBUG -o /tmp/lxc-101.log
mount: /dev/mapper/vmdata-vm--101--disk--1: can't read superblock
command 'mount /dev/mapper/vmdata-vm--101--disk--1 /var/lib/lxc/101/rootfs//' failed: exit code 32
lxc-start: conf.c: run_buffer: 405 Script exited with status 32.
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "101".
lxc-start: start.c: __lxc_start: 1321 Failed to initialize container "101".
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.