tjb_altf4

Also if that length is OK, it might be more economical to get a direct attach copper (DAC) instead of modules and fiber. That's what I used (1m DAC) between my workstation and server with Mellanox X3 cards.

Sounds like the same issue Ive mentioned before a few times, but my issue occurs using deluge's scheduler

I've got the dual port version, works out of the box, just make sure to setup and enable in the network section of the Unraid GUI. However, if you need easy access to the Mellanox tools, such as for flashing the cards bios, there is also a plugin available from version 6.9.0 onwards (or with 6.8.3 with custom kernel). The plugin can be found in Community Applications.

As above, the Unassigned Devices plugin will do you what you want.

Have a similar issue, a few suggestions made by others in my bug report that are worth checking out.

I know you said you had good cooling, but do you have an active fan blowing across these hard drives? Do the HDDs have much of an air gap?

Hoping RC3 is around the corner with 5.10.8 kernel addressing the BTRFS regression. Also fingers crossed it fixes my USB woes with some of the other kernel fixes.

Give your network equipment a reboot, and make sure if you had setup DHCP reservation that you also updated the MAC address for the new mobo/nic.

I had this briefly this morning, I only saw the logs this afternoon. Coincided with shares not being reachable temporarily, which eventually resolved itself, but I've never seen this in logs before.

Same

Yep, I've had this setup for a few years now, works easily with both API and black hole methods.

Site performance seems to be back to normal BTW

Under Account Settings for those looking Also enjoying the Fluid width setting! (under the customizer toggle)

For number 2, you remove the LSIO plugin and install the Nvidia-Driver plugin. The Nvidia-Driver installs the driver and the Nvidia docker framework for GPU acceleration in dockers... and it does it in a way that you don't need a custom kernel like the old plugin. I haven't gotten around to the realignment, but you can choose XFS or BTRFS for a single disk, but BTRFS is still the only choice for a pool of disks.

Not sure if typical for all setups, but certainly for me even with no dockers running and no processes utilising a GPU, it would hard lock the server if I tried to start a VM with the GPU passed (with drivers loaded). Binding GPU to VFIO driver avoided this situation. With 1 GPU bound to VFIO it can be used for VMs... Another GPU remains for host(GUI) and docker.

A little slower, but it's clearly going through some sort of migration at the moment, given the theme has changed etc. Give it a day IMO

The new position alignments for SSDs would have been beneficial, but there should be a good chunk of performance improving when we go to a newer kernel as the current kernel has a BTRFS performance regression bug.

Try resetting the minimum free space (set to 0KB), that is the only difference I can see to my own config that works as you would expect.

Set per pool now by the look of it, if you go Main > Cache (or whatever the pool name is), the Minimum free space option is there.

Can you screenshot your (Photography) share settings

You probably created it yourself, if you omit a name it generates one for you https://github.com/moby/moby/blob/master/pkg/namesgenerator/names-generator.go

I tested it quite a bit before posting to double check it worked as intended. Only thing I can think you should try is creating the symlink on disk 1, to ensure its the first disk it tries to write to. Mine was created on disk2, which was the first disk that participated in the share (for writing)

A couple things to try: make sure your user access is setup correctly for the new share, i.e. can you create a folder in the other parts of the share try deleting the symlink and recreating See if that fixes things

The keystrokes you need to do are hold Ctrl, press X, release Ctrl, press S Holding Ctrl for X+S is a symlink edit shortcut, hence the error. You should also remove the Processing folder on disk6 You will get a symlink already exists error, as it the content will already be present. Remember the cache folder you created will exist in the user share as unraid still looks at the cache, its only the mover and initial file creation for the share that is ignoring that folder. In MC, just delete the symlink (not the real folder!). You can then do a move to the array if needed, or simply change you cache preferences and let mover take care of it

Dockers will be started up sequentially (but effectively at the same time), in the order on the docker page. On the docker page, in advanced view, you can specify a start delay between specific dockers being started if needed.