Search results

Plese show your container config pct config <VMID>

https://pve.proxmox.com/wiki/Storage Not supported LVM lvm block no3 no yes

maybe you copy dd data uefi from old disk to new disk and UUID is the same. This will work too Verify this: lsblk -o +UUID blkid if you want change this, use proxmox-boot-tool format /dev/sdX2 format set new UUID proxmox-boot-tool init /dev/sdX2 (add entries) proxmox-boot-tool clean (removes...

My system mirror 2 disks proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi 4011-8644 is configured with: uefi (versions: 6.2.16-10-pve, 6.2.16-3-pve) 4013-7258 is configured with: uefi (versions: 6.2.16-10-pve...

Your old working disk 3272-7F43 has the partitions? partition 1 BIOS boot partition 2 EFI system partition 3 Solaris/ZFS new disk is the same partitions?

INFO: issuing guest-agent 'fs-thaw' command ERROR: VM 106 qmp command 'backup' failed - got timeout guest agent on this machine is working?

I have this symptom on Intel SR1630GP server.

https://pve.proxmox.com/pve-docs/chapter-pvesm.html https://pve.proxmox.com/wiki/Storage

fdisk -l /dev/nvme0n1 disk has only one partition? host losts one of the WD Black NVME disk?

Look this https://forum.proxmox.com/threads/linux-aer-errors-on-nvme-seemingly-related-to-overheating.136565/#post-605782 try smart temperature disks and others parameters smartctl -a /dev/nvmeXnY or nvme smart-log /dev/nvmeXnY google bard says The error message "AER: aer_status: 0x00002000...

try list your log journacltl zfs-zed.service

try journalctl and sroll down, after time column is hostname, check how was it older name. my simple hostname and hosts

You do not have declared disk on bigData: storage. You changed this name to vm-100-disk-1?

Try booting the host from a more comprehensive Linux live CD, such as SystemRescueCD, where there will be more drivers available. Then, execute the 'lsblk' command there. If you can see those drives in the BIOS, it might be that your Linux distribution used for booting doesn't recognize them

Read this https://pve.proxmox.com/wiki/Resize_disks

Try show all snapshots and other zfs get type -r or list only snapshots zfs list -t snapshot

Try to enter to VM100 by console. Login and run ip a

run pvecm expected 1 on runing node if second node runs , cluster works again

It looks good. My root@pve:~# lsof -i -n COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1 root 35u IPv4 18584 0t0 TCP *:sunrpc (LISTEN) systemd 1 root 36u IPv4 18585 0t0 UDP *:sunrpc systemd 1 root 37u IPv6 18586...

Try lsof -i -n and search TCP *:8006 (LISTEN)