Julius

I want to have total parity size expanded. It now has a 10TB and 6TB drive as parity 1 and 2, so only 6TB can be used in the array. I have another 10TB drive (planned to be) in the array, and intend to swap them around. What's the best route to go here? Do I just stop the array and unassign that 2nd parity 6TB HDD first? Then take the 10TB out of the array as well? Or can I do both in one go and start the array with the 2 swapped around? Is there a way, outside of the Unbalance plugin, to actually physically move out the data that would be on the 10TB array disk, so I'm certain to not lose anything now stored on it? How do I know what the actual amount of disks that can fail (or disappear) in the array is, if there are 8 HDD in the array (not counting the 2 parity drives) ?

I agree, this plugin has a tendency to mess up your sshd_config entirely in no time. I would not recommend using it. Just one reboot and you'll know why; It locked me out many times, not because of the banning, but because it ruined ssh config. Had to go manually fix it with KVM access to the unRAID server. And then, looking at sshd_config showed all kinds of double entries. It's better to populate the go script with copy commands and just create and maintain your own ssh config.

Come to think of it; Perhaps a /boot/config/custom or /boot/config/local dir could be used, where, if a file exists there it overrules the one provided by /boot during boot time. This saves us a lot of plugin installs etc.

Both are missing in the webGUI i.m.o. - I tend to want to use publickey login only, using a ed25519 key, and its config is ruined with every reboot without having to do strange workarounds in the go script copying entire /etc/ssh /root/.ssh folders etc., which frankly is a PITA, because you have to maintain the sources with new known hosts etc. - I also tend to want to use my own wildcard certs and own choice of encryption used for TLS in NGINX for unraid's panel. This could easily be fixed using an include for nginx config for all ssl 443 hosts, like I do here, and then have us change 'Advanced nginx ssl settings' where we can edit said include file. They do it like this in, for example, froxlor (which is open source, so implementation shouldn't be too hard..). This should also properly alter config in /boot, so it is persistent after reboots.

And that is very true, I guess, since prices have been dropping a lot lately for drives under 12 TB. Anyway, thanks for explaning.

Aha, so, beyond what is actual content it is purposely writing zeros onto the 10TB surface, even if that's never going to be used? Sorry for the silly dinosaur questions here, I come from a time when writing to disk surface would be considered wasteful, and only done when absolutely required, so I was assuming a bit flip would say "rest of the surface not needed" and that would be it. Just so you know where I'm coming from; It already didn't feel good to have to 'preclear' them, it seems needlessly strenuous for the disks. Must be me, but I'd be designing this a different way.

I've read about what is actually on the parity drive(s), but there's some things I don't really get about its sync operations; I have an array with now ~5 TB of data used on it. Two parity drives of 6 TB each. I have 10 TB HGST DC drives that I wanted to expand parity size with, so I added the 10TB's to unRAID and precleared them. Then stopped the array, replaced the 1st Parity drive with a 10TB one. Much to my surprise it was parity-syncing way more than the 5TB that is actually content. In fact, it even apparently synced way more than 6TB of the 2nd Parity disk. I would expect a speed up after the 5TB, since all other space is just nothingness. Why is it reading and writing from and to nothing, when just a quick format with a TOC would suffice?

Hey SpaceInvader, Great work, but can I still run everything of the pi-hole on its own LAN IP, like I used to? (so no port-change required) The option seems to have disappeared, and my pihole stopped running! And yes, this meant I had DNS resolving in unRAID point to the pihole IP, which is a different one from the unRAID IP. TIA! Never mind the above, I decided to drop pi-hole entirely and use Diversion on my ASUS RX router with Merlin firmware. Better to block stuff closer to the door: https://diversion.ch/diversion/use/theme-colors.html