Search results

In this case try to use `post-up iptables` as i posted above. You have to change the <port> and <VM or CT Ip address>:<PORT>

Hi, The journalctl/syslog should give you what cause the issue. You can generate the syslog in a specific time using the following command: journalctl --since '2024-11-11 00:00:00' --until '2024-11-11 08:50:15' > /tmp/$(hostname)-syslog.txt You may have to edit the date/time in the above...

Can you please re-check if the iommu parameter is correct in the /etc/default/grub? I would also try test boot from an older kernel to narrow down the issue.

Hi, Did you check the older Proxmox-kernel?

No not need to write in the ceph.conf and not need to do a reboot. On a single node will propagate. However, you can run the following command on all the nodes to make sure that the scrub load did on all the nodes. ceph config get osd osd_scrub_load_threshold

Hi, can you please post the network configuration of the Proxmox VE `cat /etc/network/interface` and the LXC config `pct config <CTID>`? In general you can do that as the following in the network configuration of Proxmox VE: post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport <PORT>...

This issue not related to Proxmox. However, could you please post the ` /etc/apt/sources.list` content. + ping to the `security.debian.org`.

Same request here? https://forum.proxmox.com/threads/disk-raw-container-proxmox-6-recovery-lxc-proxmox-8.157190/ If yes, you can do that using dd, it's deadened on the target storage type. However, if you have a backup the process will easier.

Hi, Can you please post the output of `df -h`? Yes, its possible if you have a valid backup of your VMs and the /etc/pve/

You can set the scrub load threshold [0] as the following: ceph config set osd osd_scrub_load_threshold 2.0 [0] https://docs.ceph.com/en/quincy/rados/configuration/osd-config-ref/#confval-osd_scrub_load_threshold

Hi, Yes, I can confirm that I installed the Proxmox VE on `ASUS NUC 13 Pro` and everything works smoothly.

Hi, Can you check if the Network Device inside the Windows is installed i.e., open the Device Manager and check if the Red Hat VirtIO Etherenet Adapter is installed. If yes, could you please try to set the Network to the VM to `Intel E1000`?

Could you please post the network configuration `cat /etc/netwrok/interfaces` and the output of `ip a`?

Thank you for the syslog! Could you please check the disk health using `smartctl`? smartctl -a /dev/sdb Since the `Input/output error (os error 5)` points to a hardware issue.

Can you please check the output of the `ip route` in the VM? The output should indicate your gateway `192.168.1.1`. Additionally, what say the ping to the gateway?

I would first check if the VM is already set to the `vmbr1` and check if the firewall is enabled.

Can you check the syslog for more entries? I would also try to restart the following services: systemctl restart proxmox-backup proxmox-backup-proxy

Hi, The full SMB storage impacted the pvestatd daemon, which can cause the Proxmox VE Web UI to become unresponsive. I would check the syslog around the backup time. You can also restart the pvestatd and pveproxy services.

Hi, Could you please check if that storage disks are properly connected or/and mounted?

Hi, Can you check if the NIC have an available firmware update? Sometimes the firmware update can help. and/plus check if you have microcode is installed in your Proxmox VE.