Search results

All above has been executed, to make sure I run them again here: root@poweredge:~# apt clean root@poweredge:~# apt update Hit:1 http://ftp.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Get:3 http://ftp.debian.org/debian...

any chance to update this proxmox 7?

Have tried apt full-upgrade and apt dist-upgrade but the result still same: root@poweredge:~# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and...

Just run #apt upgrade on Proxmox 7, but error. root@poweredge:~# pveversion pve-manager/7.4-20/5d6e3351 (running kernel: 5.15.30-2-pve) root@poweredge:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done...

This also happen on aaPanel on Debian 12, while Debian 11/Ubuntu 20.04 has no issue. Solution using "ExecStart=/usr/bin/lxcfs -l /var/lib/lxcfs/" has no effect on Proxmox 8.4.1. The "top" command report right cpu load, so this issue may not related to LXC, but how Zabbix and aaPanel interact to...

Is there something like QDevice for ceph?

Great .. Just add suggestion tp show QDevice on Datacenter - Summary: Status, Nodes, QDevice. https://bugzilla.proxmox.com/show_bug.cgi?id=2760#c8

more than 3 years, but I still wondering why only 1 node Online but Quorum is okay? just because I don't see the little QDevice :D

I face similar issue, the solution is using ifreload, but you must install it first because the app come from ifupdown2 package: # apt install ifupdown2 After installed then: # ifreload -a

Using external drive or SD Card for Proxmox boot is not a good idea. I suggest you boot Proxmox from RAID 1 disk (by default Proxmox use EXT4) and setup another disk using RAID 0 for ZFS. Or you may set each drive as RAID 0 then use ZFS. Because DL380 Gen 8 not support mixed mode yet (I see...

Latest version of Win 11 (24H2) delete OOBE/BYPASSNRO command, so you must use: start ms-cxh:localonly Also after Shift + F10 you can open Control Panel by typing: Control

As fabian mention you can use: - Intel Nahelem - Amd Opteron gen4 - or just use Host

So this is not a good work around, since "nesting" very dangerous in this case. I just test it again and still an issue on: proxmox-ve: 8.2.0 (running kernel: 6.2.16-3-pve) pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)

What do you mean by "uncontained"? Does this mean the CT can disturb the node itself? Should we avoid it then use Unprivileged instead?

Asking same question, but I dropped to this thread. Now it is possible to use Clipboard, see: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_display

To make this topic focus, because I have put the broken disk to new Proxmox server then let's discuss to: - https://forum.proxmox.com/threads/when-activated-lv-device-mapper-reload-ioctl-on-253-8-failed-no-data-available.150741/

The Proxmox server rebooted then LV fail, so I installed new Proxmox and old proxmox renamed to pve2. Here are what I have tried: # lsblk # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0...

Refer to: https://unix.stackexchange.com/questions/704434/lvm-vgchange-device-mapper-reload-ioctl-on-failed-no-data-available I think I will re-create the metadata like: thin_dump /dev/mapper/pve-data_tmeta -o dump.txt What is your suggestion?

When try to running VM --> TASK ERROR: activating LV 'pve/vm-100-disk-1' failed: device-mapper: reload ioctl on (253:6) failed: No data available