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!
view the rest of the comments
It seems to either be completely fine and a power cycle makes no difference - or it loses the whole structure. I don't know how I'm supposed to pull the disks back in. It doesn't seem to detect that they're already setup as part of a pool.
The pool I've created doesn't vanish but it seems my only option for it is "manage devices" which takes me to the "Add VDEVs to the Pool" menu where my three disks show up as unassigned. The only presented option seems to be to wipe them in order to add them back to the pool.
Trying to search for this stuff doesn't seem to give me anything useful. I don't know what the intended behaviour is and what it is that I'm doing wrong. I would expect what should happen is that the disks come back online and get automatically added back to the pool again but no, apparently not?
Since ZFS keeps the config info on disk, I'm with another commenter wondering about your disk health.
Check the SMART data for each drive.