Search results

Ok, I tried installing a different ESXi version (7.0.3) and this time it succeeded (on a SATA vdisk). So the issue must be ESXi v8.0/PVE v8.0 specific. Thanks

You mean the installer was able to detect the disk and then install ESXi normally ?

Tried all SCSI controller options available in PVE, but unfortunately none of them seem to be detected by ESXi installer (only IDE and SATA controllers are being setected).

Trying to install ESXi v8.0 as a nested VM on a PVE 8.0 host, but the installer fails at the installation phase with the following error: "Disk device does not support OSDATA" (see attached screenshots) According to VMware [1] the above message is shown when the installer detects the local...

Just a thought, have you tried creating a new LV with a size of 100% remaining free space, then zero out the LV by using something like 'dd if=/dev/zero of=/dev/vg/lv bs=4M' ? Finally destroy the temp LV.

I second this, I'm seeing exactly the same behaviour after applying the latest updates on a 5 node cluster. I'm using openvswitch as well.

Moreover some links to Ceph docs which seem to relate to the issues you are seeing ... https://docs.ceph.com/en/latest/cephfs/troubleshooting/ https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-osd/?highlight=backfill#debugging-slow-requests...

Just for clarification, creating an UEFI partition does not necessarily mean that you must enable UEFI boot on your current system, either if it supports it or not. You could simply create UEFI partition(s) of ~512M in size and keep them for future use. Your current system seem to have already 2...

If you decide to re-create the partitions on the original drive, then I would go for the proxmox method instead of debian, since it looks like your system and GRUB is being handled by PVE instead of the vanilla Debian. This would save you from future similar issues as you are facing now and make...

Question 1: Yes, as long as you do not 'zpool upgrade' you are safe. Long story short, if your /boot partition is located in same pool (usually rpool) as rest of the OS, then upgrading the pool would render the system unbootable due to the fact that GRUB does not support all zfs features. In...

There's an open bug in bugzilla, please post your info in there to help narrow down this issue ... Thanks

Don't think that the reboot will make any difference, I have already tried rebooting all nodes with no luck. This most likely looks like a bug, so let's see if an updated package fix will be released in one of the upcoming days... Proxmox staff has to verify this first though..

I'm having the same problem after upgrading a 3 node cluster to the latest package versions. Multicast communication works fine, but pvesr.service is unable to start because of "error with cfs lock 'file-replication_cfg': got lock request timeout". As a workaround, I have removed the content of...

It's about pve-zsync, I'm not receiving e-mails from job scheduled via pvesr [GUI replication]. In a more general context, is it possible to disable crontab e-mail alerts completely ?

hello I have configured e-mail alerts on the pve hosts and they are successfully being sent to the root account (which then forwards to my real e-mail account). What I’m trying to figure out is how to disable e-mail alerts sent by cron. If that’s not possible, can I somehow disable only zfs...

>> I'll have to study to understand the answer by @acidrop . Sorry, I misunderstood your question. I thought that you were about to partition the SSDs in 3 slices (1 for L2ARC, 1 for SLOG and the 3rd for generic VM use). That 3rd partition in this case, may be used as an additional storage on...

>> What proxmox storage would that be? That would be an additional "directory" type pve storage. You need to partition, format and set a mount point for the ssd, then add it via GUI..

>> A few days ago, I installed proxmox in a server HP Proliant DL120,but it doesn't run. Well, that sounds pretty generic. What's the actual error message ? Did you manage to install PVE successfully ? You could use the Debian installation method as a workaround if everything else fails...

>>Running VMS with automatic replication. You mean ZFS sync replication? How many PVE nodes, two (2) ? >> Whats the easiest way to launch those as machines? Well, if the VMs were running on the Primary (now offline) node, then first thing to do is to move the VM conf files to the correct...

This should be a good start ... https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#VMware_to_Proxmox_VE_.28KVM.29