Search results

Seems you are using mdadm software raid, that is not supported (/dev/md2) (I don't use it, just a guess). You should run pveperf with all VM NOT working, with vm working is pointless. Old server is in usual storage config (/dev/mapper/pve-data so Thin LVM), new server is... I've no idea! Try to...

When I wrote "maybe an hardware problem" was not about RAM or other stuff, I asked you to plug a lan cable connected to something working, so the nick had at least the signal. I had a server (not proxmox) that was unable to boot until the nick was connected. Try this please. Second, have you...

[cut] In my experience, booting with no network connected is possible without problems, maybe is some hw problem instead? Try to connect the cable to another PC or a switch just to have the hardware sensing the connection, maybe it can solve. Of course you have a single server here, with local...

I'm pretty sure is the GPU temperature, previous suggestion is wrong, should parse for "k10temp-pci-00c3" and not "nouveau-pci-0500"

Here "snapshot" is the MODE, not the storage. This means that it does not shutdown the VM before doing the backup, but it "freezes" it for the duration of the backup. It has nothing to do with the snapshots of the storage you can take, also remember that the backup does not have any of those...

Isn't the "k10temp-pci-00c3" your CPU temperature, as stated in the forum message you linked?

Hi, my home proxmox "server" is headless and does not have any IPMI console. I need to boot it with previous kernel, but if I try to remove the last one as suggested in this thread https://forum.proxmox.com/threads/changing-selected-kernel-for-boot-systemd-boot-on-headless-pve-host.59593/ it...

I think you can try to remove all proxmox packages and reinstall, BUT don't run the iso installer, that will delete all disk content. In any case you MUST HAVE a backup on external driver, if you don't there is a not trivial procedure depending on the type of storage you have (normal recent >...

Are you sure is not an hardware failure? Disk? Ram (try memtest)? Is a real server with IPMI and hardware logs to have a look at? Seems not a boot (grub...) issue to me, but a more severe (HW) one. Or try in chroot to install and updated kernel / reinstall the one you are using, maybe it's...

I've not followed this thread with attention, but there is the procedure described (but somewhat "hidden") in the wiki, have a look at: https://pve.proxmox.com/wiki/ZFS_on_Linux#_bootloader in the part with the title "Changing a failed bootable device when using systemd-boot" should be all that...

OP says "very high IO Delay", so I think that SLOG will improve a lot in this situation. In any case without SLOG performances in general are really worse than with it.

no ZIL/SLOG with datacenter grade (possible with powerloss data protection) SSD dedicated device? You do need it to have sync writes be much faster. https://pve.proxmox.com/wiki/ZFS_on_Linux "Add cache and log to an existing pool" If you can have a (datacenter grade) NVMe device instead of sata...

Do you mind share how you do that?

Also have a look at storage replication https://pve.proxmox.com/wiki/Storage_Replication

You seem to be already restoring from local machine, you have copied the backup file in the "target" Proxmox under, probably, /root dir, right? I see that the qmrestore seems to write some temporary file in /var/tmp/ (/var/tmp/vzdumptmp13242), wondering if it has enough space in it (that scares...

Frankly I'm shocked about this attitude. We are in an official Proxmox forum, it's GPL code so everyone can modify it BUT it's at least, let's say, "unpolite" to post here how remove a nag that simply reminder that the development costs and you can contribute at least with a basic, cheap...

never used, but seems SuperMicro has some with 1 DWPD. Would love to know the prices, since RW performances seems very low, at least for the "not top" models. Probably there are a lot of tuning to do on Proxmox, since is a "normal" GNU/Linux OS (and, for instances, swaps even if you have free...

select it, edit it (AFAIR button near the "add" button you use if you want to add a new disk) and assign controller type (i.e. virtioscsi) and so on. In VM Options check boot priority.

https://forum.proxmox.com/threads/restore-error.16027/ maybe you are restoring in a storage that has not enough space for the vm?

Fastest option is to edit 103.conf and add (and adapt) the line you find in 102.conf that are related to that disk (so 103 VM will point to 102 disk). The problem is that if you then delete VM 102 it will delete the disk too... If "DATA" is a file system, you could simply move and rename the...