JonathanM

When I click the download button, it said "download request received" in a blue notification, but nothing ever happened after that.

This application (not the template, so this is not aimed at @SmartPhoneLover, just informational to users) seems to be controversial, and may not be well received by the admins that run irchighway. There may be functionality issues as the author of the app negotiates with those admins. YMMV, but as of this posting, searching worked for me, but download functionality seemed to be broken. I suspect this may be ongoing, as automated downloading doesn't seem to be well received in their community.

Physical slots, while obviously necessary, are not nearly as important as a CPU and chipset capable of keeping that many resources separated and supplied with bandwidth. The number of usable lanes is quite limited with normal consumer CPU's. I suggest you search out a build that is currently doing what you need, and copying it pretty much exactly.

You have /data mapped to your array, but you are downloading to /home, which is inside the docker image. Change the root of the download folders in deluge to /data instead of /home/nobody/downloads.

Well, since the OP changed his router and immediately starting seeing login attempts with common users coming FROM THE ROUTER, it's reasonable to assume that the first answer is correct. The OP never answered, so we can only assume the issue was solved, one way or the other. Your answer didn't add anything to the discussion.

Show the cpu detail line, also, 70% is meaningless without core count, as it's only 70% of one core, so the total cpu % could be minuscule if this was on a threadripper or other high core count CPU.

Please don't post the same thing all over the place, it makes it impossible to coordinate responses. The proper place to post is in the specific container thread, you can find it by clicking on the container in the GUI and selecting support.

top command in the console. wa number on the cpu line

If the console is still showing the running command CTRL-C should stop it.

Have you checked how much CPU usage was IOWAIT? If that's the majority of it, then your solution is faster disks or interface, because IOWAIT is the CPU waiting for disks, not actual work being done. It's included in the usage because that portion of the CPU can't work on anything else while it's waiting.

Much faster to skip the clearing and just rebuild parity with the disks you want to keep. Are all your disks healthy?

Default is RAID1 for any number of drives added to the pool, unless you change that manually. Any valid BTRFS RAID level can be used, AFAIK. See this link for how drives of various capacities will be used with the different RAID levels. https://www.carfax.org.uk/btrfs-usage/

Assuming 14TB is physically connected where you want it, Boot up Screenshot Main page for drive order Tools, New config, preserve all Go to Main Select 14TB in the parity1 dropdown Select former 10TB parity in a blank data slot Start array let parity build Once parity build is complete, start parity check When check completes with zero errors, select format unmountable drives, making sure only drive listed as unmountable is former parity drive. Full SMART tests are good to do periodically, a parity check with a zero error output is almost as good. If the 14TB spins up and is detected, it's fine. If not, deal with the 3.3V. The only drive to get formatted in this entire operation should be the old parity drive once it's in a data slot, after parity is successfully completed.

Yes. XFS on pools is single drive only. Theoretically there may be other options in the future, but for now the options are single disk XFS or software defined BTRFS RAID levels.

Since you passed a parity check, the easiest would be to take note of the current drive assignments, do a new config preserving all, change the parity to the new 14TB, and assign the old parity drive to a new data slot. Start the array and build parity, but don't format the old parity drive until you finish a parity check with zero errors after the parity build is completed. If you are in doubt as to the health of any of your drives, post the diagnostic zip file and ask before moving forward. What I said to do obviously isn't the best path if you have any dodgy drives.

Since these drives are ostensibly survivors of the bathtub curve, this may not be as much of an issue, but those seagate models are notorious. One of the few models with their own dedicated wiki page. 😀 https://en.wikipedia.org/wiki/ST3000DM001 I'm not passing judgement on your specific drives, just posting notice for those unaware of the reputation as a whole. Better to be informed up front.

It's not necessarily corruption, but that is possible. More likely are speed and reliability issues when accessing all disks on the multiplier at the same time, such as when rebuilding a failed disk. As long as the enclosure doesn't mangle drive ID's (many do) it's not an issue to use them with UD. Many multi bay enclosures assign their own ID's instead of passing the disk through intact, causing issues with using multiple disks. You may end up only being able to populate 1 of the 4 bays at at time.

Depends on your use case, and how your files are currently distributed, and how you want them to be distributed in the future. Unraid doesn't care, and as long as you have proper minimum free space limits set, you'll never see a meaningful difference using the shares. It's purely an artificial need to organize things, but the benefits for most users lie on the side of letting drives fill up as they add them. That way the new files are all on a single drive, as most folks tend to use new files heavily then let them alone for archival reasons. However, if you are like some people, me included, that micro manage which files go on which physical disks, then sometimes you need to move files from disk to disk to free up space for new files that "belong" on a specific disk. That's why I asked the question, because unless you know a specific reason to move files, you probably don't really need to. Every file operation incurs risk from user error or other things, so the less you muck around, the safer your data is, generally speaking.

Why?

Another option is a VM that you install a remote desktop software like teamviewer. There are several permutations of this, securely remote accessing a computer on your home LAN. Honestly I prefer a VPN server hosted on a decent firewall / router. Wireguard on Unraid is a neat solution, but limits me too much.

No clue. I took a cursory look at the project page, but didn't see anything. Probably need to contact the developer of the app itself, this thread is for getting the app running on Unraid, it doesn't cover direct app support. Why not just set up rules in the nginx location config for this specific app to deny outside ip's?

If you read this thread, you would find... https://forums.unraid.net/topic/82198-support-binhex-urbackup/?do=findComment&comment=918119

Refutance is systile, your ass will be laminated.

Port remapping there only applies to bridged connections. If you want to use a custom ip you have to change the port in the program itself.

This. sd? designations are subject to change on hardware differences. Once you have a drive failure, to rebuild requires all remaining drives to be read flawlessly to rebuild the failed drive. So yes, if you suspect an issue with a port, it's probably not a great idea to move a drive there to try to rebuild a different drive. Diagnostics might provide a better picture of what's happening.