Search results

Here is what I have done thank to the ZFS community (mailing liste) $ zpool clear backuppool $ zpool scrub -w backuppool; zpool scrub -w backuppool $ zpool status -v backuppool pool: backuppool state: ONLINE scan: scrub repaired 0B in 01:00:27 with 0 errors on Wed Apr 12 16:18:53 2023 config...

Is this backuppool/backups:<0x43> the same as if I do root@xxx:/# zdb -d backuppool/backups 43 Dataset backuppool/backups [ZPL], ID 899, cr_txg 2827, 1.42T, 237 objects Object lvl iblk dblk dsize dnsize lsize %full type 43 1 128K 1K 4K 512 1K 100.00...

1585 1 128K 512 0 512 512 100.00 ZFS plain file 1586 1 128K 512 0 512 512 100.00 ZFS plain file 1587 1 128K 512 0 512 512 100.00 ZFS plain file 1588 1 128K 1K 4K 512 1K 100.00 ZFS plain...

If I do zdb backuppool/backups , here is what I get Dataset backuppool/backups [ZPL], ID 899, cr_txg 2827, 1.42T, 237 objects Object lvl iblk dblk dsize dnsize lsize %full type 0 6 128K 16K 288K 512 1.33M 8.71 DMU dnode -1 1 128K 512...

I don't know if it's a dataset or a zvolume. In Datacenter/Storage, "backups" is a Directory type and "backuppool" is a ZFS type. I think backuppool is indeed a zfs pool. However, I don't know if backups is a dataset or a zvolume, only that iti s a Directory type.

I got an email from my proxmox saying there was an error during backup. I run the command zpool status -x -v and here is the result pool: backuppool state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action...

I guess it was that then :) Thanks!

Thank you for your explanation. You were right, the problem was that everything needed to be written on one single line. I misunderstood the sentence "needs to be placed as one line in /etc/kernel/cmdline". Everything is working back as expected. I just wonder why it has stopped... Is it...

in /etc/kernel/cmdline, there is and in /etc/default/grub, there is and I did update-grub proxmox-boot-tool refresh in /etc/modules, there is and I did update-initramfs -u -k all reboot nothing changed...

Hello, I used to have a graphical card working on passthrough a VM windows. Unfortunatly, after some updates of proxmox (kernel...), I get now the following error when trying to start the VM : TASK ERROR: cannot prepare PCI pass-through, IOMMU not present I tried to follow again this page...

and the problem would be more linked to this issue apparently : https://forum.proxmox.com/threads/vm-shutdown-kvm-entry-failed-hardware-error-0x80000021.109410/

Thank you @eugenevdm for your help. I'll look in this new direction.

It could be because the QEMU Guest Agent was not running automatically on the VM. I changed that in the Services of windows.

If you find what cause your problem I'd like to know as I guess I have a similar issue : https://forum.proxmox.com/threads/vm-windows-shutdown-by-itself.115598/

I found someone who seem to have a similar issue : https://forum.proxmox.com/threads/qmeventd-shutdown-vm.92279

Hello, Two days ago, I found a VM windows off without reason. I first thought it had switch off itself after some obscure updates but apparently no. Then I look at Proxmox's logs and I found the following line I can't understand : I guess, it is the lines and that confirm that it is...

Well, the current situation is for testing this gpu passthrough system. The idea is of course to add CTs on the side of this VM. Here is what we want to have at the end : - 1 VM with Windows and GPU Pass through : this VM is for us (we would connect through RDP) to be able to use some specific...

Thank you for your quick answer and for trying to help me. The computer has 32 Go of Memory. The single VM (with GPU Passthrough, running Windows 11) has 20 Go. No other VM nor CT are currently running. However, Proxmox display a 95% of RAM usage. Proxmox use 8.9 Go when all VM are stopped...

Sorry to come back to you @leesteken but if I believe I understood the problem, I could not find any solution... I ended up starting only one single VM with 20 Go of RAM over 32 Go (to be sure Proxmox would not come in conflict with the VM) but still the VM might stop time to time suddenly (I...

I'm not sure to understand all the fine technical details you wrote but I guess I got the overall meaning and I thank you for this explanation.