To add something useful, this is very cool but I wish it came in JBOD form so I could run it off a Mac Mini instead, and the pricing listed in TFA seems like an idealistic lower limit.
In my case, I currently use a Macbook Air M1 (my personal one which I currently don't need as a laptop). Absolute overkill and in some aspects annoying - only two USB-C ports for example - but it was available and it's fanless and doesn't need much power.
When there's a MacOS security update and the Macbook reboots, do NAS functions work before a local user has logged in?
I think I turned auto update off on this machine but if it reboots, you would have to login first. Doesn't bother me, though. I don't have any uptime requirements.
Any launch daemon service will load and/or start at boot, only user-domain services require a login (like the Dock or menu bar would)
I see the appeal but I’m curious about the performance.
I should probably just hook something up with, say, the old Mac Mini I have lying around, but it's fun to consider the options.
To take a look at the 3D files for the chassi was literally the reason I open the blog post, sadly they haven't been published yet!
In the meantime, what are people's favorite 3D printed desktop/NAS chassis? I'm currently sitting and sketching one myself and looking for inspiration :)
https://makerworld.com/en/models/1644686-n5-mini-a-3d-printe...
They’re hardly competitive on price compared to an old nuc too. Even a new N100 with ram and ssd can be purchased heaper than a barebones Pi 5.
ARM64 does limit what software you can run as well as does the anaemic GPU hardware. They are good for other things and very small servers (like PIHoles) but once multiple drives are involved they aren't the right solution anymore.
There are good all-in-one software solutions for all this stuff (unraid comes to mind) and I really feel this kind of article is unfinished without going into that kind of thing.
Having done it, the list for me is pretty much: install using the file system you fancy, setup the raid you want, install samba and nfs, eventually avahi and encryption and that’s pretty much it.
I wouldn’t personally call that non sense. Is there something I am missing?
It isn’t though.
I got that far and I wasn’t happy. There’s a lot of extra stuff you have to think about when you want a system to run unattended, vs something that’s a workstation.
First thing I noticed was the noise and the heat. Had to install a daemon to power down the hard disks when not in use. Then when I wanted RAID I had to go spend half a day learning to do that. Then there was software updates. So on and so forth.
I also had some lingering concerns about power consumption which meant I was going to have to get out some power monitors and read some stuff about Linux power tuning.
After a while the sense of “all in one” like packages TrueNAS and unraid started to make sense.
I was all set for unraid but luckily I came into a bit of extra money and I was able to buy some of my life back with a simple box with all of this designed and configured by people who know what they are doing.
Now all I need to do is manage storage and services which is all I should have to do with a NAS.
All this stuff is interesting to learn but there’s only so many hours in the day.
By all means if you want a hobby project or you’re not concerned with non functional aspects like reliability, power consumption and security and maintenance or if you’re very poor then building your own NAS makes sense.
It depends on the drives you buy, of course, but unnecessary spin-up/spin-down cycles will wear out drives faster. Many NAS drives will keep running intentionally for this reason. If the drives didn't spin down by themselves, it's possible they weren't designed to start/stop that often.
My personal NAS solution is a combination of Debian (for stability and unattended updates) with a motherboard that's in low-power mode, with ZFS + the usual software for accessing the NAS installed. I could write a script that reboots the system based on /var/run/reboot-required but a monthly scheduled reboot works fine too.
In my experience, this setup rarely requires any maintenance. It's quite boring for a homelab project. Once every few years I need to upgrade to a newer version of Debian (last time I went from 10 to 11 to 12 in one go) but even that isn't much of a spectacle if you don't mess with non-Debian package repositories.
I used to change the frequency governor for my cpu on my previous NAS but the default Linux setup (schedutil) is now perfectly adequate. Same with disk power, default is fine.
The whole thing just shugs along happily with basically no effort on my side apart from the occasional upgrade requiring manual intervention.
It certainly didn't require anything which I would consider non sense - and I have seen plenty of things I would call that in the past, looking at you OpenLDAP and PAM. Sure, you need to have a vague idea of what RAID is but then again building a NAS and expecting to need zero knowledge of storage seems extremely ambitious to me. Then again, I realise that what I consider basic knowledge taken for granted might not seem to be so basic someone else point of view.
for USD699 (no ram and no storage) you can get this
6 SATA, 5 NVME drives, OCUlink and much more.
https://aoostar.com/products/aoostar-wtr-max-amd-r7-pro-8845...
All that being said, there are more affordable NAS cases that would eliminate the labor. This is both an art piece and a because-I-can kind of venture.
NAS do make sense in some contexts. But over the last decade they've become something people do just to do because it's hip. It usually makes much more sense just to put your storage drives in the computer you'll use them in.
But it is a problem that most people don't have capable computers anymore. :\
A lot of people just use laptops and tablets / phones with limited storage expansion space at home, and want a dedicated device for a firewall/router anyways (no worries about reboots or other interruptions due to personal work on that computer, etc).
One more powerful computer to use as both NAS and firewall (and for various shared services...) makes a lot of sense much of the time - hence the popularity of proxmox.
I have no idea how having a NAS would make somebody hip. Very strange disco. Everybody should have one.
They typically present as 4 USB connected external drives, which you can softraid into whatever. They also support eSATA. At one point I had 3 of these plugged into a spare intel NUC and used it as a NAS running first Windows, then Ubuntu, then unRAID over about 5 years. It wasn't blazing fast, but got the job done for home use.
I love seeing these cheap builds like this. IMHO NAS boxes are way overpriced, and underpowered. I had multiples the performance and capability piecemeal hacking together my old setup than buying the all-in-one systems that will lose vendor coverage in 2 years.
But this article points out that there really isn't any reason not to make this stuff out of printable plastic.
I'd guess the only real issue is cost.
ggm•6mo ago
I mean, pricewise and avoiding usb, it's a nice build. I have something not a million miles off using a zimablade and a pci card doing sata, with an ali express sata disk box and an atx psu. Even got 12v off the atx to power the zimablade via DCin
Havoc•6mo ago
Seen some reports of people running into heat issues with them though if they run them full. So they end up using 3 out of 5 slots etc.
ggm•6mo ago
Havoc•6mo ago
I went with a bunch of second hand enterprise ones (also sata) and seems to be working out great
wtallis•6mo ago
That's not how PCIe lanes work. Regardless of how many PCIe lanes are used to connect the CPU to the HBA, only one packet will be traversing that link at a time (striped across the lanes), but that imposes no direct constraints on what the other side of the HBA is doing with its several SATA links simultaneously. With 16Gb/s of PCIe bandwidth, that HBA should have no trouble keeping more than one 6Gb/s SATA link busy.
ggm•6mo ago
toast0•6mo ago
The HBA may not have or need much buffering, as transfer to/from system memory with DMA should be pretty fast... I'd guess enough memory to fully buffer one outgoing command for each port, and one or two to buffer a response for each port as well; they may have more, but not much is necessary.
Some multi-port sata cards do terrible things though. Rather than using a proper controller for the number of ports, they have a one port controller and then a sata port multiplier. These do result in a meaningful restriction in bandwidth, and some multipliers require waiting for a response before communicating with another drive which would result in poor throughput for most NAS workflows.
A particularly terrible idea would be a port multiplier hooked up as a m.2 sata device, rather than a pci-e sata controller. I don't know that I've seen that one (edit, found one on amazon), but I'm pretty sure I've seen the controller + port multiplier combo. It's definitely worth finding out what controller is on the board before buying to avoid surprises.
ggm•6mo ago
They say the bandwidth far exceeds the individual SATA port speeds. But, there's little to no visible buffer on the card.
It's not an HBA, as much as a port "multiplier"
https://www.newegg.com/orico-pm2ts6-bp-pci-express-to-m-2-ca...
toast0•6mo ago
You don't need a lot of buffer to be an AHCI controller. You need enough space for the work queue that the driver writes, for write requests, you can have one sector sized buffer, DMA to fill it and then send it to the disk, but if you have two buffers, you can max throughput without doing anything fancy. For reads, chances are you'll be able to DMA out faster than the disk filled, two buffers is probably enough there, too.
So I don't know how much space you need for the command queue, but NCQ max is 32, let's say each queue entry is 256 bytes cause that's probably way more than enough. For each port, then you'd need 8k for the command queue, 8k for write buffers, and 8k for read buffers. Or a total of 144k of memory for a 6 port device... That's not a lot of ram to stuff into a controller ASIC.
Maybe you want a little more ram, in case the driver gets behind. You don't need extra buffers for writes... if the DMA is too slow, you just lose throughput, but no big deal, DMA will only be too slow if the system memory controller is very busy, and you can let the disk idle then. You might want to be able to fully buffer all reads, even if you can't DMA them out though. Then you don't have to worry about what happens if a read comes in and you don't have anywhere to put it. In that case, you'd have 8k command buffer, 8k write buffer, 32x4k = 128k read buffer = 144k per port, 864k for a 6 port device, still not enough that you need an external ram.
[1] https://www.asmedia.com.tw/product/45aYq54sP8Qh7WH8/58dYQ8bx...
[2] https://www.amazon.com/ChenYang-Function-Converter-Adapter-J...
[3] https://www.jmicron.com/file/download/893/JMB575.pdf