JonathanM

The wireguard VPN server built into Unraid would allow that.

I guess I'll try again, but it wouldn't start my world with the 1.20.6 jar and profile. It acted the same before and after I updated the Java version. Got it working, the issue was permissions on the world files I copied from my deprecated binhex mineos container. Now, I just have to figure out how to allow my unMined mapping container to access the world files, it doesn't like the new permissions.

Have you looked at Spaceinvader One's youtube channel? He has a comprensive list of Unraid videos.

The syslog will show the sector number, but there is no way to know which disk is wrong. It's also a very difficult problem to determine which file (or free space) on each disk is being used by that sector.

Can you please explain what you mean? The only way to use wifi with Unraid's base OS is to attach a wifi to ethernet bridge and utilize the ethernet port on the Unraid pc.

or

The correct support thread is If nobody can help there, try https://www.linuxserver.io/support

That was the first thing I noticed, it wouldn't toggle to the light side. Working now, but it got me thinking. Do you have statistics on dark vs. light usage? They would be skewed to the dark side, since that's the default, but I'd be curious what the statistics say.

Have you discovered Spaceinvader One on youtube yet?

Question is, was the shirt sourced from existing wardrobe, or issued as part of the onboarding package from Limetech? 🤣 Welcome, looks like you are fitting in quite well!

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.