Recent content by Asano

Unfortunately I don't have spare hardware at my hand to try. But judging from this thread it should be as easy as setting up a Proxmox cluster and adding a Synology iSCSI storage like so: iscsi: Synology-iSCSI portal 10.0.0.100 target...

@Arm1nas you probably could debug quite easily to see if your problems also come from sound/USB emulation like it was for me: remove the hotplug: usb and audio0: device=ich9-intel-hda,driver=none from your config, reboot and connect with windows RDP. Now do something which normally lags, or even...

That sounds unbearable :d But I remember this was pretty much the experience I also had with my first try and the RTX 2080 Ti system. And though it seemed like CPU related it just disappeared the moment I stopped USB and sound emulation and passed the controller to the VM. I also remember that...

Some hints from me also I'll try to keep it short... To the "why" (@BobhWasatch): Because windows is a moloch with which you don't want to share anything more serious you do personally (be it work or private) but you need it for gaming Because it is fun Because! Over the past decades I found...

Same Problem and I'm also using Synology iSCSI so probably the cause is exactly the same. However, I make use of Synology IPv6 in my LAN so I cannot simply disable it. Is there a way to work around this (or even solve this) on the Proxmox side? @Moayad or anybody else from the Proxmox stuff do...

In a Proxmox cluster I'm seeing the following error more often when I try to rollback. ``` zfs error: Insecure dependency in exec while running with -T switch at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 176. ``` The cluster is currently a v 8.0.4 but I did see the error with v 7...

Not really unfortunately. We migrated to a Proxmox Backup server instead. And there we don't see any of those problems with the exact same cluster (also the backup server's storage is also kind of slow HDDs ).

On a Windows Server 2019 VM on a Proxmox host (7.1-11 PVE, 5.13.19-6-pve kernel) I'm having a strange problem: The upload to a new Synology DS1621+ is horribly slow (1-3 MB/s). The fun part is, as soon as I start another upload to anything else in the network both uploads become fast. The...

@oguz anbei soweit ich es posten kann. "xxxxx" ist die "neue" die gerade das Problem hatte, "yyyy" die alte. Das selbe Spiel hatte ich vor ein paar Monaten schon mal, da hatte ich aber dann die damals neue gekündigt und stattdessen die alte upgegradet... pveversion -v proxmox-ve: 7.0-2 (running...

Stand heute ist das scheinbar immernoch reproduzierbar: schließe ich eine neue Hetzner Storagebox an ein Cluster bei Hetzner an, so tritt nach wenigen Stunden oben beschriebenes Fehlerbild ein (auf allen Nodes!). umount /mnt/pve/new-storage-box-mount-name "behebt" das Problem; danach scheint...

@eminempt I'm currently not sure if you already had the passthrough working once with Proxmox 6 or if you are trying on a fresh install. Generally speaking I could imagine getting a passthrough to work with one GPU only could be really tricky. For the primary GPU I always needed a ROM file to...

Just stumbled across this thread and my problem described here ( https://forum.proxmox.com/threads/backup-zstd-stdout-input-output-error.94342/post-415389 ) is most likely the same but unfortunately also still unsolved.

So now just few days (maybe coincidence) after I replaced the server with the frequent zstd: /*stdout*\: Input/output error I just saw the error the first time on an other older server in the cluster. So currently the new server (which has quite heavy load and also inherited most from the former...

@dylanw just wanted to say that I had the exact same case as OP but without doing anything special. So basically I shut down the node to remove for good and executed `pvecm delnode node4` on a remaining node. The cluster is much smaller than OPs (3 nodes after the removal) but the error and...

I had similar issues with my passthrough setup (but I only used Proxmox 5/6 as you may know from my other thread ). In the end I solved it with the correct ROM file (or at least I'm very sure that this was what actually did it). However getting the ROM file was quite tricky and files from...