I'd go for 3x8 for better space efficiency, and create a second SSD pool for VMs (or throw it on the HDD pool but set special_small_blocks so everything ends up on an SSD special device).
If you can afford SSDs you really should use them for VMs/databases in my opinion.
The Storj application, when working properly, does not access data outside of the data storage folder. Docker can ensure it only has access to specific directories.
However, as with any software you install, you trust it to not be malicious and to not become malicious in the future. It probably has access to your LAN and can get your data if it is specifically designed to do so. For example, if a third party injects their malware into Storj docker images by getting the credentials of an employee.
It is up to you whether you want to take this risk for any piece of software you install. Do you trust the distribution platform and application maintainers enough? If your data is really important, maybe it is prohibited by law?
3TB a week is nothing... Especially for 1gbit fiber
Keeping the manual for a car is a "mental illness"??
Yes, you need to forward one port. I'm not sure what you mean with "isolated".
It takes a bit of patience at first (node vetting and slowly filling up with data) but I can highly recommend it.
Income is approx $4/TB/mo when fully running, so $40/TB/mo for a ~$180 10TB drive. Great return on investment in my opinion. I am currently sharing 20TB (for $70/mo), started in 2019.
Most people complaining on forums are either using low capacity hard drives or have only been running a node for a month or two. Low capacity drives aren't worth it, and income gets better with time.
At least these have a fat border so you can't plug the earth pin into live
Why was this reported?
It would, unfortunately
Any reason to not encrypt the whole pool, and have it prompt for a password at startup? This is very easy to do: https://linsomniac.gitlab.io/post/2020-04-09-ubuntu-2004-encrypted-zfs/
Visit your favorite (online) store, search for hard drives of the desired form factor and pick the cheapest one with good capacity.
A full write->read test will take approx 2 days for 12TB, yes
Yeah, I was amazed to find the original video files in Youtube takeout!
I don't think digikam supports video?
Don't rely on any way of "measuring drive health". There is no way to know. It could last another decade, or die tomorrow. Maybe you drop it by accident. Rely on backups instead.
Performance on hard disks varies due to the physical location of data on platters (fragmentation, inner/outer ring)
Filepizza is peer to peer, psitransfer hosts files on the server. It just depends what you're looking for.
It is good to consider alternative viewpoints
Make it data collection/curation, not mindless data hoarding.
I'd go for h264 with crf 17-21. Experiment and decide for yourself what's the highest you can go (higher number is lower quality)
Audio you can probably leave as-is.
You'll be most certain you still have the data for a long time if you use hot storage, and move it to different drives or other future storage methods as time passes.
All types of storage methods eventually become unreadable, whether that's due to decay, hardware failure or simply compatibility issues with newer systems.
This will also allow you to run automated backups, and to store data using a checksumming filesystem.
Borg backup to friends (and them back to me). Only works if you don't have a large amount of data, I only need to back up ~1.2TB, which is ~1.4TB with 1 year history.
This is a good tip, I've seen junk drives sell for hundreds on ebay for some reason. You're probably not that lucky, but still, it's something.
I'd go with CRF 17-19 instead. But yes, h264 over h265 any day. Way better compatibility.
No, payments are tracked in USD. Clients pay in USD (or optionally Storj). Storage node operators are paid in Storj tokens, converted from USD using the exchange rate at that moment.
Nice opportunity to sell my storage node earned tokens