BRiT

Which Preclear version? The docker Binhex version? Or the other one? Both have their own dedicated support threads, so you'll have better chances of getting support there. The support link is shown in the Community Apps lasting.

I think your docker.img file is full. This is likely a sign that you have a docker misconfigured program somewhere and it is writing data inside the img file. There's a FAQ entry on this.

Speaking of which, what does the new icon at the far left do, other than take up space? Pretty sure it wasn't there before. They still show up even on Desktop mode in Chrome browser. It's annoying.

Use client streaming devices which do not need to transcode 4K content, that will improve your experience the most.

What you wrote is confused. Unraid is not raid. It only uses Raid systems for the Cache Pools or if you used the ZFS plugins. Did you only ever had Cache Pool drives? Were you using ZFS plugins? Likely you did neither, and only had data drives. Every data disk in unRaid is its own self contained filesystem. The Parity drives hold values from a mathematical formula to offer protection and be able to recover data from failed drives. As to steps for recovery, try what Jonathanm wrote. When you reassign drives in a new setup, never ever assign a drive as Parity if you are uncertain. The system will detect if the drives contain a valid filesystem if assigned as a data drive. When a drive is assigned as parity, it will begin overwriting what's on it with the calculated information. You dont want to do that with data drives.

Enable advanced search inside CA and use this one from results? https://hub.docker.com/r/kelvie/web-brogue

So 27.5 TB of backups for $10K.

👀 I thought my 15 hour 10 minute parity check times were long. If they were any longer I'd definitely use that tuner plugin to split it across multiple nights. I run mine once a month. What do you do?

How long would a Parity Check run for with a drive that size? I'm using 8 TB drives now and really wish the Parity Chrck time could be cut in half somehow. I couldn't imagine it doubling in time and then some.

Filesystem overhead most likely

Your posted code is missing the build portion.

Unpack onto cache drive then move final file to the drive. Unpacking is one of the worst case scenarios for shingled drives, way to many file modifications done.

Disable WSDD "solves" the issue.

Answered earlier in the thread. In the past people may not have been exposing their server to the internet but now they may want the "My Servers" functionality so they tried to do something. They forwarded too many ports or DMZed their server and simply didn't secure it properly to start with. Nothing wrong with "My Servers", but it may have been the push for some to try out things they really shouldn't have. Humans are flawed. They tend to skip instructions or pick parts randomly to follow and ignore the rest.

Just noting possible cause and effects -- why some may be opening up ports or putting servers into DMZ. It was asked "Why now and not before", well there's an answer. Never said anything was wrong with the implementation of "My Servers".

More folks opening up ports for the early preview feature of "unraid.net" to link back to their own server?

Exactly. Give us the ability to flat out ban connections from certain countries or white-list only certain countries. For a US server I would ban everything outside of North America (US and Canada). For Europe I would ban anything in China, Russia, India or other Hotspot hacker regions for a start.

On the right hand side at the bottom in all white is the ATX 24 Pin connection. Right above that is a single EPS connection (8 pin). A little bit above that one is the other EPS connection.

They're saying your new motherboard requires it for power.

Most likely its telegraf and how its "monitoring" drives. Pause/Stop that to see if the drives spin down in due time.

@optiman did you do the steps listed by another user who said it fixed things for him in the 6.9.0 thread?

/mnt/user/ is just an aggregate of /mnt/disk#/ and /mnt/cache/, so if those are covered you don't need to explicitly cover /mnt/user/.

I find it boggling that anyone uses a system designed for data integrity to not want the data integrity portions to function.

Disabling WSDD prevents the problem 100% of the time...

But its what you need.