Search results

You can boot your computer from some "live CD" and issue: grep -E 'svm|vmx' /proc/cpuinfo or for better readability: grep --color=auto -E 'svm|vmx' /proc/cpuinfo If the output contains svm (for AMD) or vmx (for Intel) then the CPU supports virtualization. Source...

@katti Depending on your requirements on a how long the services can be unavailable and on how much fresh data can be lost, a workaround could be frequent backups to PBS. And restoring to the other cluster when needed). Thanks to "dirty bitmaps" (...

I don't know if this is a right track, but doesn't hurt trying: dpkg --verify debsums -c If the result gives any hint, try to investigate it and possibly reinstall doubtful packages.

Welcome, @ssfbc2000 Have you checked https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_pci_passthrough and https://forum.proxmox.com/search/9280634/?q=hba+truenas+passthrough&o=date or a similar search?

Hi, @proxjox If the server with this exact configuration worked OK before the failure, then something must have changed, maybe because of the failure or adding or removing or changing the place of some device. Or newer kernel... I mean that enp3s0 is not present in ip a result. Maybe it got...

Before recreating the VM, you can try what I mentioned. As SELinux insists on that missing policy file, try booting with SElinux disabled temporarily (for that one boot). To do that, while booting, add to the kernel command line: selinux=0 Let us know, if you succeed or not.

In these particular two entries probably not. The senders are different. In the first entry it is: and in the second: Unless the sending software changes the sender's email address at every retry, these were different messages. Anyway, the connecting clients were the same. Looks like for...

The OS will see hardware RAID0 as a single big "disk", so no, it's not a proper way for ZFS.

Hi, @olluz It isn't very clear from the excerpts as you obfuscated them, but are you sure these two connections relate to the same triplet "client, sender, recipient"? If the client's IP address was the same, it may mean that the first time the DNS lookup failed due to a temporary problem...

Hi, @sidoni I believe that the first warning can be explained in https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_system_settings - especially in the sections "Machine Version" up to "Update to a Newer Machine Version". As for the second warning - you probably have a snapshot dated back to...

I'm not sure about the wording. But probably yes. You must attach it to the (virtual) optical drive and change the boot options so that the VM boots from it. I haven't met the error message you quoted, but as the VM wants to execute a fs check, do it and see what happens next. If the VM boots...

Hi, @jlgarnier You probably may boot the VM from some rescue CD image (e.g. Systemrescue). It doesn't require the password of the VM. And then without mounting the original filesystem you can fsck it.

Hi, @Ozymandias42 Would you share some reliable links?

The space between " and v is redundant. But it doesn't hurt anyway, as it turns out :cool:

Welcome, @eh_pmox That is, which exceptions? :)

@BigBadBlack , as space is your priority, not performance, then RAID6. RAID10: 5.4 TB RAID6: 7.2 TB And RAID6 has bigger fault tolerance: 2-drive failure in comparison with "at least 1-drive failure". You can calculate capacity at https://www.raid-calculator.com/ Mind that RAID6 has poorer...

Welcome, @ilian_nilsson In the meantime you can try installing Debian there - as a test to know if this is Proxmox-related or a more general problem.

1) How many disks? 2) How much space do you need?

I admit I'm not very experienced with Proxmox' networking, so at the moment I'm just comparing your config with the similar one at https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_network_bond - section "Example: Use a bond as the bridge port" I can see you have auto eno8303...

The result of cat /etc/network/interfaces would give more details :) Of course not as a screenshot, but as text in the CODE tags (using this </> button above).