Search results

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

This one?

local-lvm storage exist

Here are the results: root@pve:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-a-tz-- <1.67t 0.00 0.15 root pve -wi-ao---- 96.00g...

[CODE ]root@pve:~# lvs -o name,metadata_percent,data_percent,chunk_size,size --all LV Meta% Data% Chunk LSize data 0.15 0.00 64.00k <1.67t [data_tdata] 0 <1.67t [data_tmeta] 0 15.81g [lvol2_pmspare]...

root@pve:~# lvscan ACTIVE '/dev/pve/swap' [4.00 GiB] inherit ACTIVE '/dev/pve/root' [96.00 GiB] inherit ACTIVE '/dev/pve/data' [<1.67 TiB] inherit inactive '/dev/pve/vm-108-disk-0' [100.00 GiB] inherit inactive '/dev/pve/vm-109-disk-0'...

# pvscan -vvv root@pve:~# pvscan -vvv Parsing: pvscan -vvv Recognised command pvscan_display (id 123 / enum 105). Sysfs filter initialised. Internal filter initialised. Regex filter initialised. LVM type filter initialised. Usable device filter initialised (scan_lvs 0). mpath...

After accidentally reboot, pve-data is missing. Here is the lsblk: root@pve:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 1G 0 part /boot/efi └─sda3 8:3 0 1.8T 0...

An OVA (Open Virtualization Appliance) file is a package used to distribute virtual machines. It contains a complete virtual machine image, including the operating system, applications, and any required configuration settings. OVA files are often used to distribute virtual appliances and make it...

Since instruction in documentation not complete (you must open several links) here the steps you need to do: 1. nano /etc/default/grub 2. find GRUB_CMDLINE_LINUX_DEFAULT="quiet" 3. change to GRUB_CMDLINE_LINUX_DEFAULT="systemd.unified_cgroup_hierarchy=0 quiet" 4. run update-group 5. restart...

Any plan Proxmox VE will have Incremental Backup?

Just testing today this bug still exist on Proxmox 7.4, using Huawei RH1288V3.

Solved, see: https://forum.proxmox.com/threads/webui-console-xterm-js-not-working.91230/

SSL Certicate working fine, But still error : Connection failed (Code 1006). Again, using noVNC for shell working fine, error only on default xterm.js

http://download.proxmox.com/images/system/

This guide is useless, because I still can access 8006, so do the Hacker sir :) and put nginx mean give more oppurtunity for hacker, also make additional server load

Does this will change port so hacker can not access 8006 anymore?

5 years ago, users asked how to change Proxmox port 8006. Is it possible now?