81–90 of 265 posts
Earlier quoted context omitted.
ZFS makes this completely trivial except for the "beeps and lights a led" part
smartmontools makes this trivial and can email you which might be better than beeping and lights if you’re not always near your server. I use that plus smartctl_exporter so I can do metrics and alerting off that.
Earlier quoted context omitted.
AI has freed most people I know from the tedious job of writing actual emails and birthday greetings - leaving then more time to e.g. wash dishes or clean the floor. Seriously, if arts and creativity is what sets humans apart from other animals, then AI has almost completely displaced our capacity to even consider doing these activities ourselves. People reach for AI when they should be composing a birthday greeting…
Is it a genuine birthday greeting if you just let AI do the job?
Also you can use zfs on a proxmox host and use that both for NAS duty and for the VMs. For some reason people insist on doing truenas on top of proxmox and then introducing a networking layer between everything they do. Noooo…
Not a great time price-wise to be building a NAS, but I have been doing so for the last two weeks. Inside a Jonsbo N6 case, which is pretty nice with an 8x SATA backplane and drive bays (unlike the earlier Jonsbo variants). I ended up on shucking 4x the 14 TB WD Elements Desktop. They contain helium drives, the WD140EDGZ in my case, and are about a third cheaper than 4x the 12 TB WD Red Plus drives (which are air-fil…
I’m running an 8-drive ZFS RAIDZ2 pool. I’m wondering if you know — are the free space recommendations around ZFS cargo or real? Like I’m already giving up two full drives for redundancy (which saved my ass - I recently had two drives fail on me in quick succession — both SSDs from what looks like an identical batch) but then the advice is kinda saying I need to keep at least another drive worth of space free for the…
Earlier quoted context omitted.
Yes, indeed. ECC RAM is better than non-ECC RAM, also for ZFS. The myth, popularized by a notorious thread on the TrueNAS forums [1], is specifically that ZFS requires ECC RAM, and will do worse than other filesystems without it, because scrubbing will multiply a single bitflip into a failed pool. A ZFS core developer says that that isn't the case [2]. Here's some more reasoning [3], also about many other myths. [1]…
Usually if you’re using a NAS you don’t want to lose data, ZFS is not significantly more sensitive than everything else. But everything is actually quite sensitive. We’ve accepted lack of ECC because Intel decided it would be a product line differentiator, and serious customers who didn’t want random crashes or to lose data would buy chips with ECC. It’s actually less of an issue these days because DDR5 has (by spec)…
Also you can use zfs on a proxmox host and use that both for NAS duty and for the VMs. For some reason people insist on doing truenas on top of proxmox and then introducing a networking layer between everything they do. Noooo…
its probably dumb but what i do is use proxmox with a debian VM with docker installed and each docker container gets a virtual disk i make on the proxmox host. obviously more involved than running unraid or truenas but i think the complexity underneath is simpler.
I’m talking more about people doing the same as you except they’re linking the VM storage to another vm (truenas) over network despite it all being on same host. Think it’s mostly because people don’t want to deal with zfs via command line
Earlier quoted context omitted.
I would kill (figuratively, anyway) to have no AI whatsoever. No slop machine threatening to replace my job, or turn my job into babysitting its stupidity, and hardware would be reasonably priced? That would be awesome. AI has brought me nothing but downside.
But we now have trillionaires, aren't you happy about that? It means you might be the one some day too /s
Earlier quoted context omitted.
I've been thinking about building my own NAS as well. Mind sharing how much did you pay for those hard drives, and what motherboard did you choose?
https://diskprices.com/ is great for this You have SATA or SAS to pick from. The CPU requirements for a storage server are not high. On a typical ATX board you have motherboard SATA and can put SAS controllers in the spare PCIe slots. My first "NAS" was two 22TB hard drives in a ZFS pool on my motherboard SATA
Earlier quoted context omitted.
I've been thinking about building my own NAS as well. Mind sharing how much did you pay for those hard drives, and what motherboard did you choose?
https://diskprices.com/ is great for this You have SATA or SAS to pick from. The CPU requirements for a storage server are not high. On a typical ATX board you have motherboard SATA and can put SAS controllers in the spare PCIe slots. My first "NAS" was two 22TB hard drives in a ZFS pool on my motherboard SATA
Earlier quoted context omitted.
That is kind of exactly how zfs works though. The guide isn't complete, sure, but "rebuilding" the array is just replace the disk and run a single zfs command.
That’s comforting to know; that wasn’t true in the past for ext4 over lvm (is it true now?). But what is that command? And how do you know which disk has gone bad? I am sure I can get an answer from Google / Claude / ChatGPT, but a guide is incomplete without it - and the failure report should be active like a beep or flashing hardware light - I typically log into my NAS only a few times a year. A motd or other banne…
https://openzfs.github.io/openzfs-docs/man/master/8/zpool-re...
ZFS got this right. MDADM on ext4 somehow did not.
EDIT: ext4 on MDADM.
How ZFS gets this right: zfs(8) on zpool(8). So, basically, ext4 and mdadm can talk to each other.