tech3475

Since it's been a few years, does the advice not to use Sandisk still stand or have things improved? Thinking of picking these up to have some spare drives on hand: https://www.argos.co.uk/product/9161627

I've seen this before on USB drives, you can just ignore that guff and wipe the drive.

I finally got round to looking at this again. This time I tried uninstalling, renaming the remaining config folder from the flash drive, updating unraid and reinstalling the plugin. So far things seem to be working, going off the above, I'll note the parameters is blank now.

Tried updating to 7.2.2, same issues are occuring. Don't have access to the updated diag right now but it's the same errors in the logs from when I looked for 7.1.4. I am running the latest versions of BIOS and iLO.

Is anyone else having issues on 7.2.2? When I upgraded from 7.0.1 attempting to delete files/folders created prior to the upgrade caused SMBd panics and fails to delete the file whilst I could delete newer files just file. I downgraded back to 7.0.1 and it now works. Note: I have run docker safe new permissions and run a file system check on all drives. hp-svr-diagnostics-20251210-1240.zip

Update: Did some more experimenting, seems to be Recycle Bin plugin is causing the problem or at least when I remove it the issue stops. For now I've re-downgraded since I do use that. Do you still wish for me to still submit a general bug report or just put a post in the Recycle Bin plugin topic? On a side note, on a different system to the above, this issue also still occurs after trying the same server on 7.2.2: https://forums.unraid.net/topic/192775-vm-pcie-passthrough-error-on-714/#comment-1573000 I have an updated diag but tomorrow as of posting is the earliest I can get it.

Anyone else have issues with SMB on this version? Upgraded from 7.0.1 to this and I found trying to delete older files (even after running docker safe newer permissions) just resulted in SMBd PANIC error messages and on my mac just mounting caused the log to fill up. Downgrading back to 7.0.1 fixed the issue. If it isn't a known issue I'll make a post with the diag dump when I'm back home.

Anyone who had PCIe pass through issues on >7.0.1 (RMRR regression?) able to do so on 7.2.0?

Does this fix the regression for PCI-E passthrough in certain cases? Here's a link to my problem on 7.1.4:

I have a HP Gen 8 Microserver with a PCIe quad NIC passed through to a pfSense VM. On 7.0.1 it works fine, but when I tried to upgrade it to 7.1.4 the VM fails to start with the following error: Execution error internal error: QEMU unexpectedly closed the monitor (vm='pfSense'): 2025-08-13T16:43:44.250018Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.3","addr":"0x0"}: vfio 0000:07:00.0: failed to setup container for group 1: Failed to set group container: Invalid argument I tried creating a new VM but the problem still exists with only a downgrade back to 7.0.1 fixing it and VFIO bind is enabled for all the NICs. The attached diag was made before the downgrade. Any advice or is this a bug? Please note that the system is at my parents house, so it may take a few days before I can try anything. Thank you HP-Gen8-unraid-diagnostics-20250813-1740.zip

Thanks, I just thought I'd ask here first in case it was a known issue with a quick fix.

Anyone else having issues with PCIe passthrough to a VM? At my parents I have a HP Gen 8 Mincroserver with an Intel Xeon E3-1230 V2 running 7.0.1 and I'm able to passthrough a PCIe network card just fine. However, when I upgraded to 7.1.4 I started getting this error: 2025-08-02 17:16:36.612+0000: 12559: error : qemuProcessReportLogError:1953 : internal error: QEMU unexpectedly closed the monitor (vm='pfSense'): 2025-08-02T17:16:36.605906Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.3","addr":"0x0"}: vfio 0000:07:00.0: failed to setup container for group 1: Failed to set group container: Invalid argument I tried recreating the VM from scratch but it still has the same error. The card is a quad Intel 82580 and all four are vfio bound. Unless I missed it, I couldn't see anything in the changelogs.

Currently I'm considering the 12600K and a Z790 motherboard, due to the unlocked speed and the better iGPU for transcoding. I'm thinking of then disabling things like turbo boost and maybe undervolting it. Would this be viable?

I'm looking to make a new build which is intended to replace a thin client I'm currently using as my firewall/backup server (Wyse 5070 extended w/ Intel J5005). The main purpose of this system will be: 1) Running pfSense using PCI-E passthrough to a dual NIC 1Gbe card (although the latter may change if better ISPs come to my area) 2) Backup storage for my main server 3) CCTV DVR (5 cameras, considering Agent DVR Docker) 4) (Optional) Linux install for RDP 5) (Optional) backup Plex server I've been mainly using Ryzen the last few years, but am I correct in thinking something like an i3 ok for my needs, particularly due to Quicksync? Or would I be better off just getting an i5 or something and underclocking it? Thanks for any advice

The fan I use on my Adaptec ASR-71605 has failed, since I was considering replacing it anyway I'm thinking of looking at an LSI 16i HBA. Some questions though: 1) Do these things still get relatively hot and subsequently need additional cooling similar to the adaptec for use in a regular case? For comparison, the Adaptec is currently 85c according to Storman with just the case fans (not ideal I know). 2) Have there been any unraid issues with these similar to the kernel driver issue for the adaptec a few versions ago? 3) Are there any 'common' issues with buying these second hand? I.e. are fakes common similar to GPUs. I've been looking on ebay and Aliexpress and the former has cards from my country for around £80 w/o cables (not an issue) but both seem to have the 9300 16i with cables for around £80 as well.