Search results

ChelsioUwire-3.11.0.0 was what I used. :)

Holy heck! I scoured the manual and couldn't find a single pointer about the debrules folder and how to use it instead!! It's installed now! THANK YOU!! :eek: PS: I remember glossing over a DEBIAN variable on this thread, but apparently I kept looking in the install.py not the Makefile...

Downloaded the drivers, unpacked the tar.gz, ran ./install.py. When it reached the part where it needed the "kernel source", I installed the pve-headers package for my current kernel, and it still seemed to fail to find the sources… :\ Building for kernel 5.0.15-1-pve...

Does the UnifiedWire even install on Proxmox 6? I can't seem to have it recognize the headers, and I wonder if it's just not ready for kernel 5.x… :\

Look into "AMD reset bug". I'm pretty sure it affects cards RX5* and up (inc. Vega).

I understand. But it's not "non predictable". It's in the ZFS configuration. Also, we could add that to the storage configuration options. FWIW, VM disks work perfectly fine in this model, only LXC fails… I'm not presuming to know more than you on this, obviously. If nothing else, a more clear...

Thanks for the reply. Is a fix for this in the works? Thank you.

Even when trying to add the ZFS volume mount point as a directory and writing the image file to it, as regular raw file, it fails with this error message: Formatting '/mnt/volData/images/120/vm-120-disk-1.raw', fmt=raw size=34359738368 mke2fs 1.43.4 (31-Jan-2017) Discarding device blocks...

This is good information, but doesn't help my problem at all :) What I did was probably faster than this too, for the number of VMs/containers I have ATM! ;)

Like I mentioned, I couldn't install the new disks without removing the original, hence moving them to a temporary drive I didn't plan to remove, and then adding the new disks, creating the mirror pool, and going from there... ;)

Yes, custom mount point (/mnt/<pool_name>, i.e. /mnt/volData). Does that make a difference? :o

Hey guys, I'm at a loss here. I recently moved from other virtualization solutions to Proxmox and have been pretty happy. Glad I made the switch… :) One thing that has got me stumped is this: a few days a go I got 2 enterprise-grade SSDs for VM storage. I was using a "consumer" SSD for that...

Same thing happened to me on a Supermicro X9DR7-LN4F, just FYI. 5.0 ISO worked fine, though updating didn’t update versino number (not sure if that’s expected thought). Cheers.