view the rest of the comments
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!
I'm actually not 100% what killed the drive. It could have been an issue with the drive wearing out, but my services didn't write much locally and it wasn't super old so I assume its a heat issue with a fanless micro system. I try to write everything important to my NASs so I don't have to worry about random hardware failures, but this one didn't have backups configured before it failed. Other than the drive issue its been solid for 1.5-2 years of near constant uptime.
Unless you are writing petabytes the nvme did not just burn "wear" out. Probably shouldn't do anything until you figured out what caused this failure
Consumer SSDs generally only have a 200-600TBW rating, not petabytes. Its pretty easy to wear one out in a few years installed in a server.
Is the drive totally dead? Curious what SMART would report.
My gut feeling is that it's probably cheaper to buy a replacement m.2 than the hours of time to get netboot working but it could be a fun project!