this post was submitted on 26 Dec 2025
-26 points (35.6% liked)

Selfhosted

53909 readers
358 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. 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!

founded 2 years ago
MODERATORS
-26
submitted 10 hours ago* (last edited 9 hours ago) by rook@lemmy.zip to c/selfhosted@lemmy.world
 

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:

collapsed inline media

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 😞

you are viewing a single comment's thread
view the rest of the comments
[–] atzanteol@sh.itjust.works 0 points 9 hours ago (1 children)

Am I the only one who has no idea what their problem is now? Just that there was an error about DIF but... What's the issue now?

[–] rook@lemmy.zip 1 points 8 hours ago (1 children)

The drive got whipped and apparently you're not supposed to wipe a SAS drive like a normal SATA one ...

[–] atzanteol@sh.itjust.works 4 points 8 hours ago (1 children)

The drive got whipped [sic]

Oh, it was just sitting there and "got wiped"? Not because of a command you ran?

Sorry to be snarky but when asking for help you need to provide what you did, what error message you see now or what you expect to happen and what is actually happening. Also what OS you're using would be helpful.

Presumably you should be able to get the drive back into a usable state - but I'm not familiar with SAS drives.

[–] rook@lemmy.zip 0 points 7 hours ago

Mb, I meant I wiped the drive...

I am using Truenas CE