Like other people have said, it’s going to depend on what you want to do with the NAS. If it’s going to be a pure NAS (ie network storage only), then using onboard will be fine. If you plan on doing other things (home assistant, media server, etc), I recommend going the virtual machine + HBA route.

I used a hodge-podge of chinesium parts and leftover drives to create a DAS system that hooks up to an HBA via DAC. I’m actually kinda surprised how stable it’s all been.

Measuring my server cluster

Personally, I just don’t ask questions I don’t want the answer to.

I’m learning to hate it right now too. For some reason, its refusing to upload a local image from my laptop, and the alarm that comes up tells me exactly nothing useful.

Worse. Terminally online edgelord.

“Yay! We’ve created artificial general intelligence!”

“…Fuck, it’s an asshole.”

“It works. What more do you want?”

Why is it that whenever something is spitting out junk data, those specific characters are involved?

I have a lot of questions for whoever set that up in the first place, first and foremost of which is: why in the everlasting fuck was that computer ever attached to the internet? At most it should be allowed internal network access only.

Which conversions? Most metric conversions are drastically simpler than their imperial counterparts.

It’s a function of ZFS itself. Data that is to be written to the drives is first written to RAM, then transferred to the drives. One of the benefits of this is that if you are moving a file that is smaller than the available RAM, your transfer won’t appear to be limited to the write speed of the drives.

ZFS. It can use up as much RAM as you care to give it for caching. So if you are slinging a lot of data back and forth, more RAM is better. Especially if you are using HDDs instead of SSDs.