My single node Proxmox recently got very messed up. Gave up on it, killed it and reinstalled Proxmox from scratch (a couple of days ago - v. 5.4). I then restored containers from backups. However, one container (originally CT 100 and restoring to CT 100) does not start. That container had been one of the first I had created when I originally installed Proxmox (which I think was then 4.4). I had kept the old instance of Proxmox up to date (and believe it was 5.4 when it died). The container had started without issue on the old instance. The container was originally installed with Ubuntu 17.10 but then later upgraded to 18.04 without any issues. After digging through other issues (e.g. /sys/fs/cgroup/systemd/lxc/100 files were not removed after aborted start through the GUI), it seems the root cause is this entry that I found in the debug log when trying to start the container in the foreground (i.e. "lxc-start -n 100 -F -l DEBUG -o lxc100dbg.log": Code: lxc-start 100 20190421043428.136 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start with output: unable to detect OS distribution I've reviewed all the threads I could find referencing this message and it almost always points to a missing or corrupted file in /etc of the container. I mounted the container filesystem (pct mount 100) and checked that debian_version and lsb-release exist, and they do. debian_version shows: Code: buster/sid While lsb-release is: Code: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" This is where I run into a dead end. I've looked through various posts that reference the same error and have looked at config files, tried restoring to a different zpool, checked the storage setup for PVE, etc. according to those posts, but didn't seem to have the same problems as cited in those threads. Tried to keep the initial post brief but have a ton of other logs, etc. so if any further info is desirable please advise. Any suggestions on how I could get the container up and running again would be most appreciated.