One other thing to mention... Shutdowns and lost networks shouldn't be a problem. I have my NAS, my router, and a NUC (proxmox host) all running off a UPS battery backup. If the power blinks or even goes out for 30 minutes, everything keeps running. I also get emails from the NAS any time it...
OK. So I’ve done the following, which may prove helpful. I’m also happy to run further commands. I genuinely don’t understand why I’m having trouble running containers off the NAS, especially since they all happily start up the first time but then refuse to boot later.
Here’s the steps I took...
Thank you so much Stoiko!
Yes, running off the NAS was the issue. I'm new to Proxmox but also Linux and have been trying really hard to learn enough to be competent.
I must have inadvertently setup the container that way because Proxmox prompted me to use the NAS in the GUI for the rootfs. I...
Anyone? I would be so grateful for some help. It's so disheartening to spend the better part of two days trying to troubleshoot and writeup a lengthy documentation with logs and then get no response. Surely Proxmox isn't supposed to be behaving this way?
[CONTINUING]
A manual — and successful — start of the 999 container after rebooting the host produces:
root@pve:~# lxc-start -n 999 -F -l DEBUG -o debug.txt -- [See file attachment...]
Looking at zpool.cache with strings reveals:
root@pve:~# strings /etc/zfs/zpool.cache
rpool
version
name...
I’m at my wits ends and would be incredibly grateful for any help fixing this. I’ve got a situation where lxc containers successfully boot the first time only, upon starting up the Proxmox node. However, once you shutdown a container (or reboot a container), the container simply will not boot...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.