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

Selfhosted

53933 readers
690 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
 

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

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 😞

**Edit: ** from LM22, output of sudo sg_format -vv /dev/sda

BIG EDIT:

For people that can help (btw, thx a lot), some more relevant info:

Exact drive model: SEAGATE ST4000NM0023 XMGG

HBA model and firmware: lspci | grep -i raid 00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] Its an LSI card Bought it here

Kernel version / distro: I was using Truenas when I formatted it. Now trouble shooting on other PC got (6.8.0-38-generic), Linux Mint 22

Whether the controller supports DIF/DIX (T10 PI): output of lspci -vv

Whether other identical drives still work in the same slot/cable: yes all the other 5 drives worked when i set up a RAIDZ2 and a couple of them are exact same model of HDD

COMMANDS This is what I got for each command: verbatim output from

Thanks for all the help 😁

you are viewing a single comment's thread
view the rest of the comments
[–] PhobosAnomaly@feddit.uk 15 points 1 day ago* (last edited 1 day ago)

Sorry friend.

If your data was occupationally-sensitive or renders you vulnerable to financial ruination, it's time to move to a recovery phase and see if modern data recovery specialists can work their voodoo.

Remember: never run experimental commands (you or a GenAI) in a live environment. See how it breaks things in a test environment first - if it shits itself, you may even get to learn how to fix it before running the instruction on live data.

Anecdote time! A good friend of mine drove his car to a mutual colleague's place once because the wipers were about as much use as two chicken breasts on metal poles. He says to our colleague "Hey Foxy, I hear you're good with cars, can you fix these wipers for me? The rubber seems to be in good nick but it's not clearing anything".

"Sure thing," Foxy proudly announces, "I'll get to work".

Foxy strips the wipers down, one component at a time, before dusting his hands off and walking away.

"What's going on, Foxy? The thing's still in bits!" my pal says.

"No idea," says Foxy, "not a fucking Scooby mate" and goes back inside, leaving his wipers and actuating motor in about fourteen pieces on the roadside.

So much for being good with cars.