I'm kinda repeating things already said here, but there's a couple of points I wanted to highlight...
Monitor the SMART health: Enterprize and consumer drives fail, it's good to know in advance.
Plan for failure: something will go wrong... might be a drive failure, might be you wiping it by accident... just do backups.
Use redundancy; several cheapo rubbish drives in a RAID / ZFS / BTRFS pool are always better than 1 "good" drive on it's own.
Main point: build something and destroy it to see what happens, before you build your "final" setup - experience is always better than theory.
I built my own NAS and was going with ZFS until I fkd around with it.. for me... I then went with BTRFS because of my skills, tools I use, etc... BTRFS just made more sense to me... so I know I can repair it.
And test your backups 🎃
I'm currently playing around in VMs even before I order my hard drives. Just to see, what I can do. Next up is to simulate a root drive failure and how to replace that. I also want to test rolling back from snapshots.
The data that I really do need and can't replace is redundant anyway: one copy on my PC, one on my external HDD, one on my NAS and one on a system at my sisters place. Thats 4 copies on several media (one cold) and at another place. :)
Don't sweat it.
I remember looking into this as well like a year ago. I also found the same info and started to look into ssds, consumer and enterprise grade and after all that I realised that most of it is just useless fuzzing about. Yes it is an interesting rabbit hole in which I spent a week probably. In the end one simple thing nullifies most of this: you can track writes per day and SSD health. It is not like you need to somehow made a guess when the drives fail. You do not. Keep track of the health and writes per day and you will get a good sense of how your system behaves. Run that for 6 months and you are infinitely wiser when it comes to this stuff.
That rabbit hole is interesting, but also deep and scary. I'm trying to challenge myself by setting up Proxmox, as so far I've just used Raspbery Pis as well as OpenMediaVault. So when I saw those stories about drives dying after 6 months, I was a bit concerned;. Especially because I can't yet verify the truth in those storries, since I'd call myself and advanced novice if I', being generous.
I'll track drive usage and wear and see what my system does. Good point, then I can get rid of the guesswork. Thank you a lot!
Good luck!
I'll agree with the other commenter here.
Also there may not be any difference between the consumer and enterprise drives. The reason the enterprise cost more is the better warranty. But because they have different components.
Monitor the drives, modern drives are pretty good at predicting when they are dying, and replace it necessary.
Yeah, concering TBW there wasn't a huge difference between cosumer- and enterprise drives that I saw. Something along 2500TBW vs. 3500TBW (unless you go with those unaffordable drives, then yes). I'll monitor the drives and if I find rapidly increasing wear, I can still switch to another file system. The whole reason I bought the Lenovo is to setup a second machine and experiment, while I still have a running "production" system. Thank you!
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters | More Letters |
---|---|
NAS | Network-Attached Storage |
RAID | Redundant Array of Independent Disks for mass storage |
SSD | Solid State Drive mass storage |
3 acronyms in this thread; the most compressed thread commented on today has 4 acronyms.
[Thread #259 for this sub, first seen 2nd Nov 2023, 14:30] [FAQ] [Full list] [Contact] [Source code]
I am in the same boat as you are
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!