BRiT

Nope. Moving files on the cache pool does not require reading and writing the entire file, it is couple of simple entry changes in the directory tree. If you use something like /mnt/cache/downloads to /mnt/cache/TV. May also be fine is you use /mnt/user/downloads and /mnt/user/TV too. I don't ever use /mnt/user/ for my download workflows, so not certain on that aspect.

They said "multiple array pools", meaning something different than what is currently offered. At least that's how it reads to me.

2025 at the earliest is one guess.

Multiple Unraid Array Pools. It would be beneficial to have a storage product deliver actual storage functionality.

Same here. The banner shows up on next visit despite being dismissed previously too. Functionality is entirely broken surrounding this.

Did you try Unassigned Devices with Remote Mount options?

You should probably find the proper support thread to post in.

Any chance of a new poll as my choice has changed over the past 15 months since the Poll started?

Sorry for your issues, but thanks for sharing them. You saved me and likely others ton of headache. I was going to do the same thing, since it took me 5 different "reset password" cycles until I got the email address actually used for unraid. However I felt "Nah, I've already had to jump through so many hoops already, I'll save that for another day". I'll save changing the email address for after someone says they were able to complete the process without issue.

As a likely safety step, do not assign any drives as Parity (yet). If you assign a wrong drive (a drive that was previously data) to parity, it will start to be overwritten with parity calculated data. With only data drives assigned in the new config, you have a chance to examine every Disk to see what data is contained on it. If you accidentally assigned an old parity disk as a data disk, it will likely not mount. That is from what I can recall about the steps. I'm sure others who have more recent information and experiences with similar situations will offer more directed advice too.

I would just RMA the motherboard without trying to repair the pins.

Just select multiple Servers in this plugin screen. For help ask in the support thread.

These don't have performance impacts different than other drives. Why would physical rust drives need TRIM? Are you sure you're not mixing up SSD drive behavior?

You need to run it on the system you are running unraid on. Otherwise while the sticks may be fine your bios settings could be all jacked up and causing the issues. So all you know is they work on a different system. You don't know if thecurrent system is setup right.

Run memtest for at least 12 hours. You likely have wrong settings for memory in your bios or are running the memory overclocked without realizing it.

SMR drives are perfectly fine depending on your usage patterns. If you use them for mass media storage, they work fine. This would be the write once and read many times usage pattern. Don't use them for constant churn video surveillance footage, backups, or items that are updated multiple times across it's lifetime and you'll be fine.

This plugin is obsolete and dead. Uninstall it.

From Beta to RC is "Soon™".

Plex Transcode directory: 9.0G /tmp/transcode

Three years later and still waiting on Multiple Arrays.

Another option if feasible, upgrade the client's so transcoding isn't needed and they can direct play your media. But certainly check when playback is finished to make sure the transcode directory is cleaned up by whatever server app your running (plex/emby/jellyfin etc)

It's your transcodes: 5.0G /tmp/Transcode

Nerdpack is a dead plugin as called out in the recommended posts. Go ask in Nerd Tools.

Worked fine for me in Edge-ium x64 both stable and dev versions with EFF Privacy Badger and uBlock Origin browser extensions installed. unRaid UI is set to "Azure" theme. Here's the CA settings for me --

https://community.fs.com/blog/should-we-use-cat6-or-cat6a-for-10gbase-t.html