tjb_altf4

Tried booting in GUI mode ?

FAAARRKKK I didn't see it at first, but now my eyes are on fire 🤣

Should be there for 6.8.3, otherwise there are prebuilt images for 6.8.3 on the support thread. With all that said, I've been on 6.9.0-rc2 for weeks and it is pretty solid, installing the DVB drivers is as easy as installing a plugin

You'll need to upgrade to the 6.9.0-rc2 to use that plugin, or you'll need to use the custom kernel builder for the current version (6.8.3). For what its worth, I use the GUI @ 4K with the driver installed

Bunked in with the in-laws for a few weeks while we are between houses. They have zero internet connectivity though the house other than wifi and I'm setup at the opposite end of the house, so cable run is not an option. After some head scratching and some trial and error, I came up with a suitable solution 1 AP is connected to unraid, the other AP is connected to my routers (WAN port) that is then connected to inlaws existing router (LAN port). This way I can get wireless connectivity to my unraid server, but also preserve both our existing networks. Other than some minor issues that come from the extra network overhead, its actually working quite well.

Try dropping machine type back from i440fx-5.1 to i440fx-5.0 I've had a couple windows installs that wouldn't boot on 5.1, but would on 5.0

Sounds like the igb driver issue that was present on those post 6.8.0 releases, although I thought it was resolved in 6.8.3 & 6.9

There's another report of others not being able to change threshold values, my existing threshold values are honoured (I set my NVME higher) so maybe there is an issue with the update mechanism from the multi pools update.

V3 prototype review is out for those interested

I probably wouldn't pick an address range typically used by APIPA either

Simply put, long cables from your server to the TV/Monitor you want to use, then it would be like setting up any other display. Depending on length, you can look at powered cables, or extenders that use network cables (these are a bit pricey). The ultimate version of this is using thunderbolt with a fibre cable and a dock, but that has traditionally been very expensive.

Anything that can handle streaming video should suffice, I often play games on my Android TV and Chromebook using Steam Link software. Some latency sensitive games aren't suitable such as shooters, but most others are fine. You could also potentially have extended runs of HDMI & USB and game natively on TV instead

The only way I can think it's possible is if the systems is suspended then resumed, forcing a hardware reset. Space invader leveraged something similar with a script to export vbios of the primary GPU a couple weeks ago.

Look a few posts up RE: Flaresolver

Could always try adding the GPU driver, this is easy on 6.9 onwards

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