I have 4x 6TB HDDs in my NAS. Around 5 years ago I decided to simply replace any dead drives with 6TB ones instead of my previous strategy of slowly upgrading their size. I figured I could swap to 8TB 2.5" SATA SSDs that had just started to exist and would surely only get cheaper in the future…
I fucking love copyparty. It starts simple enough but then the millions of options and configs let you twist it into exactly what you need.
As someone that runs a server OS that doesn’t support docker, it is very refreshing to see a single binary project. It has a focus on being administrator friendly thats really fallen out of fashion these days.
I think it would be fine. Friend of mine has Immich on a N100, like you mentioned, the initial ML tasks on a big library takes over 24 hours but once it’s done it doesn’t need much. I don’t have experience running next cloud but the others you mentioned don’t need much RAM/CPU.
ZFS doesn’t need much RAM, especially for a two disk 4TB mirror. It soaks up free RAM to use as a cache which makes people think it needs a lot. If the cache is tiny you just end up hitting the actual speed of the HDDs more often, which sounds within your expectations. I dare say you could get by with 8 GB, but 16GB would be plenty.
I’d only point out if you’re looking for it to last 10 years, a neat package like the ugreen might bite you. A more standard diy PC will have more replaceable parts. Would be bigger and more power hungry though.
Ah kay, definitely not a RAM size problem then.
iostat -x 5
Will print out per drive stats every 5 seconds. The first output is an average since boot. Check all of the drives have similar values while performing a write. Might be one drive is having problems and slows everything down, hopefully unlikely if they are brand new drives.
zpool iostat -w
Will print out a latency histogram. Check if any have a lot above 1s and if it’s in the disk or sync queues. Here’s mine with 4 HDDs in z1 working fairly happily for comparison:
The init_on_alloc=0 kernel flag I mentioned below might still be worth trying.
deleted by creator
After some googling:
Some Linux distributions (at least Debian, Ubuntu) enable init_on_alloc option as security precaution by default. This option can help to prevent possible information leaks and make control-flow bugs that depend on uninitialized values more deterministic.
Unfortunately, it can lower ARC throughput considerably (see bug).
If you’re ready to cope with these security risks 6, you may disable it by setting init_on_alloc=0 in the GRUB kernel boot parameters.
I think it’s set to 1 on Raspberry Pi OS, you set it in /boot/cmdline.txtI think.
sync=disabled will make ZFS write to disk every 5 seconds instead of when software demands it, which maybe explains your LED behavior.
Jeff Geerling found that writes with Z1 was 74 MB/sec using the Radxa Penta SATA HAT with SSDs. Any HDD should be that fast, the SATA hat is likely the bottleneck.
Are you performing writes locally, or over smb?
Can try iostat or zpool iostat to monitor drive writes and latencies, might give a clue.
How much RAM does the Pi 5 have?
It runs basically the same PebbleOS, so they’ll work with any app that works with the original Pebbles. They plan to keep using the community app hosting at https://apps.rebble.io/. There’s also GadgetBridge that’s compatible. Eric mentioned on HN the intention for an official open source library that can be used to make other companion apps too.
Yeah the mobile app is open source too https://github.com/pebble-dev/mobile-app
In my head I thought one could make relatively cheap high capacity in 2.5" SATA form factor by having more NAND chips of lower capacity. You give up speed and PCB space but that’s fine since bandwidth and IOPS are limited by SATA anyway and there’s plenty of space compared to M.2.
Turns out to not shake out that way, controller ICs that support SATA aren’t coming out any more, and NAND ICs are internally stacked to use up channels while not taking up PCB space.
There are some enterprise options, but they’re mad expensive.