MystX

For future googlers, I was able to get both GPUs + coral working by disabling CSM and secure boot in the bios and switching over unraid to boot via UEFI (rename "EFI-" folder in /boot to "EFI").

There aren't any more that aren't covered by GPUs. And I haven't moved the slot the coral card is in. I'll pull out the 2nd GPU and see what happens. It did cross my mind that I might have run out of PCIe lanes, but as I understand it the bottom slot that the coral card is in is run through the chipset? (If you're interested, I went from having a 2070Super + GTX750 + coral to 3080 + 2070Super + coral. All on a x570 mobo and Ryzen 5900X). EDIT: Removing the 2070 worked, and /dev/apex_0 shows up. Not sure why that is..

There are no apex* devices in /dev =(

Having trouble with the coral plugin here. The pci coral card shows up in system devices / lspci, but the coral driver plugin says no devices detected. And the apex driver is loaded. This was previously working and has stopped working after installing a new GPU (without touching the coral card at all). I've tried uninstalling the plugin, rebooting, then reinstalling and rebooting again. Diagnostics are attached from after this process. Any ideas? lsmod | grep apex apex 16384 0 gasket 98304 1 apex lspci -vv 04:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (prog-if ff) Subsystem: Global Unichip Corp. Coral Edge TPU Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 37 IOMMU group: 22 Region 0: Memory at <ignored> (64-bit, prefetchable) Region 2: Memory at <ignored> (64-bit, prefetchable) Capabilities: [80] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (ok), Width x1 (ok) TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+ 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, AtomicOpsCtl: ReqEn- LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [d0] MSI-X: Enable- Count=128 Masked- Vector table: BAR=2 offset=00046800 PBA: BAR=2 offset=00046068 Capabilities: [e0] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [f8] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?> Capabilities: [108 v1] Latency Tolerance Reporting Max snoop latency: 1048576ns Max no snoop latency: 1048576ns Capabilities: [110 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=10us PortTPowerOnTime=10us L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- T_CommonMode=0us LTR1.2_Threshold=32768ns L1SubCtl2: T_PwrOn=10us Capabilities: [200 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Kernel modules: apex krieger-diagnostics-20220827-0053.zip

OK it seems like I've got things mostly sorted. For internet prosperity what I did was follow the guide linked above to restore the cache drive to another drive. Formatted the cache drive, copied everything back over. Unfortunately my libvirt and docker images were still broken. I restored both from a backup. Libvirt was ok after the backup restore but docker was not. Had to delete my docker image, recreate it, then re-install all the dockers from community applications 'previous apps' menu. Thank Johnnie

Oh sorry, I read that that was step 2 AFTER you mounted. I will try that and report back after I clear some space off a disk lol

Hi guys, I ran pm-suspend on my unraid server to try to fix the header type 127 VM bug. I woke the server up and it hadn't worked. So I rebooted it. Now I get the following errors on the console when the cache drive ties to mount: Apr 24 19:47:17 Krieger emhttpd: shcmd (73): mount -t btrfs -o noatime,nodiratime -U 654c77cd-a2b1-470a-bebe-55a1287689f0 /mnt/cache Apr 24 19:47:17 Krieger kernel: BTRFS info (device dm-2): disk space caching is enabled Apr 24 19:47:17 Krieger kernel: BTRFS info (device dm-2): has skinny extents Apr 24 19:47:17 Krieger kernel: BTRFS error (device dm-2): bad tree block start, want 483444981760 have 8354356187505211028 Apr 24 19:47:17 Krieger kernel: BTRFS error (device dm-2): failed to read block groups: -5 Apr 24 19:47:17 Krieger kernel: BTRFS error (device dm-2): open_ctree failed Apr 24 19:47:17 Krieger root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/mapper/nvme0n1p1, missing codepage or helper program, or other error. Apr 24 19:47:17 Krieger emhttpd: shcmd (73): exit status: 32 Apr 24 19:47:17 Krieger emhttpd: /mnt/cache mount error: No file system Apr 24 19:47:17 Krieger emhttpd: shcmd (74): umount /mnt/cache Apr 24 19:47:17 Krieger root: umount: /mnt/cache: not mounted. I have tried to mount the drive as here: But no matter what I try I get "mount: /x: wrong fs type, bad option, bad superblock on /dev/mapper/nvme0n1p1, missing codepage or helper program, or other error." ^the cache is encrypted thats why the device is in /mapper Any other options or is my cache dead? Thanks =\ Diagnostics attached. krieger-diagnostics-20200424-2016.zip

I've now tried dumping my GPUs rom and supplying that to the VM. No success with that either.

Hi guys, This is an ongoing problem with my Ryzen unraid 6.8 box (same problem on 6.7). After some time with the VM idle, it BSODs with PAGE_FAULT_IN_NONPAGED_AREA. Looking at the minidumps the crash is apparently caused by "ntoskrnl.exe" which I assume is the windows kernel. The VM has a RX480 AMD graphics card passed through, and is a Q35 OVMF machine. Things I've tried: Updating all virtIO drivers, mobo BIOS, gfx card drivers, windows updates. Different Q35 versions. C-states off in bios. Memtest86+ came back with 0 errors after 6 passes. Creating a whole new VM and installing windows + gfx drivers. Same issue with that VM. I've attached my diagnostics and some minidump files to look at. If anyone has any ideas that would be greatly appreciated 😃 010120-6781-01.dmp 010520-6968-01.dmp 010520-7046-01.dmp krieger-diagnostics-20200105-1015.zip

I think because the server crashed and I had to restart, the operation wasn't in history. What I ended up doing was running: rsync -n -ai /mnt/destinationDisk /mnt/sourceDisk To see if there were any files in the destination disk that weren't in the source disk (destination and source from the point of view of my unbalance move). I.e. to see if unbalance had completed any operations and deleted. It hadn't, so I just formatted the destination disk and started again. But thanks for that info for next time =)

Hi guys, I've just had a move operation fail half way through (the server crashed hard). Some files have been transferred to the destination (about 1.5TB worth). But it seems like most, if not all, of the files remain on the source disk. So unbalance tells me there is not enough space at the destination if I try to begin the transfer again. Is there any way I can resume the transfer that failed? If not, can I be sure that all of the files are still on the source disk? I know that MOVE copies first then deletes, but I can't find info anywhere on whether it does that per folder, or it waits till everything is copied and then starts deleting. The easiest thing might be to reformat the destination disk and start again, but I don't want to do that till I'm sure obviously. Thanks

For anyone in the future, it turned out I had the MSI fix enabled on my graphics card, but not the audio device on my graphics card (i'm using HDMI audio). Enabled it on both and everything working as normal =)

Yeah mine is already set to DVD quality and it has not helped =( and I cant move away from the HDMI sound card. I've attached my diagnostics for anyone looking at this. krieger-diagnostics-20170711-0749.zip

@StuartMacfarlane @unraidrocks Did anyone find a solution to this? I am having the exact same issue with a RX480. I have tried a brand new win10 VM and all of the other suggestions here - with no results.

For someone looking at this in the future, this seems to be a HDCP problem. Decided to plug this straight into a TV since it was going through a receiver. Directly connected to the TV the VM boots right up with only HDMI plugged in. When connected to my receiver, it doesn't boot at all =( The receiver does support an older version of HDCP, so I find it weird that the card refuses to start up when connected. Once the VM is actually started it will use the receiver with no problem.