MowMdown

Mover tuning plugin is broken on Unraid 7.0, unless it’s been fixed recently? The bug prevents mover from working entirely. best to set the native unraid mover schedule to weekly or monthly.

Plex works just fine on bridge mode. No need for host mode. make sure you set the port to 32400 in both the plex remote access setting, checking the manual port box, and your routers firewall. the only time Tailscale is needed, is if you’re behind a CGNAT and don’t want to pay your ISP $5/month for a static IP.

Install the “File Activity” plugin. It will show you which files are being accessed which might give you some insight to what thing is waking up your drives.

I also forgot to tell you to hit the "Clear Stats" button at the bottom of the MAIN tab, this will zero out the reads/write numbers so you can see easier identify which disks have writes increasing from 0.

Type in to the terminal: lspci -vvvv You will get a long output, find the controller and look for the link state. For example of my JB585 Controller the "LnkSta: Speed 8GT/s, Width x2" is running in 2X mode. Note that some PCIe devices like GPUs will change their link speed depending on load, not sure things like SATA controllers or HBAs can do that but I know GPUs will switch to 1X mode when not under load. 04:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller (prog-if 01 [AHCI 1.0]) Subsystem: JMicron Technology Corp. Device 0000 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- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 61 IOMMU group: 12 Region 0: I/O ports at f200 [size=128] Region 1: I/O ports at f180 [size=128] Region 2: I/O ports at f100 [size=128] Region 3: I/O ports at f080 [size=128] Region 4: I/O ports at f000 [size=128] Region 5: Memory at fc810000 (32-bit, non-prefetchable) [size=8K] Expansion ROM at fc800000 [disabled] [size=64K] Capabilities: [80] 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: [90] MSI: Enable+ Count=8/8 Maskable- 64bit+ Address: 00000000fee00000 Data: 0000 Capabilities: [c0] Express (v2) Legacy Endpoint, IntMsgNum 0 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ TEE-IO- DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM not supported ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x2 <------------------------------------------------- This parameter right here TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-

Sorry, I meant the FileActivity plugin, which you already are using. Writes to your cache drive will not cause your parity drive to spin up, only writes to any of the array disks. You can also change the view on the dashboard to see which drive(s) have writes being performed on them by clicking the icon on the far right side. Start by stopping all dockers, spin down all drives in the array, see if any disks spin up. If so you have a device on your network reading/writing to the array. Start by finding out which device is accessing your NAS. Otherwise your might have a docker that could be logging to the array. The file activity plugin will tell you which files is being updated. It would be quite easy to figure out what is updating a specific file. Check each disk individually to make sure your cache only shares do not have data on the array disks. You dont have any VMs do you?

Download the Open Files plugin, start it and it will monitor which files get accessed. From there you’ll have to figure out what might be accessing the files listed.

I agree with @wgstarks on this one. I personally use "/mnt/user0/data" to purposefully bypass cache while still using the full array. Let me put it this way, my old 250GB 2.5" SATA SSD has over 400TB written to it and its still healthy.

I'd probably just chalk it up to the installer not wanting to be installed from a network share.

It's the drivers or firmware, nothing you can really do about.

enable mover logging and post the log after running mover. Settings > Scheduler > Mover Settings

I did not realize you were RUNNING unraid on the laptop itself. I assumed you were accessing the JetKVM webGUI from a laptop. This is 100% an issue with the laptop resolution and the JetKVM cannot handle it. I'd hit up the JetKVM discord or Github and raise the issue. They might even already be working on fixing non-standard resolutions.

/mnt/user consists of all disks in the array and the cache pools unless you've enabled exclusive shares. /mnt/user is a merged volume. If you place a file directly in /mnt/cache/media, you should be able to view it under /mnt/user/media. Same thing if you write a file to /mnt/user/media, it should also appear under /mnt/cache/media IF you have the primary storage set to your cache pool. NEVER move/copy files to/from /mnt/user to /mnt/disk or /mnt/cache you can end up with overwriting a file or duplicates Unraid does not care through which path the data was written to the cache, all that matters is how the share has it's mover action configured. Writing data to either /mnt/user or /mnt/cache will result in the data being put on the cache pool to be later moved by mover to the array if that's what you have and it sounds like you do. Somehow you ended up with duplicate files on both your array disks and the cache which results in mover not running because it doesn't move duplicate files. Honestly, with dozens of TB of data, you're better off bypassing the cache pool altogether and just write the data directly to the array. I would suggest enabling "Reconstruct Write" (Settings > Disks ) as this will greatly speed up data ingestion. Then when you're done, switch it back to Auto.

Stupid question but does it show up under the dropdown for the GPU Statistics plugin like so?

Change the laptop resolution to something standard like 1920x1080 temporarily. Edit: I will say that my JetKVM works if Im using my 3440x1440p 21:9 ultrawide (not the screenshot)

@Jltoro I mean you can always plug an actual monitor in and see if it behaves differently while you wait for your dummy plugs.

Minimum required is kernel 6.6. (I actually think it was like 6.2 or 6.4 but unraid never shipped with that specific kernel) The A310 does not require the Xe drivers as it will run off the i915 drivers. As long as you are running unraid 7 it should work. I believe to get the driver working on unraid 6.12.xx you need a modified kernel. I've personally been using my A310 to transcode to HEVC now that plex supports HEVC encoding.

Something that is not really discussed is that the CPU statistics on the unraid dashboard is deceiving. What I mean is that it includes IO-WAIT. IO-Wait is cycles not doing anything because it's waiting on the hard-drives to finish whatever they're doing before the CPU can access what it needs to resume whatever it was doing. (this explanation might not be exactly "technically" correct but it really doesn't matter, the point is the same) So when you see your CPU climbing to 100% utilization it might not actually be really at 100% utilization. It's more likely idle waiting on data/disks which gets represeted as CPU Load even though it's doing nothing. What I suspect is happening is you're filling up your cache drive if you have one and it being full is causing your system to lock up because your docker containers are running out of disk space to operate. (99% of the time this is the issue) To fix this you need either a larger cache or a dedicated disk just for dockers.

This thread might have some value to this discussion:

My guess is that it has something to do with your ASPEED BMC VGA adapter. I think you might need to blacklist it/ block unraid from seeing it as it might conflict with the ARC gpu. Another possible thing is you might need a dummy HDMI plug inserted into the intel GPU for your system to properly register it as a valid option. For shits 'n giggles, you can plug in a monitor to the Arc GPU and reboot, see if you can get the system to see it that way. If that's the case, either leave it plugged in or get a dummy HDMI plug which simulates a connected monitor.

You can always try something like this: https://www.amazon.com/Adapter-advanced-solution-Controller-Expansion/dp/B07JKH5VTL if you have any PCIe Slots available and have the physical space in your case for it.

Typically SATA ports 5 and 6 get disabled when you populate other PCIe lanes such as using an NVME drive in the M.2 slot(s). Thats why it's important to check the BIOS can see all the hardware connected. If they don't show up in the BIOS, the SATA ports 5-6 are disabled. However if you have an extra M.2 slot, pick up a ASMedia 1166 6-port M.2 to SATA controller (no need for a power hungry HBA for a few extra HDDs) These are the same chips that are part of motherboard chipsets. It's just like adding an extra one through PCIe.

Can you post your physical hardware specs? CPU, Motherboard, other PCIe hardware slotted, etc?

My A310 works just fine for me on 7.0.1

Awesome, ill check it out