Search results

  1. H

    how to restore a container from an old ssd?

    Or how do I restore a backup but use the old raw or subvol stores on the zfs storage?
  2. H

    how to restore a container from an old ssd?

    I have no idea where the config files have been gone? Can it be that the fresh installed NVMI deleted these config files? Is it possible to extract the config file of an older vm/lxc backup?
  3. H

    how to restore a container from an old ssd?

    Sorry for adding my question to this. I have a similar issue but I want to copy my old vm config files to my new instalation my pve-OLD-xxxx/root is successfully mounted but I can not find any *.conf file in the folder /mnt/oldroot/etc/pve it is just empty If I look in /mnt/oldroot/etc/lxc...
  4. H

    can not ping to DNS Server but other IPs are OK

    BTW, it worked with this config for years ...
  5. H

    can not ping to DNS Server but other IPs are OK

    I deleted it. Is there a reboot necessary? ping -c 4 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. --- 192.168.100.1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3053ms is this what you needed? ip r default via 192.168.100.1 dev vmbr0...
  6. H

    can not ping to DNS Server but other IPs are OK

    I hope I am posing the right ones: The second DNS entry here had been added recently for testing reason after the issue occured. on IP 2 there is an addguard home server. But it did not solve it
  7. H

    can not ping to DNS Server but other IPs are OK

    Hello, I am running 7.4-17. I recognized that there is some issue because apt update were not able to receive new packages. I tried from my PVE host: ping -c 4 192.168.100.1 #(my fritz box) or ping -c 4 google.com both results in all lost if I try an other internal IP 192.168.100.22 it is...
  8. H

    GUI Plötzlich nicht mehr erreichbar

    Hallo, ich weiß, dass das Thema schon paar Monate her ist, aber ich habe GENAU das gleiche Problem. Hattest du da damals eine Problem/Lösung gefunden? Danke
  9. H

    PVE host not accessible after power shutdown; VMs working

    I receive this: but if I am doing docker -v I am receiving an error??? 6: tap122i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr122i0 state UNKNOWN group default qlen 1000 link/ether 16:b6:77:9f:a3:b7 brd ff:ff:ff:ff:ff:ff 7: fwbr122i0...
  10. H

    PVE host not accessible after power shutdown; VMs working

    docker is installed in some LXC but not directly on the host. ..?!
  11. H

    PVE host not accessible after power shutdown; VMs working

    I checked status of sshd/ssh/pveproxy services. all are active afaik there I have no firewall on this server only on router checking dmesg I have a lot of this one:
  12. H

    PVE host not accessible after power shutdown; VMs working

    When I plugged a display into the server, this showed up first 192.168.100.22 is accessible by others
  13. H

    PVE host not accessible after power shutdown; VMs working

    Hello, we had an issue with our power supply. Proxmox server was killed by no power supply. After restarting the engine, I was able to SSH in and it looked quite ok. After running for a few hours I am not able to access Web GUI neither SSH. Fun fact: all VMs / LXCs are running like expected...
  14. H

    cannot prepare PCI pass-through, IOMMU not present

    This is exactly the grub file from my proxmox host which is working with 5.15.30-2 and it is working. I do not remember that I change something in grub I just added the PCI Controller to the VM conf file. I did not change something. As I wrote, after a reboot (probably with installing new...
  15. H

    cannot prepare PCI pass-through, IOMMU not present

    GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX=""
  16. H

    cannot prepare PCI pass-through, IOMMU not present

    I tried it now with 5.15.30-2 and this worked 5.15.35-2 brought up all the errors ....
  17. H

    cannot prepare PCI pass-through, IOMMU not present

    Hello, my Proxmox Server was running for years and always the PCI pass-through worked like a charm. Yesterday night I did a reboot and today I recognized my fileserver (the vm with the passed through PCI) did not start. I did a journal log but I will not be smarter with it. May I ask you for...
  18. H

    Proxmox VE nach 6to7 Update nicht mehr erreichbar

    Hab die Lösung gefunden für die Container. "Einfach" acuh diese auf bullseye upgraden, analog proxmox. Es läuft wieder alles JUHU
  19. H

    Proxmox VE nach 6to7 Update nicht mehr erreichbar

    Ich habe vor lauter Verzweiflung neu installiert. Hat etwas gedauert aber zumindest die VMs laufen wieder die Container mit docker leider nicht. Wärend ich jetzt mehrfach installiert habe hab ich rausgefunden, dass sich zfs mit dsk-VMs an dem "-" verschluckt hat. Hätte wohl gereicht das...
  20. H

    Proxmox VE nach 6to7 Update nicht mehr erreichbar

    Hallo zusammen, ich hab heute das Update von 6.4 auf 7.2 nach der step/step Anleitung durchgeführt. Leider komme ich nicht mehr auf die GUI. Mit einem Monitor und Tastatur direkt am Server komme ich an den Server ran. SSH geht nicht. Ping kann ich nichts erreichen. Das ist die Fehlermeldung...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!