Search results

  1. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    LXC Containers starts (and started) correctly... root@frigatelxc ~# systemctl status docker.service * docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue...
  2. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    Sorry, to be 100% sure... this file still is: /etc/pve/lxc/108.conf: arch: amd64 cores: 4 features: mount=cifs,nesting=1 hostname: frigatelxc memory: 8192 nameserver: 192.168.1.90 192.168.1.91 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=b2:72:05:93:9e:23,ip=dhcp,type=veth onboot: 1 ostype...
  3. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    root@proxmox02:/tmp# nano lxc-108.log GNU nano 5.4 lxc-108.log * lxc-start 108 20220315175112.114 INFO seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for...
  4. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    also tried to restore a backup with unpriviliged ticked: recovering backed-up configuration from 'local:backup/vzdump-lxc-108-2022_03_15-18_18_36.tar.zst' Logical volume "vm-112-disk-0" created. Creating filesystem with 10485760 4k blocks and 2621440 inodes Filesystem UUID...
  5. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    root@proxmox02:/tmp# nano lxc-108.log GNU nano 5.4 lxc-108.log * lxc-start 108 20220315173626.589 INFO start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWCGROUP lxc-start 108 20220315173626.589...
  6. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    Like this in /etc/pve/lxc/xxx.conf? arch: amd64 cores: 4 features: mount=cifs,nesting=1 hostname: frigatelxc memory: 8192 nameserver: 192.168.1.90 192.168.1.91 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=b2:72:05:93:9e:23,ip=dhcp,type=veth onboot: 1 ostype: debian rootfs...
  7. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    Help? please :) my /etc/fstab is: # <file system> <mount point> <type> <options> <dump> <pass> /dev/pve/root / ext4 errors=remount-ro 0 1 UUID=28B2-94D6 /boot/efi vfat defaults 0 1 /dev/pve/swap none swap sw 0 0 proc /proc proc defaults 0 0 From here...
  8. S

    Can't start LXC with docker nested after upgrade from 6 to 7

    Help. not a expert here... I have sent a lot of time reading here and there andI need help. I have upgrade from 6 to 7 and now my nested LXC containers running docker inside them won't start anymore. Some output. I tried lastly: pct set 108 --mp0 /lib/modules/$(uname...
  9. S

    2 nodes 10gbps cross cable

    Hi, what is the cheapest way to connect 2 nodes (nuc) with 10bgps ethernet? Is it possible to have usbc to usbc and emulate ethernet or something similar?
  10. S

    Convert local-lvm to zfs on a single disk cluster-installation

    So I have added my 2nd node in a proxmox cluster :-). I wanted to use "replicate" and discovered I needed ZFS for that... bump. So I have been crawling this forum and google and fund no clear answer. Without reinstalling the entire host, is it possible to convert local-lvm to zfs? What is the...
  11. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Ok fair enough... So I have another NUC8i5 with different memory (samsung) and different SSD (NVME). What is the best/easiest way to fully migrate allcontainers/VMs from one to another system? Ik think that sounds like the best way to rule out... That outher NUC8i5 with samsung mem and 1TB...
  12. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Hi, thanks for the replies. No this is a fresh system installed with Proxmox. Why am I not receviing a reply to the simple question... where can I see the log to se what happened? Ofcourse I can start stressing the hardware with all kinds of 3rd party software... but that takes time, efferot...
  13. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Is this really Proxmox? I have asked many times for help... "how" to see the logs after crash. I cannot find them... I appreciate some help with this ever ongoing issue...
  14. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Can I please get some usefull assistance? It keeps crashing every now and then. I am fully up to date with all firmware and updates etc. It lasts some days up to a week and then crashes... the most annoying now is after power cycle (only way to get it going) all logging is gone... how can I...
  15. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Can I please receive some help on this error? Where can I find those "Machine check events logged"?
  16. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    And again it crashed with a new nuc! This must be software. Please assist... Where can I find those "Machine check events logged"?
  17. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    I crashed again after 4 day thus now. Where is the information written in the logs and how can I find them? I really want this to stay stable... and swapping hardware is an option, but what to swap? The NUC, the SSD, the MEM? All is brand new and works for a longer while (now 4 days). This is...
  18. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    Easy to say... the error messag is different after each "action/update"...
  19. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    FFS! I upgraded to the newest kernel: pve-manager/6.4-6/be2fa32c (running kernel: 5.11.17-1-pve) And it crashed again! It is now getting very frustrating since it really totally hangs till Christmas and beyond. I believe I have the most standard thinkable hardware setup in the market currently...
  20. S

    Frequent crashes - [Hardware Error] CPU RIP TSC PROCESSOR - Kernal panic

    I happened again and it is starting to get pretty annoying... I think I am on the verge of leaving proxmox for what it is... I do not want to but I will upgrade to newer kernel...