JonathanM

Are you able to run 1.20.5 or 1.20.6 after doing this?

Sure, we want people to be as satisfied as possible before committing. If it's worth your time to extend the trial, go right ahead. That's what the trial extensions are for, to be absolutely positive before you pull the trigger.

Port mapping only applies to bridge. All ports are open when you assign an IP. Port changes must be made in the application itself.

A properly set up UPS would have avoided all that drama. Unraid really doesn't like having the power cut, you are lucky more didn't go wrong.

How long did that take? Writing zeroes to the entire capacity of the drive and simultaneously updating parity takes a LONG time. Many, many hours.

If you are rebuilding the smaller drives to the new ones there is no need for them to be clear. It's only when you add new data slots to an already parity protected array that the disk must be clear.

This is a contentious subject, as in normal operation the parity drive is the last to flush writes, meaning it's way more likely for the parity disk to be the one that needs to be changed if there is a sync error. The defaults have been switched back and forth a few times. Non-correcting is obviously my preference, but the longer a sync error stays around, the greater the chance a failed drive will happen before it's corrected, and have corruption as a result on the rebuilt disk. It's not completely black and white.

This is why automatic parity checks should always be non-correcting. If errors are found, there should be an investigation and a probable cause found before action is taken.

Not universally. In Unraid, the root folders on each disk or pool can be exported as user shares. I recommend watching spaceinvader one's Unraid videos on youtube, he has a load of very informative content.

Short answer, no, each array drive is a single volume using all available space. Long answer, Unraid is linux based, and the paths are going to be completely different between a windows and linux install of plex. Disclaimer, I am an emby user, so I don't have first hand experience with this, but here is supposed to be a guide of sorts. https://support.plex.tv/articles/201370363-move-an-install-to-another-system/

Yes, but I had a hard time understanding the OP question, it was clear on one part, but the "whenever I add files parity runs" had me questioning what was really intended or desired. I figured more reading would help the OP get where they wanted to go.

No. This is just a test to see if the motherboard is not resetting properly.

The basic storage functions will transfer fine, as long as both the old and new boards pass the drive ID's through identically. The only issue there is hardware RAID or drive enclosures that can modify the ID's. Any hardware that was passed through directly to VM's or containers will no longer be present and cause errors.

Turn PSU off, press power button on tower to drain residual power, turn PSU on, wait a beat to allow the motherboard to wake up, then press the power button. Probably not the USB stick, but the motherboard USB controller.

That sounds more like a motherboard issue. If it happens again try a cold boot, actually remove power from the motherboard with a power switch on the PSU or removing the AC supply.

No, the only changes made to the flash would be in the config folder. Replacing that folder with default files and adding your specific key file that belongs with that GUID will reset everything to new.

contact support. We can't do anything about keys here on the forum. @SpencerJ

You don't. If it turns back on unattended, how will you know if it is safe to turn back on, there may still be events happening that it would be better to stay off until things blow over, maybe literally. It's best practice to monitor the server startup, so you can intervene if things aren't going well.

Sounds perfectly reasonable for a core temp.

It's a good idea to do a non-correcting parity check after doing a disk rebuild. Rebuilds don't "check their work" by reading what was written to the rebuilt drive, it's assumed if a write completes without error, it wrote correctly.

Depends. There are other things you can tweak with regards to memory, cache pressure and such, and honestly Unraid is tuned for best performance with smaller amounts of RAM and may not make the best use of more than 64GB of RAM. I don't have the luxury of owning any systems with more than 32GB right now, so I must leave hands on research as an exercise for the reader.

It will kill performance if run too often, as caching data is what speeds many things along. As a clean up tool run when performance isn't a priority, or before starting a task, it should be fine. It does prove to some extent that you are over committing the memory you have for optimum performance, so more RAM would help if you really need to reserve that much RAM for VM use. I would try reducing the VM RAM allocations and see if it hurts or helps the VM performance. RAM caching by the host is one of the things that can really speed up a VM, and if you deny the host that RAM it can hurt the VM speed.

After a minute of googling (as in, no real research) I found this which may or may not do something in Unraid, haven't tried it, so use at your own risk, it was billed as a "linux" solution. This apparently a. clears speculative data that was cached b. consolidates the in use memory. If you are game to try this, execute at a point where the VM would fail to launch. To repeat, I HAVE NO CLUE IF THIS WILL DO BAD THINGS TO UNRAID.

Perhaps out of unfragmented memory. Some operations require contiguous blocks, and over time more and more addresses can be tied up and unable to be reallocated, even if the total amount free is plenty.

If the stock scheduling doesn't give you the flexibility you need, maybe look into the tuning plugin?