Recent content by justjosh

  1. Unable to start all LXC after reboot

    proxmox-ve: 6.2-2 (running kernel: 5.4.60-1-pve) pve-container: 3.2-1 Doesn't seem to be any errors for zfs on boot. Container only shows the failure to start exit code 1. Not sure if it's got to do with the root delay I placed for boot because the pools are encrypted. # journalctl -b | grep...
  2. Unable to start all LXC after reboot

    I have been cleaning the directories after every reboot but it keeps getting created once I reboot the host but it is very annoying and time consuming since I need to make sure each directory is actually empty before removing. I need a way to stop the PCT from mounting the directory before the...
  3. Ubuntu 18.04 LXC container wrong gateway.

    Would like to confirm that I have the exact same issue with pihole as well and fixed it by editing dhcpcd.conf
  4. Unable to start all LXC after reboot

    Where should I look for the logs possibly related to this? I have some CTs that directly mount directories from the ZFS pool. For example, CT102 has mp0 = /mnt/shared_a/ I've noticed that when I do a ls -l of the volume, these mount points exist in the subvol disk but with size 0 and empty...
  5. Unable to start all LXC after reboot

    # zfs get all SSD/subvol-101-disk-0 NAME PROPERTY VALUE SOURCE SSD/subvol-101-disk-0 type filesystem - SSD/subvol-101-disk-0 creation Fri Sep 25 8:02 2020 - SSD/subvol-101-disk-0 used...
  6. Unable to start all LXC after reboot

    I've just upgraded to 6.2 and rebooted. The CTs won't start. mount_autodev: 1074 Permission denied - Failed to create "/dev" directory lxc_setup: 3238 Failed to mount "/dev" do_start: 1224 Failed to setup container "101" __sync_wait: 41 An error occurred in another process (expected sequence...
  7. Unable to start all LXC after reboot

    So I just tried to do a vzdump of a container and it tripped the ZFS mount issue again. All volumes disappeared. # ls -l /SSD total 0 I've never seen it do this while everything was running. vzdump ended with error: unexpected status. INFO: starting new backup job: vzdump 102 --remove 0...
  8. Proxmox Backup Server (beta)

    vzdump of turnkey linux templates would not restore properly in unpriviledged containers because of postfix directory. There was a not so simple fix of excluding directories via CLI backup/restore. Is this process made simpler with the backup server...
  9. Unable to start all LXC after reboot

    pve-container: 3.0-14 The subvolumes are mounted but with an empty dev directory. Is it the same issue? Is it safe to upgrade to 6.2 with this error?
  10. Proxmox Backup Server (beta)

    Does this fix the postfix issue with unpriviledged containers in vzdump?
  11. Unable to start all LXC after reboot

    Not sure which version you're looking for. I've been meaning to upgrade to 6.2 but not going to do it until this issue is fixed. Don't want to risk breaking anything else. # pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve) pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)...
  12. Unable to start all LXC after reboot

    After further investigation, I managed a temporary bandaid fix by remounting every disk by hand. Not very practical and root cause is not fixed yet either. #rm -rf /SSD/subvol-101-disk-0/dev/ zfs mount /SSD/subvol-101-disk-0 ...
  13. Unable to start all LXC after reboot

    Using zfs mount -O SSD does cause the volumes to show up but the log output is still the same when trying to start the CT. # zfs mount -O SSD Unfortunately, it seems that the volumes are of the wrong size with this mount. # ls /SSD -l --block-size=M total 1M drwxr----- 3 root root 1M Sep 25...
  14. Unable to start all LXC after reboot

    lxc-start 101 20200925021614.161 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type u nsid 0 hostid 100000 range 65536 lxc-start 101 20200925021614.161 INFO confile - confile.c:set_config_idmaps:2003 - Read uid map: type g nsid 0 hostid 100000 range 65536 lxc-start 101...
  15. Unable to start all LXC after reboot

    Hi guys, I recently made a network change so I had to reboot proxmox. Before rebooting all CTs were working perfectly and I had just spun up a new LXC right before reboot. Sep 25 09:42:57 proxmox systemd[1]: Starting PVE LXC Container: 101... Sep 25 09:42:58 proxmox lxc-start[4603]...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!