Search results

  1. M

    Steps to migrate Proxmox to a new (larger) M.2 disk

    The pool configuration is not saved in any file (at least I don't think so) but is saved on each vdev (disk, partition) used in the pool. Yes, you can import a pool created on another system. From what you showed, some of the disks of your virtual machines are saved on the LVM system disk. You...
  2. M

    Steps to migrate Proxmox to a new (larger) M.2 disk

    your machine configuration is on path /etc/pve/nodes/you_node_name/qemu-server/your_machine_VMID.conf or qm config <VMID> If you backup your machine from proxmox backup, backup has machine configuration. Migration proxmox from 1TB to 2TB is posible and simple if you have zfs on system disk...
  3. M

    [bug?] For setups without "rpool" named ZFS pools destroying containers fails.

    on your storage.cfg is entry rpool if you do not have this storage remove on GUI or edit storage.cfg and try remove container.
  4. M

    [SOLVED] Unexplained Storage Growth in Windows VM on ZFS.

    "I'm wondering if you have the VSS (Volume Shadow Copy Service) function enabled, and it might simply be taking up space on your disk. Check the Shadow Copies settings on your volumes using the command line: vssadmin list shadows Another feature that could be occupying space, though it may not...
  5. M

    The current guest configuration does not support taking new snapshots

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

    proxmox-boot-tool status shows one entry in raid1 system

    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...
  7. M

    proxmox-boot-tool status shows one entry in raid1 system

    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...
  8. M

    proxmox-boot-tool status shows one entry in raid1 system

    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?
  9. M

    Backup of VM fails

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

    host console has strange background colors

    I have this symptom on Intel SR1630GP server.
  11. M

    Proxmox - install second ssd

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

    Logical Volume not found after reboot.

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

    [SOLVED] ZFS device fault for pool emails

    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...
  14. M

    [SOLVED] ZFS device fault for pool emails

    try list your log journacltl zfs-zed.service
  15. M

    i edited the /etc/hostname and /etc/hosts files and everything crashed

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

    Using a .raw file as the hard disk for a VM.

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

    NO HARD DISK FOUND

    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
  18. M

    Confusion over media storage / partitions

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