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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Did I just brick my SAS drive?
I was trying to make a pool with the other 5 drives and this one kept giving errors. As a completer beginner I turned to gpt.....
What can I do? Is that drive bricked for good?
Don't clown on me, I understand my mistake in running shell scripts from Ai...
Edit: EMPTY DRIVES NO DATA
The initial error was:
Edit: sde and SDA are the same drive, name just changed for some reason And also I know it was 100% my fault and preventable π
Thanks for the input
I thought the SAS worked like a data, just wipe and go... I'm not sure how to get this SAS connected to another computer as it is connected to my server through a SAS card...
Any ideas?
I have never worked with SAS drives. Another way to do what I suggested is to connect the server to a display output and boot a linux ISO with a libe environment.
Yeah, generally it does. Maybe just see if there's a command to turn DIF off? I've never had an issue using a SAS drive just like any other. It's certainly not anything permanent.